Self-host OrientDB with Levelrail
A multi model database for graphs and documents with the Studio web console, a generated root password and data volumes. The binary protocol port 2424 stays private.
- Authororientechnologies
- LicenceApache-2.0
- Memory1 GiB
- Services1
How to self-host OrientDB
-
Pull the images
One image is pulled on your server.
Show images
orientdb:3.2.58
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on ports 2480, 2424.
-
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.
After the first start
- Open Studio and sign in as root with the generated password from the app secrets.
OrientDB requirements
- Memory
- About 1 GiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 2480, 2424
- 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.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then OrientDB. 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 OrientDB docs page.
Deploy OrientDB your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy OrientDB from the CLI
levelrail-cli templates deploy orientdb --name my-orientdb Deploy OrientDB with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/orientdb/deploy OrientDB configuration
OrientDB services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| orientdb | orientdb:3.2.58 | 2480, 2424 | orientdb_databases -> /orientdb/databasesorientdb_backup -> /orientdb/backup |
OrientDB environment variables
| Variable | Service | Value |
|---|---|---|
| ORIENTDB_ROOT_PASSWORD | orientdb | Generated at deploy |
Ports and volumes
- Ports
- 2480, 2424
- Volumes
- 2 named mounts: orientdb_databases -> /orientdb/databases, orientdb_backup -> /orientdb/backup
OrientDB FAQ
How much memory does OrientDB need?
The catalog lists about 1 GiB of memory for OrientDB.
Does OrientDB run on arm64?
For OrientDB, arm64 support is not confirmed; amd64 is unknown.
What licence is OrientDB under?
OrientDB is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does OrientDB need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does OrientDB use?
OrientDB listens on ports 2480 and 2424 inside the stack.
Where does OrientDB keep its data?
In named volumes: orientdb_databases mounted at /orientdb/databases and orientdb_backup mounted at /orientdb/backup.
Can I deploy OrientDB 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 OrientDB, 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 orientdb:3.2.58 is what you deploy there.