⚠️ The new ZFordDev Documentation Portal is currently under active development. Search is not yet enabled and some pages are still missing. Please bear with us while we transition to the new system.
StaxV1 Router
The original Node.js‑based proxy gateway that powered early routing for the Stax ecosystem. StaxV1 served as the first unified entry point for internal services before the platform evolved into its modern architecture.
Legacy System Notice
StaxV1 Router is no longer maintained. All active routing responsibilities have transitioned to the environment‑isolated nodes of the ZIA Framework.
Why StaxV1 Was Sunsetted
StaxV1 was built during the earliest phase of the ecosystem as a lightweight asynchronous reverse proxy. It handled static route mapping, forwarded requests to internal services, and performed minimal token validation. While reliable, its monolithic structure and limited isolation model became a bottleneck as the platform expanded.
Modern requirements—such as multi‑tenant isolation, dynamic AI routing, and environment‑locked execution—are now handled natively by the ZIA Framework, the successor routing layer that provides hardened boundaries and modular routing nodes.
Migration & Documentation Status
Internal technical references, historical configs, and architectural notes for StaxV1 remain restricted until all remaining contract deployments complete their migration to isolated ZIA nodes.
Once the final transitions are complete, this page will be updated with full legacy documentation, including architectural diagrams, request flow maps, and deprecation notes.
Legacy Framework Overview
- • Runtime Architecture: Monolithic Node.js asynchronous reverse proxy.
- • Core Function: Static route mapping, path forwarding, and lightweight JSON token verification.
- • Port Configuration: Internal listener bound to
:8080. - • Successor: Fully deprecated in favor of environment‑locked routing nodes within the ZIA Framework.