Mattrbld

Mattrbld is a Git-based headless CMS for creating and managing content without tying it to a particular frontend framework. Content stays in Git repositories rather than Mattrbld’s external servers. After importing a project, users can create and edit content offline, though they must reconnect to publish changes. Schemas define fields and validation rules, which Mattrbld uses to build editing forms. It supports JSON and Markdown files with YAML frontmatter; plain YAML support is planned but not implemented. Developers can implement a preview route using Mattrbld’s protocol to show content updates in real time. The CMS communicates with repositories through Git, and its documentation identifies GitLab, GitHub, and Bitbucket as providers requiring a CORS proxy. Mattrbld does not require its own account, but collaborators need accounts with their Git provider to access private repositories or sync changes. It can be self-hosted as a single-page application. The maker describes it as suitable for developers or agencies helping small to medium-sized clients manage website content, rather than as a drag-and-drop site builder.

Mattrbld offers Git-centered content editing with offline work and optional self-hosting. Its Git LFS and binary-content limits make it a poor fit for media-heavy projects.

Mattrbld suits developers or agencies managing website content for small to medium-sized clients, especially when content belongs in Git. It is not aimed at people looking for a drag-and-drop website builder.

Mattrbld is a Git-based headless CMS for teams that want structured content editing without committing to a particular frontend framework. It is best suited to developers and agencies supporting small or medium-sized clients with content already managed in Git. Its structured forms and offline editing are useful, but the lack of Git LFS and scheduled publishing narrows its fit.

Overview

Content remains in Git repositories rather than on Mattrbld’s external servers, so the product suits teams that want their content workflow to live alongside version-controlled project files. It is not a drag-and-drop website builder: it helps manage content, not build a site visually.

Mattrbld works with JSON and Markdown files using YAML frontmatter. Plain YAML support is planned but not implemented. Schemas define fields and validation rules, then generate forms for editors. That gives non-developers a structured way to enter content, while leaving the content model and frontend work with the team.

Key features

Git-based 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. Mattrbld’s documentation names GitLab, GitHub, and Bitbucket as providers that require a CORS proxy. The product says it does not store passwords or access tokens, but credentials and repository requests pass through the configured proxy when one is required. Teams should factor that proxy into their infrastructure and security decisions.

Offline work and publishing

After importing a project, users can create and edit content offline. They cannot publish changes until they reconnect, so offline editing helps with drafting but does not remove the need for network access to sync work. Mattrbld also cannot schedule publishing: it only runs while someone is actively using it. Teams that need unattended releases or timed campaigns should look elsewhere.

Previews and media

Developers can implement a preview route using Mattrbld’s protocol, allowing editors to see content updates in real time. This can connect structured editing to a project’s presentation, but it requires developer implementation. Despite its advanced media-management designation, Mattrbld does not support Git LFS and is not suited to projects with large amounts of binary content or media-heavy repositories.

Pricing

Mattrbld offers two free options, with different responsibilities attached. The Official hosted instance costs nothing, billed Free to try. It comes with no guarantee of availability, and its provided CORS proxy is intended for small-scale private projects. That makes it a low-cost way to try the hosted service, not a dependable foundation for a larger or business-critical workflow.

Self-hosted core costs nothing, billed Free to use for self-hosting. It is open source under GNU AGPL and includes core features. Users build it from source and host it as a single-page application on a service of their choice, so the no-cost plan trades managed hosting for setup and hosting responsibility. Mattrbld does not publish a paid plan in these options.

Platforms

Mattrbld is available on the web and can be self-hosted. It is also categorized for Android and iOS. Teams can choose the official hosted instance or host the application themselves; self-hosting is the better fit for groups that want control of where the application runs and can manage that hosting.

Who it's for

Mattrbld fits developers and agencies helping small to medium-sized clients manage website content in Git. It is most compelling when the team values repository-based storage, needs schema-generated forms, and can implement a preview route. It is a poor choice for media-heavy content, scheduled publication, or users expecting a visual site builder without developer involvement.

Pros and cons

Pros

• Content stays in Git. Teams keep content in repositories rather than Mattrbld’s external servers.
• Structured forms and validation. Schemas turn defined fields and rules into editing forms, reducing the need for editors to work directly in files.
• Offline editing. Users can continue creating and editing after importing a project, then sync when connectivity returns.
• Free hosted and self-hosted options. Users can try the hosted instance or build and host the open-source core themselves.

Cons

• No Git LFS support. Large binary assets and media-heavy repositories are a poor fit.
• No scheduled publishing. Publication requires an active user session, which rules out unattended timed releases.
• Proxy and provider accounts add setup. Collaborators need Git-provider accounts, and GitLab, GitHub, and Bitbucket require a CORS proxy.
• Self-hosting requires ownership of deployment. The free self-hosted option means building from source and arranging hosting yourself.

Alternatives

For a broader set of options in this category, browse Git-Based CMS.

• Sitepins may suit teams looking for a paid plan with stated site, organization, and user limits: its Pro plan is $10 a month, billed yearly, for 6 sites, 2 organizations, and 3 users per organization, with priority support.
• Kiln is another free, open-source self-hosted option. Its Self-hosted plan is free, free forever under AGPL-3.0, but you run the worker and GitHub App and provide the site host.
• Netlify is worth considering when a team wants a platform with an API as well as web access. Its Free plan is free, $0/month forever, with 300 credits per month, one concurrent build, and one team owner.
• Siteleaf offers a free Developer plan with 100 MB, 100 pages, public GitHub repositories, API access within limits, and community support; consider it if those caps and public-repository restriction suit the project.
• TinaCMS has a free plan for up to two users and two roles, with community support, which may suit a small team working within those limits.
• Decap CMS is another free CMS option for web and self-hosted use; its Free plan is free and includes one site and one seat.
• deco CMS is an open-source, self-hostable CMS with a free core, a possible alternative for teams that want to run their own infrastructure.
• Dhub offers a free Hobby plan for one user working with personal GitHub accounts and public repositories, with editing and pushing limited to the default branch.

Verdict

Choose Mattrbld if you are a developer or agency managing structured website content in Git and want offline editing without sending content to the CMS provider’s external servers. Its free hosted and self-hosted options make it approachable, but the absence of Git LFS and scheduled publishing makes it the wrong tool for media-heavy repositories or automated release workflows.