Resources

Deploy on your own infrastructure

What it takes to run the loop on your own infrastructure.

Approved by the Board for implementation · 20 November 2026

Status

No sovereign deployment exists yet. Documents are drafts.

For sovereign deployment teams.

In one paragraph

The Sovereign Continuity Stack is designed to run the whole CRIS loop inside a country or institution, on infrastructure it controls, with its own data. This path is for the technical teams who would run it. It explains what a deployment needs, how it moves from a sandbox to live use one stage at a time, and where it can be hosted. No sovereign deployment exists yet; these documents are drafts so that you can plan, and tell us what is missing.

Readinesschecklist andagreementsSandboxisolated; no realpeople or dataTestnet nodessuch as BGTI’s,under agreementLimited partnersnamed institutions,monitoredLiveafter outsideaudit; local controla failure sends the deployment back one stageEach gate needs:the previous stage’s correspondence proofs · a C-Gate decisiona tested rollback · the local partner’s approvalThe same staging every CRIS release follows.
One stage at a time; a failure goes back one stage. From the Sovereign Continuity Stack page; the Deploy path documents each stage.

The documents

DocumentWhat it coversState at launch
Deployment guideWhat a sovereign deployment is; what CRIS supplies (software, updates, a licence, training through partners, audit tools); what stays local (data, models, hosting)Draft 0.1
Readiness checklistWhat an institution needs before the sandbox stage: a legal basis for the data; a hosting choice; staff to operate and oversee; an agreement with CRIS; a local accountable personDraft 0.1
Staged rolloutThe five stages and the gates between them, with what each gate needsDraft 0.1
Runtime interfaceWhat the Stack needs from any host: compute, storage, network isolation, CTU metering hooksPlanned
Hosting optionsNational or partner hardware; LOGOS-C; testnet nodes, each under a written agreementDraft
CTU metering methodHow energy and compute are measured and reportedDraft 0.1
SandboxAn isolated environment to run the loop with no real people or dataPlanned: when the Stack reaches prototype

Five stages

  1. Readiness: the checklist complete, agreements signed and a local accountable person named.
  2. Sandbox: the loop runs in isolation, with no real people or data.
  3. Testnet nodes: on testnet infrastructure, such as the Botswana Global Testnet Initiative’s, under a written agreement, still without live personal data.
  4. Limited partners: a small number of named institutions use it, monitored, under their own agreements.
  5. Live: general use, after an independent audit, under local control.

Each step forward needs the previous stage’s correspondence proofs, a C-Gate decision, a tested rollback and your approval. A failure sends the deployment back one stage. This is the same staging every CRIS release follows. No partner receives a stack that has not passed an external audit.

Hosting

The Stack will run on any host that meets the runtime interface (planned): national or partner hardware, LOGOS-C, or testnet nodes. Neither LOGOS-C nor the Testnet is required.

LOGOS-C and the Botswana Global Testnet Initiative. An organisation also led by our Founder. Any work with CRIS is under a separate written agreement on arm’s-length terms. Related organisations

Your data

Data and models stay under your jurisdiction. CRIS supplies software, updates, a licence on fair terms, training through partners and audit tools. It does not take your data out; the deployment licence and local law govern any exception. What stays in a country, and on what terms data may cross a border, will be stated in the wording counsel approves.

What this path will not do

It names no country, ministry or partner until an agreement is signed in writing and publication is approved. It presents no host as required. Read the Africa and sovereign deployment page in our Ecosystem section, and our Africa and Global South commitment.

Owner: Sovereign Deployment, with Systems EngineeringNext review: 2027-05-11