Host with us, or host it yourself
BetterCMS is headless by default, so you can pull content over the API and host the front end wherever you already deploy. Managed hosting exists for teams that would rather not run one, and it serves the pages built in the BetterCMS page builder. The two are not exclusive.
A hybrid setup keeps the marketing pages on managed hosting and hands the app or the docs to your own framework, against one content model. Whichever way a project starts, the content model is the part that does not have to change later.
- BetterCMS Cloud
- BetterCMS builds and serves the pages you compose in the page builder.
- Headless
- Your own front end renders, and BetterCMS is the content API and the editing surface.
- Hybrid
- Marketing pages on managed hosting, the app or the docs on your framework.
- Domains
- A domain belongs to a project, and a project can hold several with one primary.
How can I host a BetterCMS site?
There are two ways, and a project can use both at once. Managed hosting means BetterCMS builds and serves the pages. Headless means your own codebase renders them and reads the content over the API.
In managed hosting the page builder, the preview and the published site are one system. A marketer sees the real page before it goes live, because the thing being previewed is the thing that gets served.
In headless BetterCMS is the content API and the editing surface. Everything a visitor sees belongs to your codebase, on Vercel, AWS, Netlify, Cloudflare or anywhere else you already deploy.
- Cloud serves what you compose. Pages built in the page builder are the pages that ship.
- Headless keeps your pipeline. Your framework, your build, your deploy, one content API.
- Hybrid splits the site. Marketing pages managed, the app or the docs yours.
What does managed hosting cover?
Managed hosting takes the parts of running a site that nobody wants to own. Connect a GitHub repository and you get managed builds and previews, with forms and SEO already wired.
SSL is automatic and publishing is one click. Domains belong to the project rather than to a hosting account, so a project can hold several with one marked primary. A workspace level view rolls every project domain into one list, which is how you see what points where without opening each project in turn.
Images and files are served from the media library. An asset is uploaded once, used anywhere in the project, and images are resized and compressed before they are served from the delivery network.
Can I move off hosting later?
Yes, and that move is smaller than the one that brought you here. Content stays readable over the API and as markdown, so switching from managed hosting to your own front end changes where pages are rendered and not where content lives.
The content model does not have to change at all. Collections also export to CSV and every page has a markdown twin you can fetch, so no format on the way out can only be read by BetterCMS.
When Cloud is the wrong call
Managed hosting is worth it when the pages are page shaped and the team wants one system. It is dead weight when the front end is an application you already deploy.
Stay headless
- The front end is an application If nothing is page shaped, a page builder has nothing to build.
- You already have a pipeline A deploy you trust is not a problem that needs solving twice.
- The framework is the point Your own codebase renders, and BetterCMS stays the content API.
- Docs and app content Records read by an app do not need a canvas in front of them.
Host it here
- Pages are composed, not coded The page builder is where the marketing site is put together.
- Nobody wants to run a build Managed builds, previews and automatic SSL come with the project.
- A marketer publishes Preview and the published site are one system, so the page is the page.
- One domain list Project domains roll into a workspace view, with one marked primary.
What you get either way
The parts below do not change with the hosting decision. They are the same whether BetterCMS serves your pages or your own front end does.
-
One content API
Published content is read over HTTP by any front end, in any framework, on any host.
-
Preview before it is live
A draft is previewable on the real page rather than in a form that approximates it.
-
Assets served and resized
The media library stores every asset and serves images resized and compressed.
-
A markdown twin of every page
Clean text for an agent, and the format that makes leaving cheap.
-
Roles decide who publishes
Who may edit, who has to approve and who may publish are three separate decisions.
-
Forms without a backend
Submissions land in the project, on managed hosting and through the API alike.
Hosting questions
The five questions people ask before they choose a host. Same answers as the FAQ.
-
No. BetterCMS is headless by default, so you can pull content over the API and host the front end wherever you already deploy. Managed hosting exists for teams that would rather not run one, and it serves the pages built in the BetterCMS page builder.
-
Cloud means BetterCMS builds and serves the pages. Headless means your own front end does. In Cloud the page builder, the preview and the published site are one system, so a marketer sees the real page before it goes live. In headless BetterCMS is the content API and the editing surface, and everything a visitor sees belongs to your codebase.
-
Yes. Domains belong to a project, and a project can hold several with one marked primary. A workspace level view rolls every project domain into one list, so you can see what points where without opening each project in turn.
-
The media library stores every asset and serves images from a CDN after resizing and compressing them. You upload a file once and use it anywhere in the project.
-
Yes, and that move is smaller than the one that brought you here. Content stays readable over the API and as markdown, so switching from managed hosting to your own front end changes where pages are rendered and not where content lives. The content model does not have to change at all.
Pick a host, keep the model
See BetterCMS running on your pages, not on a sample site.