Access programFor engineering teamsContract is access
Build on Validiti
The docs are open. The engine is sealed. Access is by agreement.
Your team integrates the whole stack over standard, signed APIs — S3 for storage, the OpenAI API for the AI, a small signed REST surface for the rest. You get everything you need to build, and nothing that would let anyone copy what's underneath.
Why access is granted, not downloaded. The capability is real and it's yours to use — but the way it works is the whole company. So you receive keys, endpoints, schemas, a sandbox, and a sealed binary you run in your own walls. You never receive source, and you never need it: if your team can call a URL, they can build on it.
Three levels
01 · Evaluate
Prove it on your data
- Sandbox keys + base URLs
- The full developer reference
- A sealed demo you can point at real data
- No commitment
02 · Build
Integrate for real
- Development keys, version-pinned schemas
- Thin client SDKs (Python · JS)
- Engineering support
- Under a development agreement
03 · Production
Run it in your boundary
- A sealed, signed binary on your own hardware
- Your data never leaves your walls
- Production keys + SLA
- Offline-verifiable receipts
What every partner receives
API keys and your base URLs (on-prem or hosted).
Request/response schemas pinned to your version.
A sandbox to build against, plus the developer reference.
Thin client SDKs — pure HTTP, no lock-in.
A sealed on-prem binary for production — your data stays home.
Signed receipts on every response — verify offline, no call-home.
The security you're actually buying
It runs as a sealed, signed binary inside your own environment. Your data, your keys, and your queries never leave your boundary — there's no vendor cloud in the path and nothing phones home. Every answer carries a receipt you can verify yourself, later, offline. You get the capability without handing anyone your data or trusting a black box you can't check.
To request access, tell us the workload and where it runs (on-prem or hosted), and we'll issue keys, endpoints, and a sandbox. Public self-serve keys are coming soon.
Preview. This program is open to engineering teams under agreement ahead of general availability. You receive the calling surface — endpoints, schemas, receipts, examples — never the engine source or an explanation of how it works. That line does not move.