Skip to content

Platform

One platform for every layer of protection

ArxLayer unites web, API, AI-agent, and bot protection in a single event-driven control plane. Products are grouped under five pillars — Protect, Control, Trust, Edge, and Intelligence — and no private keys ever live in the enforcement layer.

The platform

Five pillars, one control plane

Adopt the products you need — they share one policy model, one event bus, and one control plane, and work together by design.

One platform, separate components

An event-driven platform with a clean boundary

Every product is a single-responsibility component on a shared event bus. The enforcement layer performs pure traffic inspection; trust, certificates, analytics, and identity each live in their own component — so a change or failure in one never widens the blast radius of another.

Architecture diagram. Traffic flows from the Internet to ArxLayer Edge, through Coraza with the OWASP Core Rule Set, then to your origin application. ArxLayer Trust, Certificates, Analytics, Billing, and IAM/NHI are separate platform components. No private keys traverse the event bus or config bus.

Request path
Internet
Untrusted client & machine traffic
ArxLayer Edge
TLS termination & request enforcement
Coraza + OWASP CRS
Inspection & anomaly scoring
Origin App
Your application or API
Platform components — separate from enforcement
ArxLayer Trust
Key custody & trust bundles
ArxLayer Certificates
Certificate lifecycle & certificate refs
ArxLayer Analytics
Event intelligence & reporting
ArxLayer Billing
Usage & commercial metering
ArxLayer IAM / NHI
User, service & machine identity

Boundary guarantee: ArxLayer Edge performs pure traffic enforcement. Certificate lifecycle, key custody, analytics, and billing are separate components — and no private keys ever traverse the event bus or config bus.

ArxLayer architecture: traffic is enforced at ArxLayer Edge using Coraza and the OWASP Core Rule Set before it reaches your origin, while certificate lifecycle (ArxLayer Certificates), key custody (ArxLayer Trust), analytics, billing, and identity (ArxLayer IAM / NHI) remain independent platform components.

Secure by design

No private keys in the enforcement layer

ArxLayer enforces traffic policy and nothing else. Certificate lifecycle and key custody live behind their own boundaries, and no secrets ever travel the config bus.

No keys in enforcement

The enforcement layer stores no private keys or secret material — nothing sensitive to exfiltrate from the request path.

Opaque certificate references

ArxLayer references certificates verbatim and never resolves them to keys.

Refs, not keys, on the bus

The event bus carries certificate references and metadata only — never private keys.

Explore the ArxLayer platform

See how one event-driven platform protects every exposed surface — web, API, AI-agent, and bot — with trust, edge, and intelligence built in.