GLACIS Managed · Operated by us
Glacis operates the control between your application and the model it calls: allow, hold, or deny. Each covered decision leaves a signed operational record an auditor, an underwriter or a customer’s security team can check for themselves. We run it; you don’t staff it. The deployment plan states what is in scope and what is not.
Defined coverage · Stated fail behavior · Signed records an auditor can check
✓ VERIFIED
Simulated for illustration · the cryptographic verification below runs locally in your browser.
Your team doesn’t run the arbiter or assemble evidence under deadline. We operate it, and an auditor can check the record without a fire drill.
The demo
The sequence below runs from the connector to a verified record.
The connector brings up a WireGuard tunnel. Your agents now reach their arbiter over a private WAN.
The agent’s base URL points at the arbiter. It doesn’t know anything happened.
Each configured in-scope operation can be allowed, witnessed, or blocked. A signed record is created for the covered event.
The record goes into the browser verifier, which checks it without trusting us.
$ glacis connect wg0 up · tenant arbiter reachable · private WAN # agent config — one line - base_url: https://api.provider.example + base_url: https://arbiter-01.tenant.glacis # event stream 14:02:31 agent-billing tool.invoke allow 14:02:33 agent-support mail.send witnessed 14:02:36 agent-ops db.drop_table blocked # receipt 4f2c…a081 canonicalize (RFC 8785) ✓ SHA-256 ✓ Ed25519 ✓ chain ✓ ✓ VERIFIED IN YOUR BROWSER — local cryptographic check complete
Simulated for illustration · the verification is real. Run it on a real signed record below.
Verify it yourself
This is a real signed sample record. The verifier checks it locally in your browser (Ed25519 over SHA-256, canonicalized under RFC 8785); the record is not sent to us to be checked. A valid signature establishes integrity and signer identity for the fields shown. It does not establish completeness, safety, or compliance.
What we run for you
A Glacis record links the governed action, the intended rule, and the control decision in a signed, hash-chained artifact. An auditor or a customer’s security team can verify its integrity. Coverage, configuration, key custody, and whether the control was appropriate stay open to examination.
A dedicated per-tenant arbiter can be reached over WireGuard, Twingate ZTNA, or AWS PrivateLink, depending on configuration. The transport and payload boundary must be assessed for the actual deployment.
We map the action path that matters onto a supported integration path, and confirm the network, identity and control configuration. The meter is the signed-record count, the same operational unit the Console records. Usage stays legible as a workflow moves into production.
Private WAN · Assurance ladder
GLACIS Managed can provide a dedicated per-tenant arbiter reached over WireGuard, Twingate ZTNA, or AWS PrivateLink. That can reduce public routing and multi-tenant mixing, but the exact network path depends on the selected transport and surrounding customer architecture.
Managed means Glacis operates the arbiter. Dedicated infrastructure and private transport are evidence about isolation and routing; they are not proof that an operator cannot access payloads. Stronger confidentiality claims require additional controls and their own evidence.
| Rung | The claim | How you check it |
|---|---|---|
| Managed | Operational isolation. Private WAN, dedicated per-tenant instance. | Records + the connector config you control |
| + Nitro | Enclave-backed. Hardware attestation can identify the enclave image and configuration that ran. | Check the attestation document and its stated measurements |
| PrivateLink / your VPC | PrivateLink can keep configured service traffic on AWS network paths; a customer-VPC deployment can keep the configured data plane inside the account, subject to actual routing and surrounding services. | Your own VPC console |
| Self-hosted / airgap | The data plane can remain within the customer-operated boundary. | Inspect your host, routing, and deployment configuration |
Each rung makes a different claim. The supporting evidence and exclusions should travel with it.
Getting started
You can start with organization-wide monitoring or with one high-risk use case, move a live workflow into production, or talk to us about an enterprise deployment. The price is scoped to what the deployment requires.
Design partners
Availability, evidence, permissions and working boundaries are settled before the work starts.
Managed deployment
We work from the action the AI can take and the rule that applies to it, and come back with the managed deployment, the private connectivity, and the evidence an auditor or a customer’s security team will ask for.
Private deployment · regulated workflows · evidence a regulator can verify
