Talk to a person, not a signup form

Single sign-on, a private routing tier, extended ledger retention and a service-level agreement — agreed in a contract rather than toggled in a dashboard.

Enterprise terms are negotiated and written into an agreement. They are not a plan you switch on from a billing page, so this page tells you what exists today, what would be contractual, and how to reach someone who can check the code before answering.

What the platform does today

• Inference runs on your own provider credential. That is enforced by a database constraint rather than policy — reversing it takes a migration and a signed resale contract.
• API keys are stored as salted SHA-256 hashes. A copy of the database yields no usable key.
• Provider credentials are AES-256-GCM ciphertext under a per-row data key wrapped by Google Cloud KMS. No read path returns key material — not to you, not to staff, not to support.
• Prompt and response content is not stored. A per-organisation logging setting exists, is off by default, and cannot be switched on in this release.
• Every hold, settlement and refusal lands in an append-only double-entry ledger that reconciles to the cent and can be exported.
• Per-key spend ceilings, model and provider allowlists, and PII redaction, applied before a request leaves us.

What is contractual, not self-serve

Single sign-on with SAML and SCIM, a private routing tier, extended ledger retention and a service-level agreement are Enterprise terms: they are agreed in a contract, and that contract governs. The Terms say it directly — Free and Team plans carry no contractual uptime commitment. We would rather state that here than leave you to infer a number from a pricing table.

For a security review

We are a Canadian company operating to PIPEDA, Quebec’s Law 25, and the Alberta and BC privacy acts. Infrastructure runs in Google Cloud’s us-central1 region. A privacy impact assessment covering transfers outside Quebec is drafted and not yet in force, and Quebec sign-ups are declined with a 451 until it is signed. These two documents are the authoritative ones:

Contact

Tell us which providers you route to, roughly what volume, and which items below your security review needs evidence for.