Documentation

AegisWire Documentation

Everything you need to deploy, enrol, connect, and operate the AegisWire post-quantum secure-transport platform — from a first device to a multi-site federated fleet. Start with the orientation below, then jump to the area you need.

How AegisWire fits together

Three components make up every deployment. Your tenant is provisioned as a managed service, so you operate the parts that matter to you and we operate the rest.

1 · Control plane

Your managed tenant

A dedicated control plane issues device identities, signs admission grants and policy, and enforces your licence and entitlements. You administer users, devices, gateways, tokens, and policy from its admin console.

2 · Gateways

The data plane

Gateways terminate the quantum-resistant tunnel and forward traffic under centrally enforced policy. Deploy them in the region and cloud you require; site-to-site links join two gateways directly.

3 · Clients & SDK

How traffic enters

Endpoints connect through the native apps, or embed the transport directly with the developer SDK. Both enrol with a one-time activation token and negotiate the same post-quantum handshake.

Connect your first device

1

Get your tenant

Your AegisWire control plane is provisioned and handed over with admin access. Talk to us to start.

2

Issue a token

From the admin console, mint a one-time activation token for a user or device. The token carries no secrets — scope is derived server-side.

3

Enrol the client

Install the native app, paste the token, and enrol. The device generates its own key material and receives a signed identity and gateway contact points.

4

Connect

Hit connect. The client completes the post-quantum handshake against a gateway and carries your traffic under enforced policy.

Native clients are available for macOS, iOS, and Linux. Detailed, version-matched installation and operator guides are delivered with your tenant onboarding.

Operator runbooks & API reference

Detailed operator runbooks, the SDK/API reference, and enrollment integration guides are version-matched to your tenant and provided as part of onboarding so they always reflect the exact build you run. If you need access ahead of provisioning, or have an integration question, reach the engineering team directly.