Self-host Spliit with Levelrail
A free way to split expenses with friends and groups, no accounts needed. Share a group link and everyone adds expenses. MIT licensed, backed by Postgres.
- Authorspliit-app
- LicenceMIT
- Memory384 MiB
- Archarm64
- Services2
How to self-host Spliit
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpineghcr.io/spliit-app/spliit:1.30.0
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 2 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.
Spliit requirements
- Memory
- About 384 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Spliit. 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 Spliit docs page.
Deploy Spliit your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Spliit from the CLI
levelrail-cli templates install spliit --name my-spliit Deploy Spliit with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/spliit/install \
-d '{
"name": "my-spliit"
}' Spliit configuration
Spliit services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | pgdata -> /var/lib/postgresql/data |
| spliit | ghcr.io/spliit-app/spliit:1.30.0 | 3000 | none |
Spliit 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 |
| POSTGRES_PRISMA_URL | spliit | Generated at deploy |
| POSTGRES_URL_NON_POOLING | spliit | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: pgdata -> /var/lib/postgresql/data
Spliit FAQ
How much memory does Spliit need?
The catalog lists about 384 MiB of memory for Spliit across its 2 services.
Does Spliit run on arm64?
For Spliit, an arm64 image is published; amd64 is image published.
What licence is Spliit under?
Spliit is licensed under MIT, which is permissive, with few conditions on reuse.
Does Spliit need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Spliit bundle?
The template includes Postgres, running as its own service.
Which ports does Spliit use?
Spliit listens on port 3000 inside the stack.
Where does Spliit keep its data?
In a named volume: pgdata mounted at /var/lib/postgresql/data.
Can I deploy Spliit 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 spliit for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, ghcr.io/spliit-app/spliit:1.30.0 is what you deploy there.