Prove it
The evidence page
Our platform classifies every document by how much it should be trusted. We apply the same standard to ourselves: every operational claim below is backed by a versioned artifact — a test run, a drill record, a policy file, or a refused deletion. Under NDA, we will show you any of them.
| Claim | Backed by | Verified |
|---|---|---|
| Full integration suite passes against both live regions (US, Mexico) | 70/70 checks, run in-cluster against the live US and Mexico deployments | Jul 2026 |
| Database restore is drilled, not assumed | PostgreSQL restore RTO measured at 21 seconds, 36/36 tables; MongoDB 4/4 collections — recorded drill notes | Jul 16, 2026 |
| Off-site backups are immutable (WORM), verified adversarially | Time-based retention policy locked; verified by an attempted blob deletion being refused by Azure ("blob is immutable due to a policy") with the blob still present | Aug 5, 2026 |
| Edge rate limiting works under attack conditions | Smoke test drove 120 requests; 21 correctly rejected with HTTP 429 at the edge | Jul 16, 2026 |
| No application code contains a hardcoded model name | All inference flows through capability-tier aliases; verified by repository-wide search — zero live call sites reference a vendor model | Aug 2026 |
| Model changes are gated by an executable evaluation contract | CI blocks any inference-binding change unless the eval harness passes: required tiers present, fallback chains legal, embedding dimensions pinned | Jul 2026 |
| Truth-value retrieval behaves as designed, as an executable test | A superseded document at 0.95 raw relevance ranks below a current authoritative document at 0.70 — and remains retrievable at a non-zero floor. Demotion, never silent deletion. | Aug 5, 2026 |
| Authoritative status cannot be machine-assigned | The classifier is structurally incapable of producing the highest truth class; promotion requires an authenticated human, a written reason, and an append-only audit record | Aug 5, 2026 |
| Tenant isolation is enforced by policy, not convention | Vector search filters are injected server-side keyed to the verified token; policy requires token tenant to equal tool tenant; effective clearance is the maximum of caller and document — a commercial caller cannot unlock a restricted document | Jul 2026 |
| Production state is answerable from a git log | All first-party images deploy by content digest, not tag; the deployment mechanism is a reviewed git commit, and rollback is a revert | Aug 3, 2026 |
| A full vector-store rebuild from source is an operational routine, not a crisis | 161-document corpus re-embedded and re-indexed from durable source storage in approximately 7 minutes with zero failures | Aug 9, 2026 |
| Prompts are not retained in our spend logs | Inference gateway persists usage accounting with prompt storage explicitly disabled in configuration | Aug 2026 |
What we have not done yet
An evidence page that only lists wins is a marketing page. These are the things we are candid about with every investor and design partner:
- SOC 2 is a roadmap item, not a certification we hold. Our compliance posture is designed to support formal audit; the audit itself has not been engaged.
- Zero Data Retention on Azure requires Microsoft approval we do not yet have. Today we operate under Microsoft's standard no-training commitment (contractual, documented) — which is strong — and we say exactly that, not more.
- We are onboarding design partners, not self-serve customers. Signup requires human approval by design. Usage-based billing is under construction; early partners get flat, simple terms.
- High availability is a build-out in progress. Early deployments run lean; our recovery posture (measured restore times, immutable off-site backups) is how we manage that honestly today.
If any of this changes your decision, we would rather you know now. If the candor itself is what you were looking for — talk to us.