Mattrbld

Mattrbld is a Git-based headless CMS for teams managing website content independently of a frontend framework. It suits developers and agencies supporting small to medium-sized clients who want structured editing within a Git workflow. Its open-source self-hosted core and offline editing are useful, but publishing automation and media-heavy projects are weak fits.

Overview

Content remains in Git repositories rather than Mattrbld’s external servers, making the product a natural fit when version-controlled files are already part of the publishing process. Mattrbld supports JSON and Markdown files with YAML frontmatter; plain YAML support is planned but not implemented. It is a CMS, not a drag-and-drop website builder.

Schemas define fields and validation rules, which Mattrbld turns into editing forms. That gives editors a structured way to work with content without requiring them to edit files directly. Developers can also implement a preview route using Mattrbld’s protocol, so editors can see updates in real time.

Key features

Git workflow and offline editing

Mattrbld communicates with repositories through Git rather than proprietary provider APIs. Collaborators need accounts with their Git provider, and must authenticate to import private repositories or sync changes. GitLab, GitHub and Bitbucket require a CORS proxy. Mattrbld says it does not store passwords or access tokens, but credentials and repository requests pass through the configured proxy when one is needed, a consideration for teams assessing their infrastructure and security requirements.

Once a project is imported, users can create and edit content offline. They cannot publish changes until they reconnect, so offline work helps with drafting but does not remove the need for connectivity to sync.

Media and publishing limits

Mattrbld does not support Git LFS and is not suited to projects with heavy media use or large amounts of binary content. It also cannot schedule publishing: the application runs only while someone is actively using it. Teams that need scheduled releases or large media libraries should look elsewhere.

Pricing

Mattrbld offers two plans, both at no cost. The Official hosted instance is free to try and includes a provided CORS proxy intended for small-scale private projects, but availability is not guaranteed. That caveat makes it a cautious choice for projects that depend on a hosted service. The Self-hosted core is free to use for self-hosting, open source under GNU AGPL, and includes core features; it suits teams prepared to build and host the application themselves.

For self-hosting, Mattrbld can be built from source and hosted as a single-page application on a service of the user’s choice. This avoids reliance on the hosted instance, but makes hosting the team’s responsibility.

Platforms

Mattrbld is available on Android, iOS, the web and as a self-hosted application. Its hosting model is both hosted and self-hosted.

Who it's for

Mattrbld is best for developers or agencies helping small to medium-sized clients manage website content in Git. It is a stronger fit for structured text workflows than for teams seeking a visual site builder, automated publishing or repositories dominated by binary media.

Pros and cons

Pros

• Content stays in Git repositories, not Mattrbld’s external servers, which suits teams that want version-controlled content.
• Schemas generate editing forms with validation, giving editors structure while keeping content in supported file formats.
• Offline editing allows users to create and revise content after importing a project, even though publishing must wait for reconnection.
• The self-hosted core is free and open source under GNU AGPL, with hosting on a service of the user’s choice.

Cons

• The hosted instance has no availability guarantee, and its provided CORS proxy is intended for small-scale private projects.
• GitLab, GitHub and Bitbucket require a CORS proxy; credentials and repository requests pass through it when required.
• No Git LFS support makes media-heavy or binary-rich projects a poor fit.
• Publishing cannot be scheduled because Mattrbld only runs while someone is using it.
• Plain YAML support is planned but not implemented.

Alternatives

Git-Based CMS is a useful starting point for comparing products in this category. Choose Quiqr instead if you want a free, open-source CMS across desktop and self-hosted platforms. deco CMS is another option for teams seeking an open-source, self-hostable core.

Decap CMS is worth considering when its free plan’s one-site and one-seat allowance suits the project. Dhub may fit a personal GitHub workflow limited to public repositories and the default branch; its Hobby plan is free for one user. HugoCMS offers a free plan per domain, with multilingual support and unlimited updates.

Keystatic may suit teams that need up to three users per team on its free plan. Kiln offers a free, open-source self-hosted plan, with the user running the worker and GitHub App and providing the site host. Netlify is an alternative when a broader web platform’s free plan, with 300 credits per month, one concurrent build and one team owner, matches the need.

Verdict

Choose Mattrbld if your team wants schema-driven editing while keeping content in Git, and can accommodate its proxy requirements and lack of scheduled publishing. Its free self-hosted core is a clear reason to consider it; teams needing guaranteed hosted availability, Git LFS or automated release timing should look elsewhere.