The project Activity feed as a single timeline rail running off the lower edge, each row carrying the person, what they did, the event key the log filed it under and the time, with one failed webhook delivery marked Activity TODAY Maya Flores published /pricing Deploy hook returned 502 after 3 attempts Tomas Reed moved Jon Ivers to Editor Agent run applied 7 changes to /docs/api entry.published member.role_changed agent.run_applied webhook.delivery_failed 14:02 13:41 11:20 09:58

Your stack. Your rules. Everyone moves faster.

What the log records

  • Every mutating action

    Projects, pages, entries, collections and components. Media, members, invitations, roles, keys and domains.

  • One action dictionary

    About seventy dotted keys, each mapped to English. An action reads the same wherever it turns up.

  • Six sources, one feed

    Builds, webhooks, publishing, access, agent and search. The source is a filter, not a page of its own.

  • Rows you can open

    An actor, an action, a target and an outcome. Expand a row for the details behind it.

  • Search, filter, export

    Search the feed or show only the calls that failed. Page through the result and export it to CSV.

The questions we get asked

Short answers on migration, models, roles, and uptime.

  • BetterCMS is headless by default and serves content over an API to any framework. It also ships a page builder, so teams that want one tool can stay in it.

  • The Migrator API maps an existing schema onto BetterCMS collections and brings entries and assets with it. WordPress, Contentful, and Sanity are covered.

  • 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.

  • There is no cap. Build models in the schema builder with your own fields, relationships, and validation rules, and change them without a migration.

  • The media library stores and organizes every asset. Images are resized, compressed, and served from a CDN, so you upload once and use the file anywhere.

  • Yes. Editors work side by side with live cursors, comments, and field locking, and every version is kept for your plan history window, 7 days on Free, 90 on Starter and 365 on Pro, so you can roll back to an earlier draft.

  • Set custom roles down to the field. Decide who can edit, who has to approve, and who is allowed to publish, then apply the same rules to your agents.

  • Content is encrypted at rest and in transit, backed up automatically, and every change is written to an audit log you can read.

Ask the log who did what

Content OS for modern websites.