Security and compliance

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.

Read the full answer

More on this topic

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.

All questions

Still have a question left

Thirty minutes with the product team, and a straight answer.