The Quickstart bundle is the fastest path to a running Ekso. OneDocumentation Index
Fetch the complete documentation index at: https://ekso.dev/llms.txt
Use this file to discover all available pages before exploring further.
docker compose up -d brings up the API, the background worker, and a Postgres database with pgvector preinstalled. No external services to wire up.
Pick this if you’re evaluating Ekso, running it for a small team, or don’t already operate a Postgres or SQL Server you want it to share. For shops with an existing database, see Bring your own database.
Prerequisites
- Docker Engine 20+ on Linux, Docker Desktop on macOS or Windows
- ~2 GB free disk for first-time image pulls
- A free license — fetch one at ekso.app/get-started. The site emails you the personalized download link in the same step.
Install
-
Download the bundle from the link in your welcome email (
ekso-docker-stack.zip). -
Unzip somewhere persistent — for example
~/ekso/or/srv/ekso/. The zip contains: -
Bring it up from the unzipped directory:
On first run, Compose pulls
eksoapp/appandeksoapp/workerfrom Docker Hub, starts apostgrescontainer with pgvector, and the API auto-applies the database schema. Allow 30–60 seconds for everything to settle. -
Open the install URL to land in the first-run wizard:
What’s running
Three containers come up:| Service | Image | Role |
|---|---|---|
app | eksoapp/app | REST API + UI on port 6050 |
worker | eksoapp/worker | Background jobs — email, ticketing, vector indexing |
postgres | pgvector/pgvector:pg18 | OLTP + reporting database with pgvector preinstalled |
/var/ekso/storage — also volume-backed.
The bundle is multi-arch — same compose works on
linux/amd64 and linux/arm64 (Apple Silicon, Graviton, etc.). Docker pulls the right variant automatically.Pointing it at a real domain
For anything beyond local evaluation, run Ekso behind a reverse proxy that terminates TLS — Traefik, Caddy, nginx, your existing Cloudflare tunnel. Forward toapp:6050 and use that proxy’s URL as the public URL during the first-run wizard.
The ekso.json config file ships with a JWT signing key already pre-baked — you don’t need to edit it for a Quickstart install. See Configuration reference if you want to know what every field does or you need to override anything.