Self-hosting Evermach
Run Evermach on Railway, AWS, Google Cloud, Azure, or DigitalOcean: what a deployment runs and what you provide.
Self-hosted Evermach is licensed under a separate agreement. Email [email protected] to talk about it and to get the full environment reference.
Where you can run it
Run self-hosted Evermach in your own account on any of these platforms:
- Railway
- Amazon Web Services (AWS)
- Google Cloud
- Microsoft Azure
- DigitalOcean
Each service below runs as a container, alongside a PostgreSQL database.
What runs
| Service | What it does |
|---|---|
| Web | The website, dashboard, widget, APIs, and MCP server (Next.js, port 3000). |
| Worker | Drift Control™ analysis, codebase overviews, and security scans. |
| Code-run | Builds, code and security reviews, and pull requests. |
| Uptime | Checks the website addresses your teams monitor. |
| PostgreSQL | The database for everything above (PostgreSQL 18). |
What you provide
- A PostgreSQL database and a domain with HTTPS.
- Your own Anthropic and/or OpenAI API keys. All model usage goes to your own provider accounts.
- A Railway API token for the worker and code-run services. Analysis and builds run in Railway's isolated sandboxes, whichever platform runs the rest of Evermach.
- Email through SMTP or Mailgun.
- File storage on the server's disk or in an S3-compatible bucket, such as Amazon S3 or DigitalOcean Spaces.
- Your own GitHub App (see below).
Register your GitHub App
- Set the callback URL to
https://your-domain/api/integrations/github/callback. - Set the webhook URL to
https://your-domain/api/integrations/github/webhook, add a webhook secret, and subscribe to Push events. - Grant the permissions listed in GitHub access and permissions.
Upgrades
Each release includes database migrations. Run them before starting the new version with bun run db:deploy.
Questions about anything here? Email [email protected] or book a demo.