Built to pass your security review
Inference runs on your own provider connections. We see metadata, not your data.
- No AWS keys required
- Content off by default
- Every access in your audit trail
- Revocable anytime
Your AWS account
Amazon Bedrock
Inference runs here
Your audit trail
Every access by us
Your S3 + KMS
Content, if you opt in
Metadata only
cost · tokens · latency · attribution
Prompts and responses
off by default · opt-in, redacted
Revocable role
scoped to Bedrock
Open Token
Dashboards, alerts, attribution
Trust, at a glance
Encryption
AWS KMS at rest, TLS in transit.
SSO and SCIM
Your identity provider.
Audit trail
Every access, in your own AWS logs.
Data residency
US East; São Paulo on request.
Web application firewall
AWS WAF in front of the site and API, with rate limits.
Fail-open
Monitoring never blocks your traffic.
- Usage metadata
- 13–25 mo
- Content
- Off
- Traces
- 14–400 d
- Audit log
- 1–7 yr
Retention
You choose, per project.
Compliance and controls
Tenant isolation
Covered by automated tests in CI.
DPA and subprocessors
On request.
Deployment in your account
On Enterprise.
Your own storage
Spans and content in your S3.
Your own keys
Encryption with your KMS.
Evidence packs
Signed, audit-ready.
Verify an evidence pack
Anyone can check a pack came from us and nothing in it changed.
Match the key
The pack's key ID matches the one here.
Check the signature
Our public key confirms the signed checksum list.
Check every file
Each file matches its signed checksum.
Our signing key
- Algorithm
- Ed25519
- Key ID
- e0299fcec9230024018ac55e01519e24
- Full fingerprint (SHA-256)
- e029 9fce c923 0024 018a c55e 0151 9e24 bbca e65e 3b37 a16b 6024 20b1 2bae 4225
The key ID is the start of the fingerprint.
How access to your AWS account works
You create a role scoped to Amazon Bedrock that only Open Token can assume. Access is temporary and tied to your organization; delete the role and it ends immediately. With a role you never give us long-lived AWS keys. If you prefer a Bedrock API key, or connect another provider, the key is stored encrypted and never shown again.
What we store, and for how long
Model, tokens, cost, latency and attribution for each call; cost aggregates for 13 to 25 months by plan. Traces for 14 days, extendable to 30, 90 or 400. Prompts and responses only if you opt in, redacted, for 14 days or your retention. Audit log for one year (up to seven on Enterprise).
Encryption and isolation
TLS in transit and AWS KMS encryption at rest, bound to your organization. Every data access is scoped to your organization, with automated tenant-isolation tests in CI.
Compliance
We share our security questionnaire, data processing agreement and list of subprocessors on request. Evidence packs include a mapping aid to SOC 2, ISO/IEC 27001 and EU AI Act references for your auditor. It is not a certification.
Who on your team sees what
Owners and Finance always see every team. Admins, Developers and Viewers can be limited to specific teams, and to environments, when you invite them and later on Members. Once limited, they see only those teams' projects, and a limited admin manages only those teams' projects and their Developers and Viewers, not company-wide settings or billing. An invitation email has a one-time link to set a password, valid for 7 days, and does not include a password. The inviter sees a temporary password once on screen, to pass on if the email does not arrive. A pending member's name, email and role can be corrected, and the invitation sent again, without adding them a second time.
See your AI spend the way finance does
Accounts are set up by our team. Tell us which model providers you use and we'll walk you through a live workspace with your own numbers.