Production governance

Production governance is the human side of an AI-era Backend Platform. Agents can model and publish. People still decide what is production, who may approve it, and which keys are allowed to move it.

The failure mode is an agent with an unbounded secret. It can delete a schema, publish draft, or write outside the site you intended. Scoped agent keys, org/multi-site boundaries, and a UI that is clearly “human” exist to keep that from being the default.

LUNO splits the question into two pages. Security asks whether you can hand the backend over at all — edge runtime, access, posture. Enterprise asks whether it works at org scale — many sites, scoped authority, a real sales path.

Governance is not an enterprise feature pack glued onto a CMS. It is the reason the category is a platform: one record, two operators, one trail. If those three diverge, you are back to rebuilding backends and explaining them after the fact.

Start on Free to see the surfaces. Talk to sales when SSO-class access, agency orgs, or a written review are the gate. The console stays open either way — governance should not mean “wait for a quote to try.”

Publish is backend state — models, forms, content. Ship is frontend release. The agent may publish. The human governs production authority and what ships.