TradingSDK

Platform · Architecture

One backend, engineered like it matters.

Forty-three services in six dependency layers power every TradingSDK app — from charting terminals to broker platforms to research products — behind one contract-tested API.

Join the waitlistBack to platform

43

Services

760

REST endpoints

6

Dependency layers

18

Order types

The system at a glance

Six layers, one direction.

Clients enter through one API. Beneath it, every dependency flows downward — from experience to application to the trading core, onto data and platform — with the Engine compute plane attached by queue.

WebMobileDesktopOne contract-tested API · REST + realtime streamsDEPENDENCIES POINT DOWNLAYER 6ExperienceWhat users touch6 servicesLAYER 5ApplicationResearch & analysis6 servicesLAYER 4TradingMoney & risk9 servicesLAYER 3Financial DataTime-series truth5 servicesLAYER 2Reference DataShared vocabulary5 servicesLAYER 1PlatformIdentity & edge11 servicesEnginecompute planeby queueSingle-writer data substrate · PostgreSQL + TimescaleDB · Redis

The service map

Six layers. Every service in its place.

Select any service to see what it owns. The layering is a build-time rule, not a diagram convention: a service depends only on layers below its own.

Layer 6ExperienceWhat users see and touch
Layer 5ApplicationAnalysis and research on top of the trading core
Layer 4TradingThe core that moves money and manages risk
Layer 3Financial DataTime-series truth with point-in-time history
Layer 2Reference DataThe nouns everything else agrees on
Layer 1PlatformIdentity, tenancy, and the commercial edge
Beside the layersComputeStateless, queue-invoked, no upward calls

The order path

From click to ledger, one governed path.

The trading core is a chain of single-owner services. Nothing skips a stage, and nothing moves money without a journal entry.

  1. 01

    Order

    Idempotent intake

  2. 02

    Risk

    Pre-trade checks

  3. 03

    Engine

    Mode-gated run

  4. 04

    Execution

    Venue routing

  5. 05

    Fill

    Guarded states

  6. 06

    Ledger

    Double-entry post

  7. 07

    Portfolio

    Positions update

Every stage is owned by one service, every state change passes a transition guard, and every money movement lands in the ledger in the same database transaction that caused it.

Build on a foundation this deliberate.

Join the early-access waitlist, or talk to us about what you're building.

Join the waitlistCompany