Features

Content teams model it themselves.

Collections and maps, with the fields you actually need, designed in the interface the way you think about content. No ticket, no deploy, no waiting on another sprint.

A collection is a table: entries are rows, the fields marketing added are columns, and everyone editing it can see everyone else.

How it works.

Collections and maps
A collection holds many entries that share a shape: posts, case studies, authors. A map is a single entry on its own: a landing page, your site settings. Both are made in a couple of seconds, and named and renamed in place.
Twelve field types
Text, rich text, number, checkbox, date, select, multi-select, link, person, asset, reference and multi-reference. Enough to describe real content, few enough to choose between without reading a manual.
A table, not a form
Entries are rows and fields are columns, so a whole collection is scannable and editable at once. Adding a column is adding a field, and it is available to your app immediately.
Written together
Live cursors in the table and in the body. Two people on the same entry see each other rather than overwrite each other, and every change is saved as it is made.
Comments on the words
Discussion is attached to the sentence it is about, not filed in a separate tool where it loses its subject.
Publishing is yours to shape
Stet serves what is saved. Drafts, review states and scheduling are a field on the model and a branch in your app, so the workflow is the one your team actually uses rather than the one a CMS assumed.

Adding a field is picking its type. Twelve of them, available immediately.

Rich text edits on a page of its own, with live cursors and comments anchored to the sentence they are about.

Stop making one team wait for the other.

Model your first collection in a couple of minutes, or have us walk you through it first.

$10 per user per month. Free to self-host.