Your rules. Executed without you watching.
OmniMaster runs your strategy across exchanges, holds the risk limits you set, and reports every fill. You keep the keys and the kill switch.
Running on live capital since 2025. Written in Go.
Four services, one order
Every order passes the same four stages. Each stage is a separate service, and each one records what it did.
- 01
OmniAlpha
Reads the chart and publishes a signal. Nothing is ordered here.
- 02
OmniGuard
Checks the signal against your limits. A rejected signal stops here.
- 03
OmniTrader
Places the order, then trails the stop loss until the position closes.
- 04
OmniLedger
Settles fills into daily profit and loss you can audit.
They are separate on purpose. A signal engine that can also place orders is a signal engine that can place orders you never approved. Splitting them means the check in stage two cannot be skipped — there is no path around it.
Where you sit
OmniPortal — The four services run on their own. OmniPortal is where you watch them and where you change them.
Exchange connections and their live status. Positions and fills as they land. Your limits, your strategy slots, your kill switches — all set here, and enforced by the server, not by the page.
Manual orders start here too — and they pass the same check. Anything you place from OmniPortal goes through OmniGuard before it reaches an exchange, against the same limits, with no exception for being typed by hand. The path in stage two is the only path there is.
What stays yours
- Your API keys
- Stored encrypted with AES-256-GCM. Withdrawal permission is never required.
- Kill switch
- Four levels: account, exchange, proxy, user. Any one of them off stops new entries immediately. Positions already open are not abandoned — the stop loss keeps trailing until they close.
- Your limits
- Coins, timeframes, leverage, and how much each strategy slot may use. You set them, the server enforces them.
Why it is built this way
No withdrawal permission. A trading system does not need it. Asking for it buys the operator nothing and costs you everything — so we don't ask. The worst case here is an unwanted order, not an empty account.
A kill switch that abandons your positions is not protection. Cutting entries and closing positions are different jobs, and OmniMaster keeps them apart. Switching off means nothing new goes in. What is already in the market stays managed until it closes.
Not every exchange gets a connector. OmniMaster is venue-agnostic by design — CEX and DEX alike. In practice a connector ships only when the exchange can carry a system like this: a stable order lifecycle, honest fill reporting, documented behavior under load. Many cannot. Those we leave out, and we say so rather than shipping a connector that reports a fill that did not happen.
Nothing ships on a backtest alone. Every connector here has been through real fills, real rejects, and real outages on live capital.
Sign-up is by invitation
An invite code is required. Without one, the rest of the form stays closed.
Not because the door is small, but because the venue behind it is. Too many accounts running the same strategies into one exchange degrades fills for everyone holding them — including you. Invitations are how we keep the load spread across venues instead of stacked on one.
What we don't do
We don't publish returns, sell signals, or manage your money. Performance is yours to produce and yours to read. This system's job is to execute what you decided, exactly, every time.
For exchanges
If you operate a venue and want a serious execution client in front of your order book, we integrate on request. Tell us what your API can do under load.
[email protected]