Project Noxus
EN中文

Financial systems engineering

Infrastructure for complex markets.

Project Noxus is developing a high-performance technology platform for derivatives and CFD infrastructure, with an initial focus on runtime architecture, state, telemetry, and replay.

Explore the architectureAbout the project ↗
Project Noxus runtime architecture modelA conceptual event runtime connected to foundation, state, IPC, telemetry, and replay nodes. Motion is illustrative and does not represent a live system.EVENT RUNTIMEFOUNDATIONSTATEIPCTELEMETRYREPLAYNOXUS / SYSTEM MODELARCHITECTURE DIRECTION

Current stage

Building the foundation before the surface.

Noxus is at an early planning and foundation stage. Market connectivity, execution routing, external hedging, and full real-time risk processing remain later development objectives.

System focus

A deliberate technical foundation.

The architecture direction prioritises clear state, observable behaviour, and repeatable testing across the system lifecycle.

01

Runtime

Coordinates event flow and internal services so latency-sensitive processing has clear execution boundaries.

02

State

Owns position and account transitions as prices change, keeping concurrent updates explicit and testable.

03

Telemetry

Makes event flow, system health, and failure conditions visible before operational complexity grows.

04

Replay

Recreates market-data and account-state sequences to reproduce issues and validate system changes.

Current engineering focus

Foundation-stage questions guiding the present architecture work.

Deterministic state transitions

Reasoning about account and position changes under continuous price events.

Replayable sequences

Structuring market-data and account-state events so scenarios can be repeated and examined.

Runtime boundaries

Defining the separation between latency-sensitive logic and service orchestration.

Observable failure modes

Making failure conditions visible before external market connectivity is introduced.

Development sequence

Foundation before connectivity.

Core runtime work proceeds alongside telemetry, replay, and state foundations before external connectivity and policy routing are introduced.

  1. 01
    In development

    Core runtime and execution foundations

    Runtime architecture, event transport, state structures, telemetry, and replay foundations.

  2. 02
    Next

    Market connectivity and data normalization

    Planned ingress, normalization, aggregation, and gateway foundations.

  3. 03
    Planned

    Risk processing and policy routing

    Later policy, margin-state, liquidation, and external hedging objectives.

Market context

A clear view of the instruments in scope.

Review a deterministic demonstration feed covering forex, indices, commodities, and crypto. The values are indicative and not executable.

View demo markets

Systems engineering

Work on event-driven runtimes, explicit state, and replayable systems.

We want to hear from engineers interested in asynchronous system design, deterministic execution, and real-time state management.

Explore available roles ↗