Licensing
Your brand. Our engine.
We don't sell to end users, and we don't compete with our partners. The engine is licensed to platforms such as e-discovery suites, public safety records systems, and FOIA processors, who embed it behind their own interfaces through our API.
From first call to production
Phase 01
Scoping
We sit down with your team, map your evidence types, volumes, and workflow onto the two pipelines, and agree on the integration surface and which model versions to pin.
Phase 02
API integration
Your engineers integrate against the unified findings schema, which is one contract for both documents and media. Sandbox access and integration support are part of the deal.
Phase 03
White-label launch
The engine ships inside your product under your brand. Your users never see the Verdictums name. What they see is your platform getting noticeably better at hard evidence.
Phase 04
Operations
Pinned versions only change when you say so. Every processed file carries its custody chain, and upgrades are opt-in, documented, and reproducible.
What partners get
- ■Full white-label: your interface, your name, your customer relationship
- ■API-first integration with one schema for all evidence types
- ■Pinned model versions and reproducibility commitments written into the license
- ■Chain-of-custody records you can export for court and audit
- ■Built-in redaction across documents, video, and audio
- ■A benchmark on your own data before any licensing commitment
POST /v1/evidence/process
{
"artifact": "production_vol3.pdf",
"pipeline": "document",
"extract": ["tables", "bates"],
"model_pin": "vd-2026.01.3"
}
// 200 OK
{
"findings": 312,
"citations": "page_line",
"hash": "7b03...e88d",
"chain": "intact"
}Licensing starts with a pilot, not a contract.
We don't ask anyone to license on faith. The seven-day pilot runs the engine against the services you use today on your hardest data first. The licensing conversation comes after the results, not before.