The whole platform, inside your infrastructure. Local models, local processing, local storage. Same eight modules, same audit chain, same console, running where your security team can point at it.
[01 / THE PROBLEM]
In healthcare, finance, government contracting and data-sovereign outsourcing, sending recorded conversations to a hosted model is not a procurement preference. It is the thing the contract forbids.
WHAT THE REVIEW ASKS
WHAT LOCAL ANSWERS
Local is not a stripped version for buyers who cannot have the real one. It is the same platform, with the network boundary drawn where your risk team needs it.
[02 / MODULES]
All three layers deploy: the eight analysis modules, the intelligence built on top of them, and the action engines. Nothing is held back for the cloud tier.
01 · MODELS
Open-weight local models run on your hardware under our licence. There is no key to a hosted provider, because there is no hosted provider in the path.
02 · PIPELINE
Transcription, personal-data removal and the eight modules run as one local pipeline. The audit chain is written on your storage, and the export bundle is verifiable on a machine with no network at all.
03 · CONSOLE
Operator, auditor and executive. Your identity provider, your access rules, your retention. What a person sees is identical to the cloud tier, because it is the same build.
Throughput follows the hardware you give it. We publish a sizing guide against your interaction volume, and deployment automation that stands the stack up rather than a runbook somebody has to follow by hand.
[03 / THE BOUNDARY]
The honest version of an on-premise claim is a list. This is ours.
Stays. Recordings are read where they are stored and never copied outward.
Stays. Transcription runs locally, and redaction happens before any module reads it.
Stay. Weights are installed once and do not phone anywhere to run.
Stay. Scores, causes, KPIs and the signed chain are written to your database.
Come in. Signed release bundles you install on your schedule, and the licence check. Nothing else.
Support runs the same way. An engineer looking at a problem works from logs you can read first, in a session you open, with an audit entry either side of it.
[04 / THE MODEL]
A single per-agent monthly rate that covers local model licensing, infrastructure support, monitoring and patches. The rate is worked out on a call, with your own numbers on the table · the on-premise premium is stated openly there, not hidden in a line item.
One rate
PER AGENT · PER MONTH
Fixed for the contract term. No renewal escalation on Local or Enterprise.
100+
SEATS, MINIMUM
Below that the deployment work costs more than the licence returns, for both of us.
4h
SUPPORT RESPONSE
Named success manager and infrastructure support, on a 4-hour response commitment.
13+
LANGUAGES
All modules, all three layers, including the DMAIC suite. Nothing withheld.
DEPLOYMENT
Infrastructure assessment, model deployment, security review, integration, training and thirty days of hypercare. Priced against what your environment actually needs rather than as a fixed line.
SCOPED TO YOUR ENVIRONMENT · ONE TIME
COMPARED WITH BUILDING IT
Engineering, infrastructure and model deployment, before anyone maintains it. REVEAL Local runs for a fraction of that, with the maintenance inside the number · we will show you the arithmetic on your own seat count.
3-YEAR TERM · PRICE FIXED FOR THE TERM
The cloud models are Starter, Professional, Business and Enterprise. The full model table lives on the platform page, the modules are identical either way, and the price is a thirty-minute call with your own numbers.
[05 / CONSOLE]
Open the console.What you see in the hosted console is what gets installed on your side. Walk it first, then send us your sizing question.