Sovereign is a checklist.

Five conditions each verifiable by your operations team during Readiness before any system access exists. Sovereign is not a label. It is a set of facts your team can confirm.

01

Your infrastructure

Runs on-prem or in your in-country cloud with air-gapped deployment available. Your operations team provisions the environment. 009 receives access to it never the reverse.

02

Models inside your perimeter

The AI models themselves are hosted inside your perimeter. Network egress rules at your boundary. Inference traffic never crosses it.

03

Read-only until signed

Recon is read-only until a deal is signed. Access credentials are issued at read-only scope during Readiness before any system access exists.

04

Your data stays

Your data never leaves your systems. A zero-egress policy at the firewall monitored by your own team. Nothing crosses the boundary.

05

You own the datalake

009 owns the tooling. You retain the datalake and everything stored in it. Storage schemas and contents sit in your tenancy.

Three ways to stand it up.

01

On-prem

Your data center and hardware remain under your physical control.

02

In-country cloud

Your national or regional cloud tenancy under your jurisdiction's law.

03

Air-gapped

No external connectivity at any layer. Updates arrive through your controlled transfer process.

Why this matters.

Control over dependency

Some institutions cannot accept foreign-hosted models or external teams with permanent access to operational data. 009 delivers the same capability inside your perimeter and staffs every engagement to transfer that capability to your own people.

Exit by design

The datalake, records, and operational mapping belong to you. Ending the relationship leaves a complete, functioning asset in your hands. Your data and institutional model remain yours throughout and after.

Bring your operations team to the first call.

Readiness is structured so their sign-off happens before anything connects.

GET STARTED