Policy Gateway
- Egress: default-deny by design
- Permit tickets: purpose-bound, time-scoped
- Audit channel: append-only with cryptographic proof
CHANGE THE GAME, NOT THE HARDWARE
Sovereign AI
Sovereign from Day One — plug-and-prove. Cryptographic proof. Instant control. No phone-home. No swaps.
Assurance Pathway
From Policy to Evidence.
Three enforcement controls that turn policy into verifiable evidence — on the hardware you already own.
Signed Runs
Default-Deny Egress
Local Keys Only
Governance Kernel
- Local root of trust; keys never leave the enclave
- Reproducible, signed builds (SBOM with immutable signatures)
- Policy enforcement with explainable decisions
Sovereign Agents
- In-loop attestation across Loop, Trim, and Shield
- Upgrades: isolated, signed; deterministic rollback
- Full offline parity
Access
Access Program — clear, fast, and verifiable.
Qualify once, deploy on-prem, then operate with verifiable evidence. No phone-home. No hardware swaps.
Government & critical-infra only
Local keys only
On-prem & air-gapped
Evidence-first operations
01
Qualify
- Security readiness + mutual NDA
- Procurement pack (NDA, Security Readiness, Data Processing)
- Architecture brief & classification (single executive / gov’t counterpart)
02
Deploy
- No hardware swaps; phone-home disabled
- Default-deny from Day One
03
Operate
- Evidence feed to your SIEM; alerts to existing channels
- Evidence Pack for audits/regulators on demand
Deployment options
| On-prem | Air-gapped | |
|---|---|---|
| Connectivity required | Phone-home: disabled | None |
| Keys residency | Local only | Local only |
| Upgrade path | Signed bundles | Offline signed bundles |
| Attestation | Real-time → SIEM | Local feed; batch export |
| Egress policy | Default-deny | Default-deny |
Any questions?
We’ve got you.
Tokra delivers AI-grade sovereignty on the hardware you already own: plug-and-prove. Cryptographic proof. Instant control. No phone-home. No swaps.
How does Tokra Sovereign work?
Every execution is signed and policy-bound with an append-only audit. Egress is default-deny; purpose- and time-scoped tickets open narrow paths. Keys stay local; offline parity supports fully air-gapped environments.
Do you require cloud connectivity?
No. Phone-home is disabled by default. Both on-prem and fully air-gapped deployments are supported.
Where do keys and identities reside?
Locally within your sovereign boundary. Keys never leave; signatures and identity binding are issued on-prem.
Can we integrate the attestation feed with our SIEM?
Yes. Stream append-only attestations to standard sinks (e.g., Splunk, ELK, Syslog). No vendor telemetry required.
How are upgrades and rollback handled?
Signed, reproducible bundles (offline path available) with deterministic rollback; evidence preserved (SBOM + immutable signatures).
What leaves the boundary?
Nothing unless explicitly permitted by a ticket (default-deny egress)