FAQ
Frequently asked questions
Straight answers on cost, migration, security, hosting and the AI agent. Pick a topic to narrow the list, or open a topic page to read the whole conversation in one place.
42 questions
Getting started
5 questions
Setting up a workspace, the first site, and what you need before you begin.
-
How do I get started with BetterCMS?
You create a workspace, pick a template or start from an empty content model, then invite the people who will publish. Everything runs in the browser. No local install and no build pipeline stand between you and a first page on a real URL, because the editor, the content model and hosting are parts of one product rather than three decisions.
If a site already exists somewhere else, start with the Migrator instead of a template. It maps an existing schema onto BetterCMS collections and brings entries and assets across with it.
-
Do I need a developer to set up BetterCMS?
No. A marketer can create a workspace, choose a template, and publish a page without a developer. A developer is needed for three things: a custom content model designed in the schema builder, a front end built on your own framework, and pulling content through the API into an application you already run.
-
How do I see BetterCMS before I commit?
Request a demo and the product team walks through BetterCMS on a call using content shaped like yours, not a sample site. Thirty minutes is the usual length. If reading suits you better, the comparison pages set BetterCMS against Webflow, WordPress, Contentful, Sanity, Payload, Storyblok and Framer, with the rows BetterCMS loses left in.
-
What do I need before I start?
You need your content, a domain, and a decision about who is allowed to publish. Content can arrive as an export from your current CMS, pasted in as markdown, or typed straight into the editor. The domain can be attached later, so waiting on DNS does not hold up the first page.
-
What does a BetterCMS project contain?
A project holds one site: its content model, its pages, its collections, its media and its domains. Each project has its own Site plan. A workspace holds several projects, and members, billing and roles sit on the workspace. A team running one marketing site and one docs site keeps them as two projects under one workspace, with a Site plan for each and its people paid for once.
Pricing and plans
5 questions
What BetterCMS costs, how Workspace members are billed, and how the bill compares.
-
How much does BetterCMS cost?
BetterCMS has a Free plan at $0, then Starter at $20 a month and Pro at $99 a month for each website, and Enterprise on a custom annual contract. Billed yearly, Starter is $18 a month and Pro is $89, saving up to 10%. Every Workspace member is $15 a month whatever their role. A three person team running one small marketing site on Starter pays about $48 a month all in on yearly billing: the $18 plan plus two members at $15, because the owner is included. On monthly billing it is about $50. These are list prices and the competitor figures elsewhere on this site were checked in July 2026.
The bill has two layers. Each website has its own Site plan, and the Workspace carries the people. Adding a second website therefore means another Site plan and not a second set of members.
-
Is BetterCMS cheaper than Webflow?
Yes for a three person team, and the gap narrows as the team gets smaller. That team, on one small marketing site, pays about $48 a month billed yearly on BetterCMS and about $113 to $128 a month on Webflow, billed yearly. The gap widens if you want an AI agent, because Webflow puts its AEO agents on the Team plan at $2,500 a month on an annual contract while the BetterCMS agent ships on self serve plans. The gap closes to nothing if you need one seat and a brochure site. Every Webflow figure here was checked in July 2026.
-
What counts as a Workspace member?
A Workspace member is anyone you add to your Workspace to work on your websites, and every member is $15 a month whatever their role. There is no role-based seat pricing, so an admin, an editor and a reviewer cost the same. Every account starts in a Personal Workspace with one owner included, so the first person is free and each person after that is $15. Members are billed on the Workspace rather than on each Site plan, so someone who works across three websites is one member and not three.
-
What can I add on to a plan?
Five add-ons are available, each per website and charged monthly: an extra locale at $8 a month, 500 more AI credits at $8 a month and 1 million more API requests at $5 a month on Starter or Pro, plus 100 GB of extra storage at $5 a month and 250 GB of extra bandwidth at $20 a month on Pro. Packs stack up to each plan limit, are not discounted on yearly billing, and are only added after you approve the new price. Workspace members are separate, at $15 a month each. Add-ons are available on paid plans only, not on Free.
-
Can I change plan later?
Yes. Each website has its own Site plan, so one website can move up or down without touching the others, and member counts change as the team does. Both change from the workspace billing page and take effect on the next bill. If you move down, your content is never deleted. Projects can also move between workspaces, and a project resets to the receiving workspace plan when it lands, so a transfer never carries an old price into a new account.
Migrating
5 questions
Moving content, files and URLs off the CMS you have now.
-
Can I move my content from another CMS?
Yes. The Migrator maps an existing schema onto BetterCMS collections and brings entries and assets across with it. WordPress, Contentful and Sanity have direct paths, and any source with an export file or an API can be mapped through the same tool.
The mapping step is the part worth slowing down for. A field that lands in the wrong place costs minutes to fix on day one and days to fix after a thousand entries have been written against it.
-
Which platforms does the Migrator cover?
WordPress, Contentful and Sanity have direct paths through the Migrator. Everything else goes through the same mapping step using an export file or the source platform API, which is how sites arrive from Webflow, Storyblok, Framer and hand built systems. The comparison pages set out what actually changes when you move from each one.
-
What happens to my page paths?
Page paths stay under your control, because a path is a field on the page rather than something the CMS derives from the title. Decide before the move which paths have to change and which do not. A path that moves twice loses its accumulated links twice, so it is worth getting right once.
-
Do images and files come across?
Yes. Assets move with their entries into the media library, which stores and organizes them and serves images from a CDN after resizing and compressing them. You upload a file once and use it anywhere in the project.
-
What does a migration not bring?
Theme code, plugins, and anything a plugin kept in its own tables do not come across. A WordPress site leaning on a dozen plugins is not one export. It is a decision about which of those twelve behaviours the new site genuinely needs. Content, media and structure move. Bespoke template code does not.
Developers and API
5 questions
Frameworks, the content API, the schema builder, the CLI and MCP.
-
How do developers work with BetterCMS?
Developers work with BetterCMS through its content API, its SDKs, a CLI and an MCP server, and shape the content model in the schema builder. BetterCMS is headless by default and serves content to any framework over the API. It also ships a page builder, so a team that wants one tool can stay inside it rather than build a front end first.
The split most teams settle on is that a developer owns the content model and the components, and a marketer owns the pages composed from them.
-
Which frameworks does BetterCMS work with?
Any framework that can call an HTTP API works, and Astro and Next.js have first class paths. A headless setup pulls content into your own build. A hybrid setup keeps marketing pages in the BetterCMS page builder and hands the app or the docs to your framework, against the same content model.
-
Is there an API and are there SDKs?
Yes. Every content type defined in the schema builder is readable over the API the moment it exists, with no endpoint to write by hand. SDKs wrap the same API for the common frameworks. API keys are issued per project and the key is shown once at creation, so a leaked key is replaced rather than recovered.
-
Can I define the content model in code?
The schema builder is visual, and its output is a JSON schema you can read, diff and copy from a live panel next to the model. Fields, groups, relationships and validation rules all live there. Changing a model does not require a migration step, so a field added on Tuesday is queryable on Tuesday.
-
What is the MCP server for?
The MCP server lets an AI coding assistant read and change BetterCMS content through the same tools a person uses. An assistant inside your editor can look up a content model, draft an entry, or propose a change without anyone copying content between two windows. The CLI covers the same ground from a terminal.
AI and agents
5 questions
What the agent does, what it may never do, and who controls the budget.
-
What can the BetterCMS agent do?
The BetterCMS agent proposes changes across many documents at once and hands each one back for review, field by field, with undo. A rename that touches forty entries is one run and one review rather than forty edits. The agent works inside the same roles, approval stages and audit log a person does.
The agent also drives the page generators: a set of SEO pages from a keyword list, or one account based page per target company. Both arrive as drafts and go through the same review as anything else.
-
Can the agent publish without a human?
No. The BetterCMS agent never publishes on its own. Every change it proposes waits for a person to approve it, and each field shows its before and after so the approval is informed rather than one blanket yes. Undo is available afterwards as well, per document.
-
How do I keep the agent on brand?
Two things steer the agent: the brand kit and the workspace instructions. The brand kit holds the tokens, the voice and the rules a page has to follow. Instructions are a workspace library of skills and rules written in markdown, and a run streams the line that says how many it is following, so you can see which ones applied. A project can opt out of an instruction it should not inherit.
-
Can a workspace admin limit what AI costs?
Yes. A workspace admin sets a monthly AI budget and a hard ceiling above it, and can switch individual skills and generators off for everyone in the workspace. The limits are enforced when a run starts rather than reported after it finishes, and a disabled skill shows as disabled in the interface instead of failing halfway through.
-
Can I bring my own model key?
Bring your own key is a workspace level switch, so a team with its own model contract can run the agent on it. External model access is a separate switch beside it. Both are off until someone with the right role turns them on, and both sit on the same page as the budget and the skill toggles.
Security and compliance
5 questions
What is protected, what is logged, and the certificates BetterCMS does not hold.
-
How is my content kept safe?
Content is encrypted at rest and in transit, backed up automatically, and every change is written to an audit log you can read. Access is governed by roles that reach down to the individual field, so who may edit, who has to approve, and who is allowed to publish are three separate decisions rather than one permission.
The same rules cover the AI agent. It holds a role, it works inside that role, and its runs appear in the audit log beside everyone else.
-
Is BetterCMS SOC 2 certified?
No. BetterCMS holds no SOC 2, no ISO and no HIPAA certificate today, and we will not describe it as enterprise grade until those exist.
It does ship what a large team asks for functionally: single sign on, field level roles, audit logs and approval workflow. Whether that is enough depends on whether your blocker is capability or paperwork. If a security team is the buyer and a certificate is the gate, BetterCMS does not clear it yet.
-
Who on my team can see and change what?
Roles decide it, and a role can be scoped down to an individual field. The built in roles are admin, developer, marketer, editor and reviewer, and custom roles narrow the permission set further. A reviewer comments and approves without edit rights. Roles change what a member can do and not what a member costs, because every Workspace member is the same $15 a month.
-
Can I see who changed what and when?
Every change is written to an audit log and every version is kept for your plan history window, which is 7 days on Free, 90 on Starter and 365 on Pro. Compare places two versions side by side with a word level diff, and a single field can be restored on its own rather than rolling the whole document back. Agent runs are recorded the same way a person edit is.
-
Can I get my content out again?
Yes. Content is readable over the API, collections export to CSV, and every page has a markdown twin you can fetch. No format here can only be read by BetterCMS, which is the honest test of whether a CMS is a lock in.
Hosting
7 questions
Managed hosting, headless, hybrid, domains and how files are served.
-
Do I have to host my site with BetterCMS?
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.
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.
-
How is Cloud different from headless?
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.
-
Does traffic to a Cloud site use my API requests?
No. On managed hosting a visitor asks BetterCMS for a page and is served HTML from the CDN. Nothing in that path is a Content API call, so nothing is metered. The monthly API allowance counts uncached Content API requests, which means the calls your own code makes, not the pages we render and serve for you.
That is why a Cloud site’s usage tracks how often you publish rather than how much traffic it gets. A day with a hundred visitors and a day with a hundred thousand cost the same.
-
Do the editor, the CLI and the MCP server use my API requests?
No. The allowance is for production reads from your own front end. Editing in the Visual Editor, opening a draft preview, running the CLI, regenerating types with bettercms-codegen and driving the MCP server are workspace tools rather than visitor traffic, and they are not counted against it.
The per-second rate limit is a separate thing and does apply to every caller, tools included. It protects the service from a burst, which is a different problem from a monthly total.
-
Can I use my own domain?
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. A Free site runs on a BetterCMS subdomain, and a custom domain starts on the Starter plan.
-
How are images and files served?
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. Organizing stays in the library rather than in a shared drive nobody maintains.
-
Can I move off BetterCMS 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.
Publishing and workflow
5 questions
Drafts, approval stages, versions, locales, and two people on one page.
-
How does publishing work in BetterCMS?
A page stays a draft until somebody with publish rights publishes it from the publish menu. Workflow stages sit in front of that gate, so a page can be required to pass review before the publish action is available at all. Every publish is versioned, and any version can be restored.
Pages, collection entries and standalone markdown files all follow the same draft and publish lifecycle. That is one rule to learn rather than three.
-
Can I require approval before a page goes live?
Yes. Workflow stages gate publishing, and a page moves through them on a board that shows what is waiting on whom. A reviewer approves or requests changes, and the person who asked is notified either way. Every Workspace member is the same $15 a month whatever their role, so an approver costs no more than an author.
-
Can two people edit the same page at once?
Yes. Editors work side by side with live cursors, comments and field locking, so two people on one page see each other rather than overwrite each other. Avatars appear on the field somebody is in, on the row in a list, and on the section in the visual editor.
-
Can I go back to an earlier version?
Every publish makes a version, versions are kept for 7 days on Free, 90 on Starter and 365 on Pro, and any version in that window can be restored. Compare puts two versions side by side with a word level diff, and a single field can be restored on its own rather than rolling the whole document back to an older state you did not want.
-
Can I publish in more than one language?
Yes. Free includes one locale, Starter two and Pro five, and an extra locale is $8 a month per website. Translate inside the editor and publish each locale on its own schedule from the same content model. One model serves every locale, so a field added once reaches all of them.
No questions in that topic yet.
Still have a question left
Thirty minutes with the product team, and a straight answer.