docker-compose.yml's quick-start exec'd ./apikey_admin inside the backend container, but the Dockerfile only built/copied the reacher_backend binary -- that command would have 404'd on a fresh deploy. Also wires DATABASE_URL (the var apikey_admin reads) alongside the existing RCH__STORAGE__POSTGRES__DB_URL, and drops the version key Compose v2 flags as obsolete.
One-click self-host deploy
Three ready-to-run deploy targets, all pointing at the same backend/Dockerfile
and all enabling multi-tenant API keys (RCH_ENABLE_API_KEYS=1) out of the
box. Pick whichever matches where you already run infrastructure — these are
the exact three reference points the landing page's cost calculator
(site/lib/competitors.ts) uses for the "self-host ~$X/mo" numbers.
| Target | File | Reference cost |
|---|---|---|
| Any VPS (Docker Compose) | docker-compose.yml |
~$6/mo (1 vCPU / 1GB VPS) |
| Fly.io | fly.toml |
Free tier covers low volume; ~$5-8/mo beyond it |
| Render | render.yaml |
Free Postgres + $7/mo Starter web service |
Docker Compose (any VPS, your own server, a NAS, etc.)
cd deploy
cp .env.example .env # set RCH_PUBLIC_URL once you have a domain pointed here
docker compose up -d
# Issue your first API key once the backend is healthy:
docker compose exec backend ./apikey_admin create --owner "you@example.com" --plan free --quota 1000
Reverse-proxy port 8080 behind TLS with Caddy, nginx, or Traefik to get a
real https:// endpoint. This is the deployment the "self-host ~$6/mo"
claim on the landing page is computed from.
Fly.io
cd deploy
fly launch --copy-config --name <your-app-name> --no-deploy
fly postgres create --name <your-app-name>-db
fly postgres attach <your-app-name>-db -a <your-app-name>
fly secrets set RCH_ENABLE_API_KEYS=1 RCH__PUBLIC_URL="https://<your-app-name>.fly.dev"
fly deploy
Render
Push this repo (or your fork) to GitHub, then in the Render dashboard choose
New > Blueprint and point it at deploy/render.yaml. Render provisions
the free Postgres instance and the web service, and wires
RCH__STORAGE__POSTGRES__DB_URL automatically via fromDatabase.
To get a literal one-click "Deploy to Render" button once this repo (or your
fork) is public, add this to the top-level README.md:
[](https://render.com/deploy?repo=https://github.com/<your-org>/check-if-email-exists)
After deploying anywhere above
- Create your first API key:
apikey_admin create --owner <label> --plan <name> --quota <n>. - Send that key as the
x-reacher-secretheader to/v0/check_email,/v0/check_email/simple,/v0/bulk,/v1/check_email, or/v1/bulk. - Watch the startup logs once —
warn_if_port_25_blockedtells you immediately whether your host's outbound port 25 is open; if it's blocked (common on AWS/GCP/Azure/DigitalOcean/Oracle Cloud by default), configure a[proxy]inbackend_config.tomlinstead of discovering this later via silently-unknownresults.