This page answers where the Cyber Fabric mesh sits and where Ikaros (PDE) runs.
Dedicated enclave, not multi-tenant SaaS, not a cloud brain. Telemetry does not leave the fielding.
We do not publish lab addresses. ATT&CK IDs, when shown, are evidence citations — not a claim we outperform a catalog.
THE FRINGE is published only at c1bertitans.com. This is the sole public sales and architecture surface.
Reference architecture
Diagram · dedicated enclave · untrusted ≠ enrolled · residency = customer/lab · marketing host is outside this picture
What is public vs not
The public origin is a static brochure. It is not the mission system.
This diagram names the split. It does not publish addresses.
Diagram · marketing host ≠ enclave · no addresses published
Planes, control, residency
Enforcement
Customer- or lab-sited edge PEP. The fabric is three planes: untrusted admission, enrolled workforce, WAN / on-the-wire. Selective TLS inspect is enrolled-plane only — never default on untrusted. Ikaros returns acts to these PEPs on the wire.
Control
Dedicated admin station (or future always-on core). Not a multi-tenant cloud control plane in v1. Public marketing host is not the enclave.
Decision
Ikaros is the PDE. CEP-Rank scores; AEGIS kernel gates; journal records. LLM narrates only. Gate is HUMAN_ONLY. AUTO_SAFE is off. The AEGIS droid on the hub is the guide, not the weights.
Residency
Fused telemetry stays in the customer or lab enclave. We do not ship a “telemetry lives in our SaaS” claim for v1.
Tenancy: dedicated per fielding — one customer (or one lab) per enclave.
Residency: fused telemetry does not leave that enclave in v1.
This brochure plane is a single shared host today (cert SAN will show cPanel cosmetics). That is a perception gap, not product HA. Dedicated hosting and marketing HA wait for ARR. Mapping to NIST is not an ATO.