Most Ionide users run on the hosted service at app.ionide.net, but the engine is built to run as a self-hosted instance too — for anyone who'd rather operate their own infrastructure than rely on ours.
Why self-host
A few reasons users have given us for wanting this:
- Full control over infrastructure — your own servers, your own network boundary, your own logging and monitoring stack.
- No dependency on our uptime — a self-hosted instance keeps running on your own terms.
- Comfort with the stack — if you're already running Docker services, adding one more is a small lift.
What you'll need
- Docker and Docker Compose.
- Exchange API keys scoped to trading only — see Setting Up API Keys Safely before you generate anything.
- Comfort reading container logs and setting environment variables. This is a self-hosted deployment aimed at technically inclined users, not a one-click installer — at least not yet.
The shape of a deployment
A self-hosted setup runs the same pieces as the hosted product: a persistence layer, the trading engine itself, and an API layer in front of it. Every service reads its configuration from its own environment file rather than a shared config, so the first real step is reviewing and setting those values for your environment before starting anything.
Licensing
Self-hosting runs on an annual, renewable license rather than the hosted service's fee model — see the pricing page for current rates, including the current early-adopter discount for new licenses.
What's still in progress
We're actively building a guided setup script to shrink this from "read the docs and wire it up yourself" to something much closer to one command. If you want to be first to know when it lands, watch this space or reach out via Contact — happy to point you in the right direction in the meantime.
Get new posts in your inbox
Strategy breakdowns and product updates — no spam, unsubscribe anytime.
