Development deployment

From a repository clone or extracted release archive:

./release/abada-platform doctor dev
./release/abada-platform up dev

The first command creates .env.dev from release/.env.dev.example, validates Docker and Compose, checks ports and image availability, and renders the final configuration. The stack exposes only Traefik on port 80 and its loopback-only dashboard on 8080. PostgreSQL is not published to the host.

Up also starts the Agent Worker automatically: it provisions Keycloak and the engine idempotently, registers the global abada:agent capability and begins polling project-agnostically. Pass --no-agent only when you need a core-stack diagnostic run. See Agent nodes and the Agent Worker.

Development identities

The bundled realm provides accounts for the Studio operator UI:

Application	Username	Password	Access
Studio	alice	alice	Task work, operations, process control and deployment
Keycloak administration	admin	admin	Development realm administration

Studio (http://studio.localhost, or http://localhost:5605) is the single operator UI. Its Header tabs cover Designer, Task Inbox, Operations and Insight; the Administration button is gated on the abada-admin JWT group. Both accounts are development-only.

Core Compose equivalent:

docker compose -f compose.yaml -f compose.dev.yaml up -d

Bundled telemetry:

./release/abada-platform up dev --telemetry
# equivalent overlay:
docker compose -f compose.yaml -f compose.dev.yaml \
  -f compose.telemetry.yaml up -d

Operations:

./release/abada-platform status dev
./release/abada-platform logs dev
./release/abada-platform down dev

To delete local databases as well, use docker compose with the same files and run down -v. This permanently removes workflow and Keycloak data.