The third adaptive hybrid system

Protection does not stop at the device.

Citadel coordinates protected routing, DNS, containment, privacy-safe evidence, endpoint controls, and optional two-hop separation across one governed Internet journey.

Explore the system See what gets verified

Standalone or integrated
Client + server
One-hop or two-hop

A luminous information path moving through a sequence of Citadel protection boundaries and two gateway nodes

Journey viewRepresentative architecture

One tunnel.Multiple coordinated defenses.

Current truth.Not a decorative “connected” badge.

Bounded claims.Every capability carries its evidence state.

One protection fabric

Adaptive by design.
Honest by operation.

Citadel changes form without changing its responsibility: protect the approved journey, report what is actually happening, and avoid silently interrupting desired traffic.

Current / validated scope POC / under qualification V2 / standby

Standalone or integrated

Use Citadel as its own protection client or embed the governed protection boundary inside an application.

Android, Linux, Windows

One product family with platform-specific artifacts and qualification states—not one-size-fits-all claims.

Client and server defenses

Endpoint consent, route truth, gateway enforcement, continuity, and evidence work as separate observable responsibilities.

One-gateway or two-hop

Start with direct protected egress or select ingress/egress separation when the approved service tier requires it.

The system in one view

One dominant idea.
Details when you ask for them.

The architecture remains available to technical buyers without forcing every customer to decode it before understanding the benefit.

Citadel shown across standalone and integrated deployment, three operating systems, client and server controls, and one-gateway or two-hop routing

Protection that proves itself

“Running” is not the same as protected.

Citadel separates the signals that security products too often collapse into one reassuring icon.

Configured

The customer requested protection and an approved configuration exists.

Interface

The protected network interface is present.

Handshake

The peer exchange is current—not stale.

Traffic

Receive and transmit counters prove useful movement.

DNS

Resolution follows the approved protected path.

Egress

The public exit matches the selected route class.

A customer-facing dashboard is part of the product direction. Any displayed measurements must be identified as real evidence, representative data, or demonstration data.

Live threat evidence

What Citadel has stopped.

Only signed, production-observed blocks that meet the public privacy threshold appear here. Laboratory tests, demonstrations, raw addresses, customer identifiers, and small identifying buckets are excluded.

Checking verified evidence

Aggregate feed

Verifying the feed…

The live ledger is below its privacy threshold or has no eligible signed production events.

UIA means Unclassified Intrusion Attempt. Classification is evidence-led; automated analysis advises, while deterministic policy controls what can be published or enforced.

Independent connection tests

See what the outside world can observe.

Run these third-party checks with Citadel enabled, then compare the results with your approved route and DNS configuration. Each test supports specific ring evidence; none certifies an entire ring by itself.

Ring 01 AegisRing 02 TrueNorthRing 08 Infrastructure

IPLeak

Inspect the public IPv4/IPv6 address, visible DNS resolvers, and WebRTC exposure.

Open independent test

Ring 02 TrueNorthRing 03 Gatewatch

DNSLeakTest

Run a standard or extended test to see which DNS resolvers are visible outside the protected journey.

Open independent test

Ring 02 TrueNorthRing 03 Gatewatch

BrowserLeaks DNS

Inspect browser-visible DNS resolution and compare it with Citadel's approved resolver path.

Open independent test

Ring 01 AegisRing 05 Veil

BrowserLeaks WebRTC

Check whether the browser exposes another public address outside the selected Citadel route.

Open independent test

Ring 02 TrueNorth

Cloudflare Connection Information

Review resolver and encrypted-DNS characteristics reported by an independent network service.

Open independent test

These tests are operated by independent third parties. Their privacy policies apply when you leave the Citadel website. Citadel does not transmit your account identity to these links.

Route architecture

Choose the journey—not the jargon.

CoreOne-gateway

DeviceIngress + egressInternet

Protected transit and public-IP masking through one registered Citadel gateway.

Premium architectureTwo-hop separation

DeviceIngressEgressInternet

Separates customer-facing ingress from destination-facing egress, reducing what an ordinary single-position observer can reconstruct.

Two-hop separation does not erase identity supplied to a destination, defeat authenticated accounts or cookies, or promise legal untraceability.

Citadel defense sequence

Ten rings. Ten honest states.

Evidence status is assigned by ring. Citadel’s ten-ring architecture should not be described as wholly deployed, universally qualified, or independently certified.