This project is not yet finished. Public release planned end of 2026.Contact us for details
Guides

Self-Hosting Ionide

What the installer does, what it needs from you, and how to update or reconfigure it.

Ionide's bot only runs self-hosted. There's no hosted alternative. This page covers what the installer does and how to manage the container afterward. For the end-to-end walkthrough, start at Getting Started.

New to self-hosting? It just means running the bot on a machine you control instead of a service we run for you. A small VPS (see cost and specs below) works fine — it doesn't need to be powerful, just online whenever you want Ionide actively managing positions.

Requirements

  • A Linux host with Docker (the installer will offer to install Docker if it's missing).
  • A Discord bot application and token (see below if you don't have one yet).

What server should I choose?

Choose a small Linux VPS. You do not need to understand Docker, Java, memory heaps, or container settings — the installer handles those parts.

  • Memory: 512 MB minimum; 1 GB recommended. This gives the bot and Docker comfortable room.
  • Storage: 5 GB free minimum; 10 GB recommended for updates and normal Docker housekeeping.
  • CPU: one virtual CPU is enough.
  • Network: keep the server online while you want Ionide to monitor and manage positions.

The bot itself uses little storage: encrypted exchange credentials, activation state, and small operational data stay on the server. The extra disk headroom is for Docker images and updates, not for a large local trade-history database.

In practice, a basic $4–5/month VPS plan with 1 GB RAM and 10 GB storage is plenty.

Free VPS options

Ionide's footprint is small enough to fit some providers' permanently-free tiers, not just paid trials:

  • Oracle Cloud "Always Free" — an Ampere ARM instance (4 OCPU / 24 GB RAM) is free forever, far more than Ionide needs. Requires a card on file for signup even though nothing is charged on the free tier, and Oracle has been known to reclaim idle free instances in some regions if usage looks too low, or to have capacity temporarily unavailable in popular regions.
  • Google Cloud "Always Free" — one e2-micro instance (1 GB RAM) is free forever, but only in specific US regions (us-west1, us-central1, us-east1). Fits Ionide's footprint fine.
  • AWS Free Tier and Azure free trial — both offer a small instance for 12 months only, then bill normally. Fine for testing, not a permanent free option.

The tradeoff: free tiers don't come with a guaranteed uptime SLA the way a paid VPS effectively does through the provider's own reputation and support. Oracle's idle-reclaim policy in particular means a free instance can, in principle, get taken back if it looks unused — a real risk for a bot meant to run unattended for months. A paid $4-5/month VPS is the more predictable choice for continuous, hands-off position management; a free tier is a reasonable way to try Ionide out first or to run it if you're comfortable monitoring uptime yourself.

Creating a Discord bot token

  1. Go to the Discord Developer Portal and create a New Application.
  2. Open the Bot tab, click Reset Token, and copy the token. You'll paste this into the installer.

Running the installer

curl -fsSL https://install.ionide.net | bash

The installer:

  1. Checks for Docker and offers to install it via Docker's official convenience script if it's missing.
  2. Prompts once for your Discord bot token.
  3. Generates a SECRETS_ENCRYPTION_KEY and writes both values to a local .env file. This key encrypts your exchange API secrets at rest. Back it up, since losing it means losing access to any exchange credentials you've stored via /secrets action:set.
  4. Starts the bot and keeps it running after a server restart. Your local bot data is retained across updates.
  5. Waits for the bot to come online and prints a Discord invite link built from your bot token.
  6. Prints a current public IPv4 address if its optional one-time lookup succeeds. Add it to an exchange API-key allowlist only when you know the address is stable; it is never stored or sent to Ionide. See Security & Data.

Invite the bot using the printed link, then continue with connecting your account.

Updating

Ionide updates itself by default. It checks for a new version every hour, then installs it when it is safe: no position is close to liquidation and no funding settlement is due soon. You do not need to SSH into the server for normal updates.

If a new version cannot start correctly, Ionide automatically returns to the previous version and notifies bot owners. Run /update-check in Discord when you want to check for an update and approve it now instead of waiting for the next safe automatic update.

Re-run the installer only to repair an installation or refresh its setup files. It keeps your bot token and encryption key:

curl -fsSL https://install.ionide.net | bash

To change your Discord bot token or regenerate the encryption key, pass --reconfigure:

curl -fsSL https://install.ionide.net | bash -s -- --reconfigure

Where things live

  • .env: your Discord bot token and encryption key.
  • /app/data (Docker volume): the bot's local database, including your encrypted exchange credentials and activation state. Back this up along with the encryption key if you move hosts.

Troubleshooting

  • Container won't come up / installer hangs waiting for it: check docker logs ionide-discord-bot for errors. A missing or invalid bot token is the most common cause.
  • Commands don't respond in Discord: the bot blocks every command except /setup until a license has been activated. Run /setup first.
  • Still stuck? Ask in Discord.