Mattrbld

Mattrbld is a Git-based headless CMS for editing structured content independently of a site’s frontend framework. It suits developers and agencies managing content for small to medium-sized clients. Its strongest case is keeping content in Git while giving editors generated forms; media-heavy work and scheduled publishing call for another tool.

Overview

Content lives in Git repositories, not Mattrbld’s external servers. That makes it a natural fit for teams already comfortable with repository-based workflows, but collaborators need Git-provider accounts and authentication to import private repositories or sync changes. Mattrbld is a content editor, not a drag-and-drop website builder.

It supports JSON and Markdown files with YAML frontmatter. Schemas define fields and validation rules, then generate editing forms, helping teams keep content consistent without asking editors to work directly in files. Plain YAML support is planned but not implemented.

Key features

Git editing and offline work

Mattrbld communicates with repositories through Git rather than proprietary provider APIs. Its documentation names GitLab, GitHub and Bitbucket as providers that 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 required. Teams should factor that proxy into their security and infrastructure decisions.

Once a project has been imported, users can create and edit content offline, then publish changes after reconnecting. This is useful for drafting without a connection, but does not provide offline publishing.

Schemas and previews

Developers can implement a preview route using Mattrbld’s protocol, allowing editors to see content updates in real time. That flexibility puts setup in the hands of the project’s developers rather than providing a ready-made preview for every site.

Media and publishing limits

Mattrbld does not support Git LFS, making it a poor choice for media-heavy projects or repositories with large amounts of binary data. It also cannot schedule publishing: the application only runs while a user is actively using it, so teams that need unattended releases should look elsewhere.

Pricing

Both plans cost nothing. The Official hosted instance is free to try, but availability is not guaranteed; its provided CORS proxy is intended for small-scale private projects. It is the simplest way to start, provided that availability and proxy scope suit the project.

Self-hosted core is free to use for self-hosting and open source under GNU AGPL, with core features. It fits teams willing to build and host the single-page application themselves; unlike the hosted instance, it puts hosting in their hands. Mattrbld can be built from source and hosted on a service of the user’s choice.

Platforms

Mattrbld is available on Android, iOS and the web, and can be self-hosted. Its hosting model is both hosted and self-hosted, giving teams a choice between the official instance and running the application themselves.

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 when structured editing and repository-based storage matter more than scheduled publishing or handling large binary assets. Teams seeking a visual site builder, Git LFS support or unattended publishing should choose another approach.

Pros and cons

Pros

• Content stays in Git: repositories remain the content store rather than Mattrbld’s external servers.
• Structured editing: schemas generate forms from defined fields and validation rules.
• Offline drafting: users can edit after importing a project, even without a connection.
• Self-hosting option: teams can build the application from source and choose their hosting service.

Cons

• Publishing requires a connection: offline edits cannot be published until users reconnect.
• Proxy is part of some integrations: GitLab, GitHub and Bitbucket require a CORS proxy, through which credentials and repository requests pass.
• Weak fit for large media: no Git LFS support limits repositories with substantial binary content.
• No scheduled publishing: releases depend on a user actively running the application.

Alternatives

Git-Based CMS is a useful place to compare other tools in the category.

Consider Quiqr if you want a free, open-source option that runs on Linux, macOS, Windows and the web, with self-hosting available.

deco CMS is another option if you want an open-source, self-hostable CMS with a free core.

Choose Netlify if you need a platform with a free tier that includes 300 credits per month, one concurrent build and one team owner, or a paid Personal plan at $9 a month.

Decap CMS is an alternative with a free plan covering one site and one seat, and a free trial.

Kiln may suit teams looking for a free, self-hosted AGPL-3.0 option where they run the worker and GitHub App and provide the site host.

Siteleaf offers a free Developer plan with 100 MB, 100 pages, public GitHub repositories, API use within limits and community support; its Personal plan costs $7 a month, billed annually.

TinaCMS has a free plan for two users and two roles, with community support.

Dhub has a free Hobby plan for one user, limited to personal GitHub accounts and public repositories, with editing and pushing to the default branch.

Verdict

Choose Mattrbld if your team wants structured content editing while keeping content in Git, and has developers comfortable with schemas and repository setup. Its free hosted and self-hosted options make that workflow accessible, but the lack of scheduled publishing and Git LFS support is reason enough for media-heavy or automation-dependent projects to look elsewhere.