Security · how we build it
Hardened on purpose.
We govern the most dangerous actions in your stack, so our own posture has to be the strongest thing we ship. Tenant-scoped signing keys with no cross-tenant surface. Connectors that verify and fail closed in the target system. A cryptographically signed and replayable audit chain — per-tenant public-key (JWKS) verification is live. A CycloneDX SBOM generated in CI. SOC 2 Type II in progress. Single-tenant deployments for sensitive workloads.
01 · Posture
02 · The unit of authority
The token is the security boundary.
Every guarantee reduces to a single artifact. An Authority Token is Ed25519-signed with a tenant-scoped key, bound to the exact proposed action by an intent hash, short-lived, and single-use. The connector verifies all of it locally against the pinned tenant signing key — so a missing, malformed, expired, or replayed token is refused at the boundary, not somewhere upstream where a network blip could fail open.
1// An Authority Token is a self-describing, verifiable artifact. 2{ 3 "alg": "EdDSA", // tenant-scoped Ed25519 key 4 "intent": "OI-104", // canonical Open Intent code 5 "intent_hash": "sha256:…", // binds the exact proposed action 6 "env": "production", 7 "exp": 1730000000, // short TTL — minutes, not hours 8 "jti": "…", // single-use; replay refused at the gate 9 "kid": "…" // pins the tenant signing key for verification 10}
03 · How decisions are protected
Tenant-scoped · rotatable
Each tenant gets isolated Ed25519 keys with a 90-day rotation default; rotate on demand. There is no cross-tenant signing surface — one tenant’s compromise cannot mint another’s tokens.
Hash-linked · replayable
The audit chain is content-addressed and exportable. Decisions are cryptographically signed and replayable; per-tenant public-key (JWKS) verification is live. Tamper-evident by construction.
Fail-closed at the boundary
Connectors verify the token themselves. If anything is off — signature, TTL, intent hash, revocation — the action is refused there, in the target system. There is no default-open fallback.
security@intended.so
Coordinated disclosure, acknowledged within 2 business days. Read the disclosure policy before you file.
Disclosure policy →04 · Isolation & supply chain
Single-tenant where it matters; an SBOM you can read.
For regulated workloads the control plane runs single-tenant: an isolated runtime, your own signing keys, and no shared verification surface. Sovereign and air-gapped operation is in design with enterprise partners (the in-cluster stack and zero-egress controls are built). On the supply-chain side, we generate a CycloneDX SBOM in CI — available on request — so you can inventory exactly what runs in the path of a decision. The fail-closed model means the worst case for an Intended outage is that nothing gets a token — the gate refuses, rather than waving actions through.
no token, no action, and the token verifies locally against the pinned tenant key. If Intended disappeared, your gate stays closed and your existing signed receipts still stand. Per-tenant public-key (JWKS) verification is live.- Cloud. Every authority token is verified against Intended’s ledger, is single-use globally, can be revoked instantly, and expires within 5 minutes.
- Self-host / BYOC. Tokens are verified entirely inside your perimeter with no call to Intended; each token is single-use within the gate that consumes it, expires within 60 seconds, and is revocable within one revocation-list pull interval.
- Air-gapped. Tokens are verified with only a public key and a clock, with no network of any kind; replay and revocation are bounded by a short time-to-live (≤60s) that you control.