Self-host Hoppscotch with Levelrail
An open-source API development platform, a self-hosted alternative to Postman, backed by Postgres.
- Authorhoppscotch
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services2
How to self-host Hoppscotch
-
Pull the images
2 images are pulled on your server.
Show images
postgres:15-alpinehoppscotch/hoppscotch:2026.2.1
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 6 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Hoppscotch requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Hoppscotch. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Hoppscotch docs page.
Deploy Hoppscotch your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Hoppscotch from the CLI
levelrail-cli templates deploy hoppscotch --name my-hoppscotch Deploy Hoppscotch with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/hoppscotch/deploy Hoppscotch configuration
Hoppscotch services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:15-alpine | none | hoppscotch_db_data -> /var/lib/postgresql/data |
| hoppscotch | hoppscotch/hoppscotch:2026.2.1 | 80 | none |
Hoppscotch environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| DATABASE_URL | hoppscotch | Generated at deploy |
| DATA_ENCRYPTION_KEY | hoppscotch | Generated at deploy |
| ENABLE_SUBPATH_BASED_ACCESS | hoppscotch | Preset by the template |
| VITE_ALLOWED_AUTH_PROVIDERS | hoppscotch | Preset by the template |
| VITE_BASE_URL | hoppscotch | Preset by the template |
Show all 9 variables
- WHITELISTED_ORIGINShoppscotchPreset by the template
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: hoppscotch_db_data -> /var/lib/postgresql/data
Hoppscotch FAQ
How much memory does Hoppscotch need?
The catalog lists about 512 MiB of memory for Hoppscotch across its 2 services.
Does Hoppscotch run on arm64?
For Hoppscotch, an arm64 image is published; amd64 is image published.
What licence is Hoppscotch under?
Hoppscotch is licensed under MIT, which is permissive, with few conditions on reuse.
Does Hoppscotch need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Hoppscotch bundle?
The template includes Postgres, running as its own service.
Which ports does Hoppscotch use?
Hoppscotch listens on port 80 inside the stack.
Where does Hoppscotch keep its data?
In a named volume: hoppscotch_db_data mounted at /var/lib/postgresql/data.
Can I deploy Hoppscotch on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id hoppscotch for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:15-alpine, hoppscotch/hoppscotch:2026.2.1 is what you deploy there.