Self-host marimo with Levelrail
A reactive Python notebook that is reproducible, git-friendly, and shareable as an app.
- Authormarimo-team
- LicenceApache-2.0
- Memory1 GiB
- Archarm64
- Services1
How to self-host marimo
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/marimo-team/marimo:latest-sql
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 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.
marimo requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- 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 8080 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 marimo. 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 marimo docs page.
Deploy marimo your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy marimo from the CLI
levelrail-cli templates deploy marimo --name my-marimo Deploy marimo with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/marimo/deploy marimo configuration
marimo services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| marimo | ghcr.io/marimo-team/marimo:latest-sql | 8080 | marimo_data -> /app |
marimo environment variables
| Variable | Service | Value |
|---|---|---|
| MARIMO_TOKEN_PASSWORD | marimo | Generated at deploy |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: marimo_data -> /app
marimo FAQ
How much memory does marimo need?
The catalog lists about 1 GiB of memory for marimo.
Does marimo run on arm64?
For marimo, an arm64 image is published; amd64 is image published.
What licence is marimo under?
marimo is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does marimo need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does marimo use?
marimo listens on port 8080 inside the stack.
Where does marimo keep its data?
In a named volume: marimo_data mounted at /app.
Can I deploy marimo on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for marimo, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/marimo-team/marimo:latest-sql is what you deploy there.