Event-driven runtime
A hybrid C++ and Go direction for the core runtime, with internal event transport and IPC services forming the foundation.
Technology
A systems-first architecture direction.
Noxus is developing the foundations of an event-driven platform, with later capabilities planned across market data, execution policy, and risk processing.
Runtime model
Built around events, state, and evidence.
The technical direction combines a performance-oriented C++ core with Go services where concurrency, networking, and operational simplicity are valuable. Final implementation choices will be validated as the foundation develops.
Capability map
Current foundation systems.
The areas presently in development.
Position and account state
State models intended to make balance, position, and account transitions explicit under concurrent workloads.
Telemetry and observability
Instrumentation foundations intended to expose system health, event flow, and operational behaviour from the beginning.
Historical replay
A replay framework direction for repeating market-data scenarios and supporting deterministic regression testing.
Core architectural pillars
From market events to account conditions.
Architecture direction
Market data aggregation
Designed to normalize and aggregate heterogeneous market data into a consistent internal representation.
Planned
Execution policy and routing
Planned policy logic for exposure-aware execution pathways and explicit routing decisions.
Planned
Margin and liquidation state processing
An event-driven state model intended to recalculate account conditions from price and account events.
Development tracks
Parallel work, explicit sequence.
Core runtime and event bus
Runtime, internal event transport, state, telemetry, and replay foundations.
Gateways, data pipelines, and telemetry
The next connectivity and operational layer, without implying active external connections.
Policy routing and margin calculation
Later execution-policy and risk-processing work built on the earlier foundations.
Future platform direction
PlannedBlockchain and custody infrastructure.
Future research may include wallet services, custody architecture, chain integration, key-management boundaries, and on-chain connectivity. No custody operation or chain integration is currently presented as operational.
Join the work
Systems problems worth examining closely.
Review available roles across core systems, future platform domains, reliability, and customer operations.
Join Our Team