CAIN-42 · everything on one page

CAIN-42 is a Byzantine trust fabric.

The CAIN-42 Studio platform and its suite of hundreds of products, services and inventions for governing autonomous AI.

AI agents now run code, move money, touch customer data and command other agents. CAIN-42 is the runtime trust and control layer between those agents and the actions they want to take. No agent, node or software wrapper may vouch for itself: decisions and their evidence are checked and notarized by an independent Byzantine fault-tolerant quorum, so one replica can lie, crash or be compromised and the record still stands.

The CAIN-42 Studio platform

CAIN Studio is the hosted platform for the whole fabric: one account and one API key reach a suite of hundreds of CAIN-42 products, services and inventions, every one of them governed by the same decision path.

—products and features —hosted AI services, one API key —inventions catalogued from the code —pages in the evidence library —Top 100 products with live demos

Counted from the published catalogs (cain-ecosystem.json, invention-atlas.json, top100-products.json) as the page loads. Each tile opens the full list.

Live right now

—PBFT consensus cluster

—hosted AI services

—self-checks of its own code

—KEYSTONE signed fix records

—Top 100 products

Read from this site’s public routes as the page loads, and every 42 seconds after.

The rule

NO AUTHORIZATION → NO EXECUTION.

An action runs only when it carries authorization for exactly that action. UNKNOWN and ERROR never become ALLOW. Consensus notarizes the record; it can never make an unauthorized action authorized, override a policy denial or grant permission.

How a decision moves

WHO → AUTHORITY → INTENT → SECURITY CONTEXT → POLICY → RISK → TRUST → PREDICTION → DECISION → ENFORCEMENT → EXECUTION → EFFECT → EVIDENCE → CAUSALITY → COUNTERFACTUAL → OUTCOME → TRUST UPDATE → NEXT DECISION

Every decision leaves a record, allowed or refused: canonical JSON, signed with Ed25519, linked into a SHA-256 hash chain and rolled up into a Merkle root, so a changed byte anywhere is detectable.

The seven moats

The fabric runs seven trust controls on top of the quorum. Each answers one question.

1 · Trust stateWho do we trust right now?

2 · Security-context continuityDoes authority and security context survive every boundary?

3 · Trust graphHow is everything connected?

4 · Execution provenance & attestationCan we prove what actually happened?

5 · Predictive trust & blast radiusWhat could happen before we let it happen?

6 · Adversarial trust engineCan cain break its own trust guarantees, detect the failure, and contain it?

7 · Autonomous trust control loopCan verified experience continuously change future trust and decisions?

What you can use today

CAIN StudioThe hosted control plane: every agent action checked before it runs, 100+ AI services behind one API key.MCPGateThe enforcement gate in front of MCP servers, APIs and internal tools: a call goes through only with authorization for that exact action.Quorum-QaaSByzantine consensus as a service: send a SHA-256 digest, get back a quorum certificate anyone can verify offline.KEYSTONEFind the fake, fix it, prove the fix: a deterministic detector, a frontier AI fix, an independent sandboxed test, a signed record.MCPGate KEYSTONEThe same proof loop for MCP tool servers.VeriCoding KEYSTONEFormal verification closes the loop.MCP-AttestorSigned attestations for MCP servers.FALSEWORK, SCENIC, NULLIUS, SALLYPORTProve code is real, CI for agents, trust on the word of no one, and a governed runtime.Guards for agents that act in the worldPayment mandates, coding-agent supply chain, MCP tool poisoning, browser agents, drones, vehicles, robots and more.The Top 100A hundred products, each with a one-click live demo on its card.

Proof you can check yourself

CAIN-42 checks its own code every 42 secondsRe-verify the chain of checks in your browser, run FALSEWORK on your code, open KEYSTONE’s signed fixes.Verification CenterEverything about CAIN-42 you can check yourself, and how.The live PBFT clusterFour replicas in four US regions, read live.LabCrash nodes on a PBFT sandbox and verify every signature in your browser.Evidence librarySigned evidence bundles with standalone verifiers that import no CAIN code.Verify a proof offlineDrag in a bundle and check it on your own machine.ChangelogEvery change, dated.llms.txtThe same facts, for AI agents and crawlers.

Three sites, one system

cainstudio.onlineThe hosted control plane. mcpgate.onlineThe enforcement gate. clawx.clickThe public evidence.

For developers

QuickstartYour first governed agent action.DocumentationConcepts, API, SDKs, MCP and integrations.PricingSecurity is never a paid feature: every plan gets the whole decision path.FAQEvery question, answered for beginners and for engineers.Start freeNo card. A 30-day evaluation of the full platform.Book a demoSee it on your own agents.

Who builds it

CAIN-42 is built by FIRME AI in San Francisco, founded by Vincent Noriega. Read the mission. Contact: sales@cainstudio.online · security@cainstudio.online · support@cainstudio.online