Edge
Policy changes reach every edge node in seconds
ArxLayer streams configuration to the edge fleet over an event-driven, log-compacted bus, so a policy edit lands everywhere within seconds. Every change is observable, ordered, and reversible.
The problem
A change you can't see isn't a change you can trust
Distributing configuration across an edge fleet is where security tooling quietly drifts and breaks.
Drift across the fleet
Nodes fall out of sync when updates are pushed best-effort, so the same domain enforces different rules in different places.
Slow, unclear rollout
You change a policy and have no idea when it actually took effect, or whether every node received it.
Cold starts lose state
A node that reboots or scales in needs the current config immediately, not a slow replay or a stale default.
What you get
Configuration that arrives fast and stays consistent
Changes flow as events on a compacted log, keyed per domain, so the edge always converges on the latest intended state.
Event-driven rollout
A control-plane change publishes an event; the edge fleet picks it up and applies it within seconds.
Log-compacted bus
The bus retains only the latest config per domain, so a node always reads the current state, not a long history.
Per-domain delivery
Each domain's configuration propagates independently, so one tenant's change never waits on another's.
Reconciliation
Nodes continuously converge on the published state, healing any drift instead of accumulating it.
Snapshot on boot
A node that starts or scales in loads the current config from the compacted log before it serves traffic.
Reversible by version
Every config is a version. Roll back by publishing a prior state, and watch it propagate the same way.
How it works
From edit to enforced
A change moves through the control plane to the edge as an ordered, observable event.
Make a change
Edit a policy or list through the API-first control plane. The change becomes a new versioned config for the domain.
Publish to the bus
The control plane writes the config as an event on the compacted log, keyed to that domain.
Apply and reconcile
Edge nodes consume the event, swap in the new config, and keep reconciling so the fleet stays consistent.
FAQ
Questions, answered
- How fast does a change reach the edge?
- Typically within seconds. The change is published as an event and the edge fleet applies it as it arrives, rather than on a fixed polling cycle.
- What happens when a new edge node starts up?
- It reads the current configuration from the compacted log before serving traffic, so it never starts on a stale or default policy.
- Can I roll a change back?
- Yes. Every configuration is versioned, and rolling back publishes a prior state that propagates to the fleet the same way the change did.
- Does propagation slow down the request path?
- No. Config is applied out of band and the edge serves requests from local in-memory state, so enforcement never waits on the control plane.
Ship policy changes you can watch land
See how ArxLayer propagates configuration across the edge fleet in seconds, with reconciliation and snapshot-on-boot.