Technical reference for trading infrastructure.
An honest index rather than a catalogue of placeholders. Public documentation covers architecture, integration surfaces and operational configuration. Endpoint-level references, credentials and environment specifics are issued per engagement, because they describe your servers rather than a generic product.
Two layers of documentation.
Separating the two keeps public pages accurate and keeps environment detail where it belongs.
Public — architecture & capability
What each component does, how the parts connect, which configuration decisions matter and where the usual failure points sit. Everything indexed below is a real page you can read now, without a login or a form.
Engagement — environment & endpoints
Interface specifications, field mappings, authentication, runbooks and rollback procedures for your deployment. These are written against your servers, versions and integrations, so publishing a generic version of them would be misleading rather than helpful.
Documentation by subject.
Six areas covering the infrastructure a broker or prop firm actually operates.
Platform & Server-Side Interfaces
How platform-level automation is approached, and what the Manager API can and cannot do on a live server.
Integration Reference
The integration surfaces available across the stack, the patterns we build against, and how failures are handled.
CRM & Back Office
Record structure, workflow and reporting across broker and prop firm back offices.
Payments, KYC & Compliance Operations
How funding routes, verification providers and audit requirements are wired into the back office.
Risk & Dealing
Exposure monitoring, rule enforcement and the division between automated and human oversight.
Operational Configuration
The settings that decide how a book behaves day to day — and the ones most often misconfigured.
Request documentation for a specific system
Tell us which component you are integrating with and we will send the relevant interface documentation for your environment.