Sovereign compute placed inside the jurisdiction it serves
Public bodies increasingly need inference capacity that demonstrably stays within their own borders, without committing to a multi-year capital program to obtain it. A distributed node estate is procured site by site against service that already exists.
Capacity obtained without the approval cycle it normally requires
The deployment model was designed around the constraint that defines public infrastructure delivery: the queue. Attaching to existing secondary service is what removes substation interconnection, rezoning and multi-year municipal approvals from the critical path.
Compute sits where the data must stay
Placement determines residency. Workloads execute in-region on a zero-trust mesh with mTLS identity, AES-256-GCM links and hardware-enforced memory encryption, rather than transiting to a distant commercial region.
No interconnection or rezoning path
Nodes attach to existing secondary grid drops, so deployment does not enter substation interconnection queues, rezoning or multi-year municipal approval cycles.
Committed per site, not per program
Capacity is added node by node against qualified locations, so expenditure follows contracted sites rather than being committed years ahead of first use.
Capability left behind at the site
Every node includes on-site storage. Civic buildings, depots and utility sites retain backup capacity and local power resilience as a by-product of hosting compute.
What governs feasibility on this site type
Public-sector siting is usually governed less by engineering than by classification, procurement and the public realm. The physical assessment is the same five gates as any other host.
| Consideration | What is assessed |
|---|---|
| Service capacity | Spare electrical capacity behind the existing supply at the candidate building, depot or utility site. |
| Security classification | Physical access control, perimeter arrangements and any handling requirements attaching to the workloads intended for the node. |
| Data residency | Documented residency and sovereignty requirements, confirmed against node placement and mesh routing before survey. |
| Public realm | Visual and acoustic impact of the sited enclosure, and any planning or conservation consent applying to the location. |
| Procurement route | Multi-year licensing rights over the location, and the framework or contract vehicle under which the site license is granted. |
| Access | Crane or vehicle access for placement and for scheduled maintenance. |
What the site receives
DAIT carries all capital expenditure, installation, maintenance and insurance. The host contributes space and access to existing service.
- Zero capital outlayDAIT carries all capital expenditure, installation, insurance and maintenance.
- Local power resilienceOn-site storage remains at the site, providing backup capacity without the authority procuring a battery system.
- Peak demand reductionStorage is intended to shave peak demand, targeting a 20–30% reduction in the site’s power costs.
- Recurring incomeA fixed site license fee or a share of compute revenue on otherwise unproductive estate.
DAIT is at pre-pilot stage — no node has yet been deployed in the field, and all timing, cost and resilience figures are engineering estimates and design targets rather than measured results. The platform is architected to meet SOC 2 Type II, HIPAA isolation and GDPR in-region data requirements; these are design targets, not certifications currently held. Any public-sector deployment would be subject to the relevant procurement rules, security accreditation and planning consent in the jurisdiction concerned.
Discuss a public-sector deployment
Tell us the estate, the residency requirement and the sites under consideration, and we will set out tier fit and the accreditation questions to resolve first.
Start a site assessment