Pilot program
Prove Verity on your AI workflow.
A focused two-to-four-week pilot to test Verity on your real use case, with a dedicated deployment, clear success criteria, and a detailed report. For teams running customer-facing chatbots or internal copilots who need evidence — not a sales deck — before committing.
What you get.
Your own Verity instance — not a shared tenant. Your database, your keys, your traces, isolated from other customers by architecture.
Your business rules, modeled as policy and enforced on requests and responses — the refund ceilings, prohibited offers, and data your bot must never touch.
Real results: blocked attacks with examples, false positives found and fixed, policy and judge verdicts — written by the founder from your traces.
At the end, a review against the success criteria agreed up front, stated plainly: what Verity caught, what it missed, and what it would take to close the gaps.
How the pilot works (2–4 weeks).
We discuss your use case, policies, and risks — and decide together whether a pilot makes sense.
What "works" means on your traffic, including a false-positive budget measured on your real support questions.
Your dedicated deployment is configured with your policies, then passes a fixed verification battery — key enforcement, attack and policy blocks, your benign questions answered — before any traffic flows.
Traffic flows through Verity; false positives are tuned via a human-reviewed corrections loop, with a report each week.
Decide to continue, extend, or stop — based on evidence, measured against the criteria from step 2.
· Traces stored in your dedicated database
· Automatically deleted after 30 days (pruned on an ongoing basis; full deletion at pilot end, confirmed in writing)
· Never used for training — attack patterns are paraphrased and human-reviewed first
· Your provider key stays yours, entered only into your deployment's settings
· Not an authorization system (see your own stack) — permission-check sensitive actions in your backend
· Streaming not supported yet — responses return complete
· Founder-led support (no 24×7 SLA)
· Early-stage product — the pilot exists to prove it on your traffic
What happens when the pilot ends: convert to a monthly engagement, extend once, or stop — in which case your deployment and data are deleted as described above and your traces can be exported to you first. Removing Verity is also one line: the same base-URL change, reversed.
Request a pilot.
Tell us about your use case and we will get back to you for a scoping call. The founder reads every request personally and replies within two business days.
Request recorded.
Your reference is —. The founder will reply to your work email within two business days. Your details are stored in Verity's database, read only by the founder, and never shared or added to a mailing list.
Just evaluating for now? Create a free account and test the gateway with your own key.