Edge

See your policy converge across every edge node

ArxLayer Edge Health reports per-node status, config version, and freshness for the whole fleet. Watch a policy change roll out, spot a node that hasn't caught up, and know exactly how the edge behaves when the control plane is briefly out of reach.

Start free Explore the platform

The problem

A policy change isn't done until every node has it

Distributed enforcement only protects you when each node runs the version you intended. Without convergence signals, rollout is a guess.

Silent config drift

One node lagging behind on an older policy version enforces rules you already changed, and nothing tells you.

Rollout you can't observe

You apply a change and hope it propagated. Without per-node freshness, you don't know when the fleet has actually converged.

Unclear failure behavior

If the control plane blips, teams need to know whether enforcement keeps running on the last-known config, or quietly stops.

What you get

Convergence signals you can act on

Every node reports the policy version it's running and when it last refreshed, so rollout state is observable instead of assumed.

Per-node health

See each edge node's status, the config version it's enforcing, and when it last reported in.

Config freshness

Track how current each node's policy is, so a stale node stands out immediately.

Convergence view

Watch a versioned change move across the fleet until every node has converged on the target.

Drift detection

Surface nodes running an older version than the rest, before that gap becomes an enforcement gap.

Fail-static, made explicit

If the control plane is briefly unreachable, nodes keep enforcing the last-known config. Edge Health shows that state plainly.

Fleet at a glance

One operational view of node status and config version across every region you run.

How it works

From change to converged

Apply a policy, follow it across the fleet, and confirm the whole edge is enforcing what you intended.

Publish a versioned change

Every policy change is a new version, pushed to the fleet through event-driven config rollout.

Nodes pick it up

Each edge node loads the new version locally and reports the version it's now enforcing along with its freshness.

Confirm convergence

Watch freshness update node by node until the fleet has fully converged, and catch any straggler that hasn't.

Start free Request demo

FAQ

Questions, answered

What does Edge Health actually show me?: Per-node status, the config version each node is enforcing, and how fresh that config is, so you can see rollout and detect drift across the fleet.
What happens if the control plane goes offline?: The edge fails static. Nodes keep enforcing their last-known config locally, and Edge Health reflects that they're running on a prior version until the control plane returns.
How do I know a policy change reached every node?: Each node reports the version it's running. Watch config freshness update across the fleet until every node has converged on the new version.
Does Edge Health add latency to the request path?: No. The edge request path is local and in-memory. Health and convergence reporting are separate from request enforcement.

Explore

Know your edge is running the right policy

Watch every node converge on your latest version, catch drift early, and understand exactly how the edge behaves when the control plane blips.