Engineering

Deploy the image. Pin the release. Verify the chain.

For engineering teams: the pilot path, the Helm chart and Terraform module, signed images and the open verifier.

Every capability on this page is a design commitment, and every record shown is an example on a fictional institution.

The pilot path

A pilot, not a product.

The pilot path is for an engineering team to try the image on a platform it already uses. It is neither GovernanceOS Cloud nor GovernanceOS VPC, carries no institution terms, and holds no production records.

Platform	What deploys	Label
Railway	The signed image with a sample tenant	Pilot, not a product
Render	The signed image with a sample tenant	Pilot, not a product

Helm chart

The Boundary Gateway and the VPC image

helm repo add governanceos [chart-repository]
helm install gateway governanceos/boundary-gateway \
  --set tenant=[tenant] --set mode=observe

Terraform module

VPC in your account

module "governanceos" {
  source  = "[module-source]"
  region  = "[region]"
  kms_key = "[key reference]"
}

Dashed boxes mark values set before launch.

Supply chain

SBOM and signed images

Every image is signed, ships with an SBOM, and carries a tool manifest hash you can pin.

Example release record

Release: 2026.10.1
Manifest: e341b1a6038544333df4b42eaa95a76dd9c881cc89953020f43611791af984d1

Verifier

Apache 2.0, offline

Recomputes the hash chain, checks the pack signature and compares the chain head with the one you were sent. No account and no network needed; the public anchor you check yourself.

Download the verifier 1.2.1

One Python 3 file, nothing else to install. SHA-256 of the download:

9e47a9fa d63ead2f 7588c080 9291ed0d 6ed06e18 341f851a 78308c2c 9532b543

Sample pack: nebula-mutual-2026Q3.pack.json, SHA-256 204ecfcf a43a42f6 5019d5ca 71058878 d9ee8333 2086c3e5 015cfef7 a08afada.

Changed pack, the same pack with one record changed: nebula-mutual-2026Q3-tampered.pack.json, SHA-256 7ba97367 3c2950aa 8027d06c e890a148 25c854f3 8e808745 3bc33cfe 282fb85f. All values: SHA256SUMS.txt.

python gos-verify.py nebula-mutual-2026Q3.pack.json --key cb943626ee1843d2df97786726539a0486ffbf8fca54cf64d3f1bc2241536e90

Exit codes: 0 verified (signed by the pack key you were sent), 1 not pinned, 2 chain broken, 3 signature invalid, 4 head mismatch, 5 cannot be read, 6 key mismatch. The sample’s pack key hash: cb943626 ee1843d2 df977867 26539a04 86ffbf8f ca54cf64 d3f1bc22 41536e90. The changed pack exits 2. Verify a pack, step by step

Interfaces and integrations

Interfaces: how your systems connect.

Assistants: Claude, Claude Code, ChatGPT and Microsoft Copilot connect over MCP. They read and draft. A gate passes only with the approver's signed token, issued outside the chat.
Sign-in: Your identity provider: Microsoft Entra, Google Workspace or Okta. One issuer per tenant. Nobody holds a GovernanceOS password.
MLOps tools: Webhooks bring events in; signed approval tokens go out to your deployment step.
VPC: AWS, Azure or Google Cloud, in your account.
Tool manifest: Versioned, hashed, signed and listed in the SBOM.

Ask from your assistant

Run the verifier. Then ask for a pilot.

One Python 3 file under Apache 2.0, offline, with no account. For a pilot image on Railway or Render, book thirty minutes with us.

Download the verifier Ask for a pilot image