Built with the teams that run it
Stories from our early design partners are being written and land here first. Until then, this is what teams build when one engine holds their state, their history and their live views.
What teams build
What teams build on one engine
Ten workloads, each a solution page with the tables, derived tables and live queries it runs on. Analytics reads the history; operational systems act on the current state.
Analytics
05Operational
05By industry
The same engine, your industry’s tables
Each page names the events an industry keeps, the state it derives from them and the queries it follows live.
Consumer & Real-Time
Infrastructure & Platforms
Industrial & Operations
Design partners
Become a design partner
The first stories on this page are written with the teams that run the engine on their own workloads. If you keep state, history and live views in separate systems and want them in one, write to us.
- 01
Work directly with the team
Your questions go to the engineers building the engine, in the open on GitHub, and what you run shapes what gets fixed and documented first.
- 02
Shape the roadmap
Your workload shapes what gets built next: the table modes, the joins a transformation can use, the windows a streaming query can open.
- 03
Run the engine on your own infrastructure
NYXDB is self-hosted software, so your data stays inside your environment from the first table onward, under the controls you already operate.
Build the next story on one engine
Start a node, create a table, and watch a streaming query follow it. The docs take you from install to your first self-maintaining derived table.