Built, not bought
The research protocol, the execution engine, the risk monitoring and the operating model behind Algotoria — including what we have tried and rejected.
Every layer is ours to inspect
Algotoria builds the pieces that determine whether a strategy survives contact with a real market — the research protocol, the execution path, the risk controls and the record of what happened. Owning them is what makes it possible to say precisely how each one behaves, including where it falls short.
Machine-learning research
Algotoria runs its research as a set of numbered, self-contained experiments, each with its own data, configuration, harness and written record. Work does not graduate because a backtest looked good. It graduates by climbing a fixed evaluation ladder — smoke test, signal triage, single-seed screen, a three-seed reproduction, nested walk-forward at book level, a robustness battery, a shadow window, and finally a pre-registered, one-look forward gate whose pass criteria are written down before the out-of-sample window is ever read.
That last rule is the point of the whole apparatus. The forward window is opened once, against criteria fixed in advance, and the result stands either way. Supporting it are a leak-free data protocol that masks the boundary between training and held-out data, a registry of numbered robustness laws distilled from earlier mistakes, and append-only ledgers of adopted, rejected and pending verdicts — each entry auto-stamped with its date and the exact commit that produced it, so any decision can be reconstructed years later.
The models themselves are built in house. The current line is a multi-scale convolutional network that reads one five-minute bar stream at four horizons at once — five minutes, one hour, twelve hours and seven days — through a purpose-built temporal encoder with cross-instrument wiring. It is now in its fifth generation, and each generation is a documented architectural change rather than a re-tune. The most distinctive piece is not the network but the target it learns: an in-house label that compresses move size and how long the move persists into a single continuous position, computed net of realistic trading costs and under a volatility-scaled stop, so the model is optimising something an account can actually capture.
Alongside price-derived work, Algotoria maintains an active research programme into exogenous signals — order-book liquidity and depth imbalance, social and news-flow sentiment, on-chain activity such as address counts and whale transfers, and capital-flow measures such as exchange net flows and stablecoin supply. These are researched properly and judged by the same ladder as everything else. To date none has earned a place in a production model: the edge has repeatedly proved to live in multi-scale price behaviour itself. We publish that outcome because a research programme that never rejects anything is not a research programme.
Every model is trained on Algotoria’s own hardware, through Algotoria’s own data downloaders, backtester and optimiser. No training is outsourced and no third-party modelling service is used.
- Evaluation ladder
- Eight stages, R0 to R7, ending in a pre-registered one-look forward gate
- Reproduction
- Three fixed seeds before any result is believed
- Selection metric
- Calmar (CAGR ÷ max drawdown), with hard disqualification above 30% max drawdown
- Cost realism
- Round-trip cost bands calibrated per venue — Binance, OKX and Bybit modelled separately, 14 to 28 bps
- Training
- In house, on own research hardware, through an own end-to-end pipeline
Algotoria Spike is the product of this research line. It has not launched, no client has ever held it, and its published figures are simulated and carry that marker wherever they appear.
Read the Algotoria Spike overviewThe Executor engine
Between a signal and a filled order sits the cost of trading: fees, spread, slippage and funding. Algotoria built its own execution engine rather than buy one, because that cost is where a systematic strategy quietly loses the edge the research found. The engine is clean-room work — the exchange clients for OKX, Binance and Bybit are written by hand against each venue’s own specification, and both an earlier third-party trading library and an outside contractor’s component were retired in the process.
It works on a target-position model: a signal states the exposure an account should hold, and the engine converges the account towards it. Intake is fast and stateless — an incoming signal is acknowledged, typically within a quarter of a second, before any exchange is touched — and the actual convergence is done by parallel workers.
Execution is maker-first by design. Orders are placed as post-only limits by default, with a per-instrument price adjuster that tunes how aggressively to sit in each market according to that market’s own liquidity. Market orders exist only as a capped fallback for an order that has gone stale, and that fallback stops immediately if it is not filling. Around this sit the unglamorous things that actually save basis points: orders batched to each venue’s maximum, amended in place instead of cancelled and replaced, and split into deterministic chunks so the full size is never shown to the book. Slippage is measured per account and per instrument, not assumed, and an alert fires when it drifts outside its expected band.
The engine runs as stateless services — redundant intake behind a load balancer, a horizontally scalable worker pool, and a sharded, replicated data store — deployed across three availability zones in its primary cloud region, with a second-region instance that can be promoted if the primary region is lost.
- Order policy
- Post-only limit by default; capped market fallback only for a stale order
- Measured cost today
- ≈11.3 bps all-in round trip — roughly 1.1 bps fees, 4.3 bps slippage and 0.3 bps funding per side, against 20 bps assumed in research
- Maker share today
- 73 / 27 maker-to-taker by volume; the Executor upgrade targets fully passive placement
- Batching
- Up to 20 orders per batch on OKX and Bybit, 5 on Binance, with in-place amendment
- Account scale
- Designed around 200 independent accounts per venue, with capacity analysis to roughly 500
- Resilience
- Stateless services across three availability zones, plus a promotable second-region instance
Status. Development is complete and the engine has been validated end to end on demo accounts. It is progressing through staged hardening and a controlled live launch on small balances that is then widened. Until that completes the established execution path remains in service, and the published track record is unaffected by the migration.
Read the Executor release notesRisk monitoring
The Algotoria Monitoring System is proprietary and deliberately separate from the machinery it watches. It is entirely independent of signal generation and trade execution, connects through its own read-only API keys, and is hosted inside a private cloud network isolated from the public internet. It can observe every account and change none of them — which is precisely what makes it trustworthy as a control.
It tracks more than ten risk parameters for every separately managed account and raises real-time alerts to the NOC and the trading team whenever one crosses a pre-defined threshold. Alerts are graded, and the thresholds sit deliberately below the limits themselves, so a problem is escalated while there is still room to act rather than at the moment the limit is breached.
Monitoring runs against hard portfolio limits rather than opinions. Gross market value is capped at three times account equity, and in practice the daily average sits well below that. Each strategy carries a 95% one-day Value-at-Risk ceiling, no single sub-strategy may contribute more than 5% of that figure, and drawdown budgets are staged — the first stage at two-thirds of the budget triggers an Investment Committee review of the account, the second at the full budget puts the decision to the client.
Underneath it all is comprehensive structured logging across the trading, execution and monitoring estate — every alert, collector run, order and reconciliation recorded in a queryable form, which is what allows any position, fill or alert to be reconstructed after the fact for a client, an auditor or a post-incident review.
- What triggers an alert
- Position deviation from the master account, leverage above two-thirds of the account limit, drawdown at two-thirds of budget, daily loss beyond 5%, insufficient margin, and API or connectivity errors
- Leverage
- Hard cap of 3× gross market value to AUM; typical daily average 0.8× to 1.0×
- Value at Risk
- 95% one-day limit of 2.0% on Stable and 2.2% on Diversified; maximum 5% single-contributor share
- Isolation
- Separate read-only API keys, private network, independent of signal generation and execution
- Human cover
- A dedicated NOC/SOC on continuous global shifts — 24/7/365
Automated telemetry is the floor, not the ceiling. A dedicated Network and Security Operations Centre runs continuous shifts globally, so an algorithmic anomaly or an exchange API degradation is triaged by a human engineer at any hour. In practice that human intervention is needed roughly once a month.
24/7 client support
Clients reach the Monitoring System through the Algotoria Telegram bot. It answers on demand, at any hour, without going through a relationship manager: current balance, profit and loss and a generated chart over a chosen interval — 24 hours, 7, 30 or 90 days, a year, or since inception — for any account you hold. Clients with more than one separately managed account switch between them in the same session.
Beyond status, the bot issues quarterly reports with the profit-and-loss figure, the high-water mark and the Success Fee calculation behind it; sends daily, weekly or monthly notifications on a schedule you configure; and generates read-only share links for anyone you want to give visibility to, such as an adviser or an auditor. It speaks English and Russian. Access is granted per account by your relationship manager, and the bot is strictly read-only — it cannot place a trade or move funds.
In development is an agentic assistant with natural-language input: rather than choosing from a command list, you will be able to ask a nuanced question about your account, your fees or the strategy and have it compose the answer and the supporting report. It is being built on the same principle as everything else here — grounded in the firm’s own knowledge base, read-only with respect to your money, and escalating anything legally or financially significant to a named human.
- Available now
- Account status and P&L charts, multi-account switching, quarterly reports, scheduled notifications, read-only share links
- Languages
- English and Russian
- Permissions
- Read-only — no trade execution, no fund movement
- In development
- Natural-language agentic assistant for nuanced questions and generated reports
An AI-native firm
Algotoria is an AI-native asset manager. Beyond the systematic trading engine itself, every operational function — research, software development, operations, client support, compliance and accounting — is executed through AI-assisted workflows under human-in-the-loop oversight, governed by the firm’s Board-approved AI and External Data Provider Policy.
The boundary is absolute and worth stating plainly. Trading is deterministic and non-discretionary. Live signal generation and order execution are governed by algorithms, not by language models. AI sits one layer above the trading loop, in the work that surrounds it.
What makes that layer work is a knowledge base built to be read by machines as well as people. The firm’s wikis carry routing tables that send an agent to the one authoritative file for a question, a standing rule that answers must be grounded in a cited section rather than general knowledge, and an explicit instruction to say “the wiki is silent” rather than guess. On top of that sit detailed playbooks — written procedures for recurring work such as compliance forms, the monthly performance refresh, client-guide verification and wiki maintenance — which an agent follows step by step instead of improvising. The result is that two agents, or an agent and a new employee, answer the same question the same way, from the same source, with the citation attached.
Every consequential decision has a named gatekeeper. Nothing that moves money, changes risk, or reaches a client passes on an agent’s own authority.
- Trading strategy
- The Investment Committee governs the strategy roster and weights, and gates promotion from incubation to production; a new strategy must additionally clear its pre-registered forward gate plus owner sign-off
- Risk limits
- Any change to a hard-coded risk limit requires unanimous Investment Committee approval and notification to the Board
- Production deployment
- Merge-request only, through feature to dev to stage to main; agents work in isolated worktrees and never push to a protected branch; every diff is reviewed by a named human engineer
- Compliance and client matters
- Account opening, AML case closure and regulator filings require a named human reviewer; the MLRO approves in writing any AI use touching KYC/AML data
- Client-facing output
- Every client-facing deliverable is reviewed and signed off by a named human before despatch
- Governance
- Board-approved AI and External Data Provider Policy, aligned to ISO/IEC 42001 and 23894, ISO/IEC 27001 and 27701, the NIST AI Risk Management Framework, the OWASP LLM Top 10 and the EU AI Act
This is also the structural reason Algotoria charges no management fee. AI-native operations lift the productivity of a deliberately lean team far enough that the firm can run on performance fees alone.
Meet the people who hold the gatesYou do not have to take our word for any of it
The live track record streams through a read-only exchange API to a third-party verification service, so every published figure is reproducible from data Algotoria does not control. On request, read-only keys can be provisioned directly to your own auditor.