Deployment
Your perimeter, your keys, your jurisdiction.
If a platform only works when your data sits in a vendor cloud, it does not work for most of the agencies we build for. Every deployment model below is a first-class target, not a downgrade path.
Deployment models
Air-gapped
The full suite installed inside a network with no external connectivity. Collection runs through a controlled diode or scheduled transfer; updates ship as signed offline bundles.
Typically
Security and intelligence services, classified environments
On-premises
Your hardware, your data centre, your keys. Outbound collection egresses through infrastructure you control and can inspect.
Typically
Law enforcement, national agencies, regulated financial institutions
Sovereign cloud
Deployed into a cloud region and tenancy you nominate, under your own cloud account where required. Data residency is contractual, not best-effort.
Typically
Agencies with a mandated national cloud, corporate security teams
How an engagement runs
Scoping
We map your sources, your legal authorities, and the environment we will deploy into. This is where air-gap constraints and data-residency rules get written down.
Pilot
A bounded deployment against a real caseload, with your analysts using it. Success criteria are agreed before it starts.
Production
Full deployment, integration with your existing systems through the REST APIs, and operator training.
Sustainment
Signed update bundles, source-adapter maintenance as collection targets change, and a named engineering contact.
On timelines and pricing
We do not publish a deployment time or a price list, because neither is honest without knowing your environment. An air-gapped installation with three custom source adapters and an accreditation review is not the same project as a sovereign-cloud pilot for one team, and quoting a single number for both would be marketing rather than engineering. Scope with us and you get a real schedule.
Start a scoping conversation