Self-host Grist with Levelrail
A modern relational spreadsheet that combines spreadsheet flexibility with database structure.
- Authorgristlabs
- LicenceApache-2.0
- Memory512 MiB
- Archarm64
- Services3
How to self-host Grist
-
Pull the images
3 images are pulled on your server.
Show images
postgres:16-alpinegristlabs/grist:1.3.3redis:7-alpine
-
Create the app
3 services start in a single Compose app, with 3 named volume mounts for your data, on port 8484.
-
Fill in the secrets
5 secrets are generated and stored encrypted, 5 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.
Grist requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8484
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, 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 8484 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 Grist. 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 Grist docs page.
Deploy Grist your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Grist from the CLI
levelrail-cli templates deploy grist --name my-grist Deploy Grist with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/grist/deploy Grist configuration
Grist services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | grist_db_data -> /var/lib/postgresql/data |
| grist | gristlabs/grist:1.3.3 | 8484 | grist_data -> /persist |
| redis | redis:7-alpine | none | grist_redis_data -> /data |
Grist environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Generated at deploy |
| GRIST_SESSION_SECRET | grist | Generated at deploy |
| REDIS_URL | grist | Preset by the template |
| TYPEORM_DATABASE | grist | Preset by the template |
| TYPEORM_HOST | grist | Preset by the template |
| TYPEORM_PASSWORD | grist | Generated at deploy |
Show all 10 variables
- TYPEORM_TYPEgristPreset by the template
- TYPEORM_USERNAMEgristGenerated at deploy
Ports and volumes
- Ports
- 8484
- Volumes
- 3 named mounts: grist_db_data -> /var/lib/postgresql/data, grist_data -> /persist, grist_redis_data -> /data
Grist FAQ
How much memory does Grist need?
The catalog lists about 512 MiB of memory for Grist across its 3 services.
Does Grist run on arm64?
For Grist, an arm64 image is published; amd64 is image published.
What licence is Grist under?
Grist is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Grist need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Grist bundle?
The template includes Postgres and Redis, running as its own service.
Which ports does Grist use?
Grist listens on port 8484 inside the stack.
Where does Grist keep its data?
In named volumes: grist_db_data mounted at /var/lib/postgresql/data, grist_data mounted at /persist and grist_redis_data mounted at /data.
Can I deploy Grist 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 grist for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, gristlabs/grist:1.3.3, redis:7-alpine is what you deploy there.