Built for one trader today,
designed for desks later.
SwiftTrade is a privately run project in development. Today it serves its founder's own research and trading; the same engine is designed to carry teams and, one day, more. Each door says what exists now.
Private investors,
institutional discipline.
The full terminal on your own account: paper trading from the first minute, a research lab that deflates every result for the number of trials, and JARVIS narrating the tape for any instrument.
- Web terminal and desktop app on one account
- Paper broker with realistic costs, latency and partial fills
- Walk-forward lab and Monte-Carlo cones on your own strategies
- Two-factor sign-in, session control, audit trail
Several people,
one server.
The software already separates who can research, who can trade and who administers, and strategies move from research to approval only with recorded evidence and a second person's sign-off. SwiftTrade does not serve teams or family offices yet; this is the groundwork for when it does.
- Roles: user, researcher, trader, administrator
- Governance: backtested → validated → paper → approved (4-eyes)
- Shared audit log of every order, deploy and sign-in
- Personal API tokens for notebooks and automation
Your servers,
your data, your keys.
The engine runs on infrastructure you control: one process, one port, a Parquet lake and a hash-chained audit log. Production mode refuses to start without sign-in, secrets from the environment and pinned hosts. SwiftTrade is not an institution and serves none today; this is the direction it is built for.
- Self-hosted: your servers, your data, your keys
- Fail-closed production configuration (swifttrade doctor)
- Order-flow analytics on your own tick capture
- Documented APIs (OpenAPI) and a WebSocket stream