Safety lives in the platform, not the prompt

Claude’s team recently wrote about commerce agents: the model can stage a change, but a person or a policy has to apply it. Checkout has no charge method the model can call. Writes only accept IDs the server issued. Safety lives in the harness, not in a paragraph of instructions.

That is the right rule for a storefront. It is the right rule for a roster, a stocktake, and a quotes app too.

The prompt is not a lock

If the only thing standing between a vibe-coded app and the internet is “please put a login on this,” you do not have a login. You have a suggestion. The next prompt, the next model, or a page of pasted text can skip it.

On Croft the app never contains the lock. Enterprise single sign-on sits in front of every app, with passkeys instead of passwords. Identity is checked at the gate, before a request reaches your code. An AI-built app cannot ship a broken login page, because it does not contain one.

Access starts locked. People see the apps you grant, nothing more. Someone leaves? Remove them once and they are out of everything.

The keys are not in the app either

The same split applies to money and customer data. If the model writes a Stripe key into the repo, the key is already gone. Connectors hold the credential on the platform. The app calls Stripe, a CRM, or email without ever seeing the secret. That is the commerce rule in plain language: the tool talks to systems you already run; it does not reimplement them, and it does not carry the keys.

Stage, then apply

A bad deploy should be reversible. On Croft every release is versioned. An update from Cursor or Claude that is not right is a one-click rollback, not a reconstruction. The model proposes. You keep the undo.

What this is not

This is not a shopping agent, and Croft is not a storefront. It is the home for the small internal app you built because a spreadsheet was never quite right. The people who use it are your people. They should sign in as themselves.

The architecture Anthropic describes for checkout is the architecture a private app already needs: the model writes the tool, the platform enforces the rules.

See how Croft hosts that →  ·  Host a Cursor app behind company login →

More from the blog