Put your AI
under authority.
Humanity remains in control. StoneAI is the control plane above your AI systems — every judgment that matters is sealed, put in front of a person, signed with a key bound to that exact content, and written to a ledger nobody can quietly rewrite. The AI recommends. A person decides. Stone holds the proof, and your systems act only on a decision that verifies. Your AI. Your rules. A safer human future.
Powerful machinery.
One set of rules.
Your AI systems are powerful machinery. Stone does not replace them; it governs them. Each system gets a role, a boundary and an escalation path, and every decision that matters passes through one authority instead of a dozen agents improvising on their own.
People set the boundaries
Your operators define what an AI may propose and who may approve it. An AI cannot widen its own lane. When it reaches the edge of its authority, it stops and escalates.
A person holds the pen
A reviewer approves or denies each decree. That decision is signed and bound to the exact content that was reviewed, so a “yes” can never drift onto something else.
A record that stands up
Anyone you hand a receipt to can verify the decision on a public page, with no account and no need to trust us.
Think of a notary. A notary does not run your business. A notary leaves a record of what was agreed, by whom, and when, that is very hard to dispute later. Stone is that notary for AI, with the notary's seal replaced by cryptography.
No adjectives.
Counted facts.
Every figure below is counted from the current codebase, and the service reports its own health in public at /status. No uptime we have not measured. No certification we do not hold.
Many seats.
One verdict.
No single model presides. Each configured model seat casts a judgment and the majority carries. The council can recommend anything. It can execute nothing.
Counted, not blended
The winning judgment is the one most seats voted for. Confidence is the mean of the winning seats, and dissent is kept on the record.
Ties never wobble
A split vote is broken by a fixed rule. The same votes always yield the same verdict.
Silence means hold
If every seat fails, the council returns hold. It never invents a verdict it did not reach.
Status — council deliberation: live. Today the live council draws on one independent model provider. Three or more independent seats: roadmap.
Sealed in stone.
Stripped of power.
Every judgment becomes a decree: reasoned, sealed with a SHA-256 content hash, and inert. It carries no credentials, no tokens and no ability to act. Change one byte and the seal no longer matches.
Example data — for illustration.
A person decides.
The signature proves it.
A reviewer marks the decree approve or deny. That decision is Ed25519-signed over the tenant, decree, approver, scope, content hash, nonce, expiry and verdict, and it verifies only against that exact decree. A decree is decided once; a second attempt is refused. Then Stone notifies your systems by signed webhook, and your systems act.
Nothing forgotten.
Nothing quietly rewritten.
Every ledger entry is SHA-256 over its tenant, event, payload and the hash before it. A per-tenant lock prevents forks. Postgres rules refuse UPDATE and DELETE. Alter one entry and every hash after it breaks in the open.
Example data — for illustration.
Public receipts
Anyone can verify a decision at /proof/:tenantId/:decreeId with no login. It checks the signature, the decree binding, the ledger entry hash and the verdict.
Hourly anchoring
Once an hour, each tenant's ledger is rolled into a Merkle root and submitted to OpenTimestamps, on a best-effort basis.
Tenant isolation
Postgres row-level security is forced on decrees, approvals, the audit ledger and billing. Tenants can be suspended and API keys revoked on the next request.
Honest status
/status reports real process data in public. No uptime percentage we have not measured. No certifications we do not hold — today, that is none.
Start free.
Pay as you govern.
Every plan, including Trial, runs the same engine: the council, SHA-256 decrees, Ed25519-signed decisions, the hash-chained ledger and public receipts. Plans differ only in volume.