Built for operational clarity
Control, tenant, usage, audit, and runtime records live in separate SQLite databases with foreign keys, WAL, checksummed migrations, and data-specific durability settings.
- Server-resolved tenant hierarchy
- Transactional audit outboxes
- Tamper-evident central audit chain
- Deterministic signed runtime snapshots
A real gateway lifecycle
The current release imports OpenAPI 3.0/3.1 JSON, validates and stores the original contract, configures scoped upstreams and routes, compiles Envoy resources, publishes signed snapshots, and records rollback history.
Boundaries stay visible
Developer portals, monetization, a broad policy catalog, administrator identity federation, migration adapters, provider-neutral AI routing, RAG, MCP, and agent governance remain staged work. The implemented shared-Llama queue is documented separately from that broader roadmap.
Frequently asked questions
Does RLX Gate require Kubernetes?
No. The current production topology is designed for one hardened VPS. Kubernetes remains an optional future deployment target.
Can the gateway continue if the control plane stops?
Envoy continues serving its last accepted filesystem configuration. gRPC xDS acknowledgement and multi-node fleet control are not yet implemented.