Toolkien
Sign in Get started

Self-hosting

Run your own Toolkien with one Docker Compose stack, on any server or on Coolify.

Last updated 2026-11-14

Toolkien is open source under AGPL-3.0. The managed service is the easiest way to use it; self-hosting gives you the same product on your own infrastructure. When you self-host, you are the controller (and processor) of your users’ data, and our managed-service legal terms do not apply to your instance.

What you run

One Docker Compose stack with four services:

  • app: the SvelteKit application (web UI, OAuth server, MCP endpoint, bridge). The only public service.
  • openbao: secrets engine (transit) that wraps per-workspace data keys. Persistent volume, never in dev mode.
  • egress-proxy: the single exit to upstream MCP servers.
  • runner: Deno supervisor that runs each script in a permission-less process, on an internal-only network.

The database is libSQL: a Turso database (pick an EU region if you serve EU users) or a local file for small installs.

Requirements

  • A Linux server with Docker and Docker Compose, or a Coolify instance.
  • A domain with TLS in front of the app (Coolify’s proxy, Traefik or Caddy).
  • A Turso database URL and token, or a file: database on a volume.

Steps in short

  1. Clone the repository and copy deploy/compose.env.example to an env file; set ORIGIN, DATABASE_URL, BETTER_AUTH_SECRET, PLATFORM_ADMIN_EMAILS and the runner secret.
  2. Start the stack: docker compose --env-file .env.production up -d --build. On Coolify, use the Docker Compose build pack.
  3. Initialise OpenBao once with the provided script: keep the unseal keys and root token offline, create the transit key and the AppRole for the app, then revoke the root token. Put the AppRole role_id and secret_id in the app’s environment.
  4. Unseal OpenBao after every restart with the provided script (auto-unseal can come later).
  5. Run the database migrations, sign up, and use the platform admin panel at /admin (for emails listed in PLATFORM_ADMIN_EMAILS) to tune limits.

The repository’s docs/deploy-coolify.md is the step-by-step guide, including backups (Turso point-in-time restore plus a daily encrypted export, with a documented restore test) and OpenBao snapshots kept separate from database backups.

Operating notes

  • Single instance: rate limits, queues and scheduled jobs live in memory. Do not run two app instances at once (no rolling deploys with overlap).
  • Configuration is only through environment variables; nothing secret lives in the repository.
  • Logs: activity logs are kept for AUDIT_RETENTION_DAYS (90); configure your container log rotation to keep technical logs for 14 days.
  • Keep the legal pages of your instance accurate: the drafts in legal/ describe the managed service.