Self-host

Run the entire meetbot stack on your own infrastructure. Docker Compose for one-machine setups, Helm chart for Kubernetes. MIT-licensed; no metering loop, no phone-home.

We ship the same orchestrator + bot images that power meetbot.dev. Self-host is the path you pick when data residency, air-gapped networks, or bot-hour volume above ~1,000 hr/month make the hosted plan the wrong fit.

Three ways to run it

Docker Compose →

Single-machine. 5-minute setup. Perfect for one-host deployments and dev environments.

Helm chart →

Kubernetes. HPA on the worker, in-cluster Postgres or BYO managed PG.

Hosted →

Skip ops entirely. $0.30/hr, EU-hosted, $5 free credit. We run it.

What's in the bundle

Service	What it does
`orchestrator`	HTTP API on `:3010`. Job dispatch, webhooks, admin.
`orchestrator-worker`	pg-boss queue. Spawns bot containers per job.
`postgres`	Job state, OAuth credentials, webhook delivery log.
`caddy`	TLS-terminating reverse proxy. Auto Let's Encrypt certs.

The bot image (ghcr.io/meetbot-dev/bot:latest) is pulled on demand by the worker. Real Chrome + Xvfb + ffmpeg, ~750 MB compressed.

What's different from hosted

Read the honest list at github.com/meetbot-dev/self-host#limitations-vs-hosted. The headline gaps:

Calendar V2 (OAuth-managed scheduling) is off — needs public callback URLs that self-hosters can't always offer. Workaround documented in the repo README.
Email intake (bot@meetbot.dev) runs on Cloudflare Workers in hosted; self-hosters wire their own SMTP receiver.
Stripe billing is off by default — you're not paying us. Wire it only if you bill your own customers downstream.
Hosted dashboard (the Next.js UI) isn't shipped — bring your own frontend or call the API directly.

Everything else is identical: same bot adapters, same per-speaker audio, same webhook signatures, same migrations.

Quick start

git clone https://github.com/meetbot-dev/self-host
cd self-host
cp .env.example .env  &&  $EDITOR .env
./init-db.sh
docker compose up -d
curl https://api.your-domain.com/healthz   # → ok

Then dispatch your first bot — it's the same SDK call as hosted, just point baseUrl at your own API endpoint.

import { createMeetbot } from "@meetbot/sdk";

const meetbot = createMeetbot({
  apiKey: process.env.MEETBOT_ADMIN_SECRET!,
  baseUrl: "https://api.your-domain.com",
});

await meetbot.dispatchBot({
  url: "https://meet.google.com/abc-defg-hij",
  externalId: "selfhost-test",
  webhooks: { onFinalize: "https://yours.example/hook" },
});

Working sample: samples/self-host/.