Self-hosting
Run the whole Grovs platform on your own infrastructure as one Docker Compose stack.
Which edition you run
The open-source stack runs Grovs Community: free, MIT-licensed, and the complete links and analytics product for up to 100,000 users. Grovs Enterprise is a licensed self-hosted edition with everything in Community plus engagement, revenue, data export and compliance features.
Pages for Enterprise features say so at the top. Talk to sales about Enterprise.
What you run
The grovs-io/self-host repository bundles the backend, dashboard, PostgreSQL, Redis, ClickHouse, background workers and a reverse proxy with automatic TLS. The application ships as two GHCR images released together under one version, GROVS_VERSION:
| Image | Runs |
|---|---|
ghcr.io/grovs-io/backend | API, link redirects, migrations and both workers |
ghcr.io/grovs-io/dashboard | Web dashboard |
The source is open at grovs-io/backend and grovs-io/dashboard. Architecture shows every service and how traffic reaches it.
Self-hosted mode turns off billing and public sign-up, removes usage quotas, and lets you invite members with a copyable link instead of email.
Requirements
| Requirement | Value |
|---|---|
| Server | Linux with Docker and Docker Compose v2, ports 80 and 443 open |
| Size | 4 vCPU, 8 GB RAM, 80 GB SSD for up to 100,000 users. See Sizing. |
| Domain | One domain you control, with wildcard records. A separate branded links domain is optional. |
Choose a path
lvh.me. No domain or DNS needed.Setup generates your secrets and the first administrator login. No application build or SMTP is required. Cloud and platform deployments use paid resources in your own account.
Import the preview service template.
Easypanel setup guide Get Easypanel template (opens in a new tab)Import the preview One Click App template.
CapRover setup guide Get CapRover template (opens in a new tab)Create a VM with guided Cloud Shell setup.
Deploy on Google Cloud Open in Cloud Shell (opens in a new tab)Create an Ubuntu VM from an ARM template.
Azure setup guide Deploy to Azure (opens in a new tab)Run the full stack on a Droplet.
DigitalOcean setup guide Open DigitalOcean Console (opens in a new tab)Provision Grovs on an Ubuntu Cloud server.
Hetzner setup guide Open Hetzner Console (opens in a new tab)Run Grovs on a Cloud Compute instance.
Vultr setup guide Open Vultr Console (opens in a new tab)Deploy the Compose stack on a Linode.
Akamai / Linode setup guide Open Akamai / Linode Console (opens in a new tab)Install Grovs on an Ubuntu Instance.
Scaleway setup guide Open Scaleway Console (opens in a new tab)Create the full stack from the Railway template.
Railway setup guide Deploy on Railway (opens in a new tab)Create the services from a Render Blueprint.
Deploy on Render Deploy on Render (opens in a new tab)Go to production
Before real traffic arrives, work through the production checklist. It covers DNS and certificates, secrets, email, backups, monitoring, firewall, updates and SDK setup.
How updates work
Backend and dashboard always run the same release. Pin a numbered version, then pull, run migrations and restart. See Upgrades and Images and releases.