Mattrbld
mattrbld.com
- Free plan
- Web
- iPhone and iPad
- Android
- Self-hosted
What Mattrbld is
Mattrbld is a Git-based headless CMS for creating, editing, and managing content independently of a frontend framework. Content stays in Git repositories rather than on Mattrbld’s external servers. After importing a project, users can work offline, but must reconnect to publish changes. Schemas define content fields and validation rules, which Mattrbld uses to generate 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 so editors can view content updates in real time. Repository communication uses Git rather than proprietary provider APIs. The documentation names GitLab, GitHub, and Bitbucket as providers that require a CORS proxy. Mattrbld does not require its own account, though collaborators need Git-provider accounts to access private repositories or sync changes. It can be built from source and hosted as a single-page application. The maker describes it as suited to developers or agencies helping small to medium-sized clients manage website content, not as a drag-and-drop site builder.
Who it suits
Mattrbld suits developers or agencies helping small to medium-sized clients manage website content in Git. It is not a drag-and-drop website builder.
Good to know, and what to watch
- Content is kept in Git repositories, not Mattrbld’s external servers.
- Editors can work offline after importing a project.
- Schemas generate editing forms with field validation.
- Supports JSON and Markdown with YAML frontmatter.
- Can be self-hosted as a single-page application.
- Publishing changes requires reconnecting.
- Plain YAML support is planned but not implemented.
- GitLab, GitHub, and Bitbucket require a CORS proxy.
- Does not support Git LFS or scheduled publishing.
Plans
Every plan and priceOfficial hosted instance
Self-hosted core
Free plan
Getting started
- Open Mattrbld on the web or supported mobile platform
- Import a Git project
- Authenticate with your Git provider when required
- Define schemas for content fields and validation
- Configure a preview route if live previews are needed
- Publish changes after reconnecting
Limits to check
The hosted instance is free to try without an availability guarantee, and its supplied CORS proxy is intended for small-scale private projects. Mattrbld cannot schedule publishing, does not support Git LFS, and plain YAML files are not implemented.
The verdict
Mattrbld provides Git-based content editing with schemas, offline editing, and an option to self-host. Check the proxy requirements and limits around publishing and media before adopting it.
Questions people ask
Does Mattrbld require an account?
Mattrbld does not require its own account. Collaborators need accounts with the Git provider to import private repositories or synchronize changes.
Where is content stored?
Content lives in Git repositories rather than on Mattrbld’s external servers.
Which file formats are supported?
Mattrbld supports JSON and Markdown files with YAML frontmatter. Plain YAML support is planned but not implemented.
Can Mattrbld be self-hosted?
Yes. It can be built from source and hosted as a single-page application on a hosting service of your choice. The self-hosted core is free and open source under GNU AGPL.
Can editors work offline?
After importing a project, users can create and edit content offline. They must reconnect before publishing changes.
Does it support GitHub, GitLab, and Bitbucket?
Yes, Mattrbld communicates with repositories using Git. Its documentation identifies GitLab, GitHub, and Bitbucket as providers requiring a CORS proxy.
What the maker publishes
- Authentication
- Mattrbld does not require its own account, but collaborators need accounts with the Git provider and must authenticate to import private repositories or sync changes. source
- Automation
- Mattrbld cannot schedule publishing because it only runs while a user is actively using it. source
- Content storage
- Content lives in Git repositories and is not stored on Mattrbld’s external servers. source
- Credential handling
- Mattrbld says it does not store passwords or access tokens, but credentials and repository requests pass through the configured CORS proxy when one is required. source
- Data modelling
- Schemas define content fields and validation rules, and Mattrbld uses them to generate editing forms. source
- Git integrations
- Mattrbld communicates with repositories using Git rather than proprietary provider APIs, and its documentation names GitLab, GitHub, and Bitbucket as providers requiring a CORS proxy. source
- Intended users
- The maker describes it as suited to developers or agencies helping small to medium-sized clients manage website content, and says it is not a drag-and-drop website builder. source
- Live previews
- Developers can implement a preview route using Mattrbld’s protocol so editors can see content updates in real time. source
- Notable limitation
- Mattrbld does not support Git LFS and is not suited to media-heavy projects or content containing large amounts of binary data. source
- Offline editing
- After importing a project, users can create and edit content offline, but cannot publish changes until they reconnect. source
- Product
- Mattrbld is a Git-based headless CMS for creating, editing, and managing content independently of a particular frontend framework. source
- Self-hosting
- Mattrbld can be built from source and hosted as a single-page application on a hosting service of the user’s choice. source
- Supported content formats
- Mattrbld supports JSON and Markdown files with YAML frontmatter; plain YAML support is planned but not implemented. source
Checked against the maker's pages on 5 Oct 2026.