Apps and integrations
One front door
Web, mobile, desktop, and partner apps all use the same consistent API.
Platform · Architecture
TradingSDK brings 46 focused services together behind one API, covering everything from accounts and market data to orders, risk, research, and reporting.
46
Services
in 6 dependency layers
754
API operations
one consistent, documented contract
12,000+
Automated tests
across 160 test projects
200+
Database tables
PostgreSQL, plus ClickHouse analytics
How it fits together
Web, mobile, and desktop apps all connect the same way. Trading features are built on shared market data, accounts, and permissions, so every part of your product works from the same information.
FROM APP FEATURES TO CORE DATA
Experience
Features for users
Application
Research & analysis
Trading
Orders, money & risk
Engine
Trading & Research
Financial Data
Market information
Reference Data
Shared definitions
Platform
Accounts & access
Built for different kinds of work
Some work needs an answer right away, some runs around the clock, and some needs serious computing power. TradingSDK gives each its own place, so heavy work doesn't slow down the app people are using.
Apps and integrations
Web, mobile, desktop, and partner apps all use the same consistent API.
Ongoing tasks
Data imports, alerts, indicators, and scheduled work continue without slowing down the app.
Trading and research
Dedicated processing handles live trading, simulated trading, backtests, and optimization.
Realtime updates
Prices, trades, and portfolio changes reach connected apps as soon as they happen.
PostgreSQL
accounts and business records
ClickHouse
large volumes of market data
Redis
fast updates and short-lived data
File storage
archives and larger files
What is included
Select a service to see what it does. Each one has a single, clear job, which keeps the platform easy to understand, extend, and run.
What happens to an order
From the moment someone taps Buy or Sell, the order is checked, routed to the right place, recorded, and reflected in their portfolio.
01
Order
Request received
02
Risk
Limits checked
03
Engine
Trade processed
04
Execution
Destination chosen
05
Fill
Result confirmed
06
Ledger
Money recorded
07
Portfolio
Holdings updated
Every step has a clear owner. Orders are checked before anything changes, and money movements are recorded in the same step, so nothing is ever left half-recorded.
How it is engineered
Our standards aren't just written down. Tests and compiler rules check them automatically, and every service has its own design document.
415
Architecture rule tests
Automated checks make sure every service follows the rules for dependencies, naming, security, and accounting.
20
Custom code-analyzer rules
Our coding rules are built into the compiler, and warnings that have been fixed can't creep back in.
12,000+
Automated tests
Spread across 160 test projects, including tools that simulate failures and replay past market data.
670K+
Lines of C# code
Not counting comments or blank lines. On top of that, 156,000 lines of documentation sit right alongside the code.
137
Documentation pages
334,000 words covering service designs, coding standards, and operations guides.
46
Service design documents
One for every service, describing what it does, the actions it supports, and the business rules it follows.
Join the early-access waitlist, or talk to us about what you're building.