Design direction

HYBRID

Keep payload processing close while centralizing governance

Hybrid should preserve customer-local secrets and payload processing while delivering signed configuration and bounded metadata to a control plane.

Last reviewed

RLX GATE SYSTEM MAP
Control plane
OPERATORSPolicies & routes
SIGNEDVerified revision
Data plane
CLIENTSApps & agents
RLX GATEIdentity & policy
ENVOYRoute traffic
ORIGINSBackend APIs

Envoy keeps serving the last verified revision if the management console is unavailable.

The operating problem

Central governance can conflict with residency, latency, private networking, local observability, and the need to keep serving during a control-plane interruption.

The intended control surface

This capability is part of the reviewed product architecture, not a decorative console module.

  • Customer-managed Envoy data planes
  • Local secrets and payloads
  • Signed offline-capable configuration
  • Configurable metadata-only reporting

What exists today

Signed snapshots and Envoy’s last-known configuration behavior provide a foundation. Remote fleet identity, xDS, node heartbeats, and regional placement are not implemented.

Work with the implementation team

Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.

Frequently asked questions

Is this capability generally available?

No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.

Can Reallexi evaluate our requirements?

Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.

NEXT STEP

Shape the requirements before implementation.

Talk to ReallexiRequest platform access