Getting started with Orkovia in 15 minutes
Run Orkovia on your own computer with Docker, sign in, deploy a first process and start an instance.
In short
- 01
Everything runs locally in Docker — nothing leaves your machine.
- 02
Two sites: the app (run and monitor) and Studio (design).
- 03
One command starts it; one command stops it and keeps your data.
Orkovia ships as a Docker bundle with a small start script. This guide takes you from an empty machine to a running process instance.
What you need
- Docker Desktop (Windows or macOS) or Docker Engine with the Compose plugin (Linux), with at least 4 GB of memory
- About 3 GB of free disk space
- The Orkovia beta bundle and the registry username and token that come with it
Start Orkovia
Log in to the image registry (once)
Start everything
Open the two sites
./orkovia.sh login
./orkovia.sh startDeploy your first process
Draw it in Studio
Deploy
Start an instance
Complete the task
Everyday commands
| Command | What it does |
|---|---|
| start | Start everything |
| stop | Stop; your data is kept |
| status | Show what is running |
| logs | Follow the logs |
| update | Download newer images and restart |
| password | Show the admin password again |
| backup | Write a database backup to the backups folder |
| reset | Stop and delete all data (asks you to confirm) |
Use the API
The REST API is served from the same address as the app. Sign in to get a token, then send it as a bearer token on every other call.
curl -X POST http://localhost:3000/api/v1/auth/login \
-H "Content-Type: application/json" \
-d '{"username": "admin", "password": "<your password>"}'See it on your own process
Book a walkthrough with the Orkovia team.
Keep reading
Importing models from Camunda 8
What carries over when you open a Camunda 8 (Zeebe) BPMN model in Orkovia, and what you need to fix by hand.
Read articleTest a process before you deploy it: Play mode
Step through a diagram node by node inside the designer, choose gateway branches, and watch variables change — without deploying anything.
Read articleBuild without the backend: mocking service tasks
Give a service task a pretend response, delay and failure rate, so you can run the whole process before the real system or worker exists.
Read article