Home · Learn · The Deployment Runbook

The deployment procedure is part of the license.

A sovereign domain is stood up under a license, in phases, with issuance off until a licensing event.

A demonstration is not a national deployment. Re-skinning the demonstration onto a country's names and language is measured in hours; that is the demonstration only. The live validator fleet is operated by JIL Sovereign Technologies Incorporated.

The path, phase by phase

  1. Briefing. A first call with a named principal and an engineer, under NDA on request. You leave with a license term sheet and a security as-built summary.
  2. Evaluation. Your technical team reviews the Federation Thesis and the status ledger and tests the claims.
  3. Pilot domain design. Choose the license class. Define the currency policy, the identity requirements, the jurisdictions the domain accepts value from and sends value to, the per-transaction ceiling, and the corridors that matter.
  4. Pilot deployment. A domain on the managed backbone reaches technical readiness in about 30 days after its policies are pinned, with issuance off. Licensing and regulatory approvals are separate and are not in that figure.
  5. Production. Local regulatory approval, then a licensing event before issuance is enabled.
  6. Expansion. Additional corridors, instruments, hubs, and annexes.

On the country's side: a legal entity and a regulator relationship, a KYC and KYB process at the domain, and a named lead for compliance, treasury, and operations. Governance of the domain, its policy and profile, stays with the licensee. JIL controls changes to the shared core and operates the home-chain validators; who holds which key and who can halt or upgrade is on the control and custody page. The step-by-step deployment procedure is provided to the licensee.

Learn ยท Request a briefing