package mainimport ( "fmt" "time" "github.com/tresorhq/attest/go/attest")func main() { releaseRoot, err := attest.LoadBundledReleaseRoot() if err != nil { panic(err) } tuple, err := attest.Verify(attest.Inputs{ Envelope: envelope, // GET /attestation BundleJWS: bundleJWS, // GET <trust_bundle_url> ReleaseRootPubKey: releaseRoot, LiveTLSSPKI: spki, // SHA-256 from live TLS Now: time.Now(), }) if err != nil { panic(err) } fmt.Println(tuple.WorkloadIdentityTag)}
Familiar API. Verifiable runtime.
Every call goes through the same path: into an attested enclave, back with a receipt you can check.
Drop in your OpenAI client
Change two lines. Keep the rest.
Set base_url to api.trytresor.com/v1 and use a Tresor API key; chat completions, streaming, and transcription work exactly as your existing SDK expects. Compatible with Python, Node, Go, and any OpenAI client lib.
Verify what's running first
See the enclave. Pin the runtime. Then send.
Fetch live attestation evidence, match it against the signed trust bundle, and pin TLS to the expected enclave so no request goes out until the destination checks out. GET /attestation. Trust bundle at /.well-known/trust.json.
Signed receipts by default
Proof attached to the request, not promised after.
Every successful call returns a receipt_id for a JWS that binds the request and response to live attestation evidence. JWS/ES256. Verify with any JWT library or the tresorhq-attest SDK.
Route on your terms
Route on purpose. Or let auto handle it.
Address compound IDs like lux/tresor/kimi-k2.5 to pin every detail, or pass auto to let the router pick from a set you've approved. Region/provider/model selection per request or per key.
Set your own failover rules
Resilience without silent rerouting.
Declare ordered fallback routes per key or per request, and the router only switches within the alternatives you explicitly named. Every failover event is recorded in the receipt and usage log.
Keys per service or team
Separate environments without sharing secrets.
Create, name, and revoke keys per service or environment, and every call carries a key_prefix so usage stays attributable. Per-key attribution in the dashboard and usage API.
Powered by frontier models.
The best of open source, isolated and verifiable in Zero-Access TEEs.
Custom contracts with negotiated rates, SLA, and compliance.
Custom
monthly commitment + overage
Negotiated model discounts
Committed spend
Metered overage
Custom rate limits
Invoice billing
SLA & priority support
Talk to Sales
API Pricing
Live route catalogue as used by current API calls.
deepseek-v4-pro
Chat
1 route available
Route ID
Input
Output
global/tinfoil/deepseek-v4-pro
$1.50/M
$5.25/M
gemma-4-31b
Chat
2 routes available
Route ID
Input
Output
eu/privatemode/gemma-4-31b
€0.77/M
€1.27/M
global/tinfoil/gemma-4-31b
$0.45/M
$1.00/M
glm-5.2
Chat
1 route available
Route ID
Input
Output
global/redpill/glm-5.2
$1.40/M
$4.40/M
gpt-oss-120b
Chat
2 routes available
Route ID
Input
Output
eu/privatemode/gpt-oss-120b
€0.43/M
€1.70/M
global/tinfoil/gpt-oss-120b
$0.15/M
$0.60/M
gpt-oss-20b
Chat
1 route available
Route ID
Input
Output
global/redpill/gpt-oss-20b
$0.04/M
$0.15/M
kimi-k2.6
Chat
3 routes available
Route ID
Input
Output
eu/privatemode/kimi-k2.6
€1.55/M
€7.74/M
global/chutes/kimi-k2.6
$0.95/M
$4.00/M
global/tinfoil/kimi-k2.6
$1.50/M
$5.25/M
llama3-3-70b
Chat
1 route available
Route ID
Input
Output
global/tinfoil/llama3-3-70b
$1.75/M
$2.75/M
mistral-24b-uncensored
Chat
1 route available
Route ID
Input
Output
global/redpill/mistral-24b-uncensored
$0.20/M
$0.90/M
qwen-2.5-7b-instruct
Chat
1 route available
Route ID
Input
Output
global/redpill/qwen-2.5-7b-instruct
$0.04/M
$0.10/M
qwen3.5-27b
Chat
1 route available
Route ID
Input
Output
global/redpill/qwen3.5-27b
$0.30/M
$2.40/M
voxtral-mini-3b
Transcription
1 route available
Route ID
Input
Output
eu/privatemode/voxtral-mini-3b
—
€0.0040/min
voxtral-small-24b
Transcription
1 route available
Route ID
Input
Output
global/tinfoil/voxtral-small-24b
$0.20/M
$0.60/M
whisper-large-v3
Transcription
1 route available
Route ID
Input
Output
eu/privatemode/whisper-large-v3
—
€0.014/min
whisper-large-v3-turbo
Transcription
1 route available
Route ID
Input
Output
global/tinfoil/whisper-large-v3-turbo
—
$0.010/req
API Questions
Privacy without the trade-off.
Public AI tools read everything you send. On-prem is private but impractical. Tresor gives you both: cloud convenience, infrastructure-grade privacy.
Powerful Models
Public Cloud AI
On-Prem
Tresor AI
EU-hosted
Public Cloud AI
On-Prem
Tresor AI
Zero-Access
Public Cloud AI
On-Prem
Tresor AI
No Ops
Public Cloud AI
On-Prem
Tresor AI
No Setup
Public Cloud AI
On-Prem
Tresor AI
Verifiable Proof
Public Cloud AI
On-Prem
Tresor AI
Capability
Public Cloud AI (ChatGPT, Claude, etc)
On- Prem
Tresor AI
Powerful Models
EU-hosted
Zero-Access
No Ops
No Setup
Verifiable Proof
Trusted by people who don't trust easily.
I can only use AI in coaching when it fully protects the sacred trust between practitioner and client; confidentiality is non-negotiable.
Tove Thyes
Transformational Coach and Energy Medicine Practitioner
As a software strategist, I treat privacy as the blueprint that lets my team turn client visions into AI people can trust.
Igor Miazek
CEO & Founder, Techs
At Dance, we build experiences people trust. Tresor’s approach to privacy-first AI is a simply a great match.
Christian Springub
CEO & Co-Founder, Dance
As a therapist, I can only use AI that protects client privacy. Tresor delivers exactly that.
Magali Cahen
Psychologist and Therapist, Independent
The only way to earn trust in AI is to make privacy a design principle, not a feature. Tresor’s system does exactly that.
Ingmar Schuster
CEO & Co-Founder, Provolut
In the AI era, rigorous risk-based security and GDPR-aligned privacy are non-negotiable foundations for any trustworthy system.
Davy Cox
Founder, Brainframe
Understand the technical details.
Zero-Access AI Conversations: How Tresor Protects Your Privacy
Executive Summary
Tresor is built on a simple promise: your conversations belong to you, not us. Every
message you type is protected by end-to-end encryption and processed only inside secure
computing environments that even Tresor cannot inspect. Teams can now collaborate
inside shared workspaces without ever handing Tresor access to their plaintext. This
whitepaper explains the principles and safeguards behind Tresor’s zero-access design,
showing how we deliver practical confidentiality without trade-offs in usability.