Skip to main content
The fastest way to see apowerb running is the apowerb-hosting stack: Postgres, the API and the interface, wired together by a single docker compose up.

1. Clone the three repositories

They are expected to sit side by side — the compose file builds the API and the interface from source.

2. Generate secrets and start

generate-secrets.sh fills ENCRYPT_KEY and TEST_TOKEN. It never overwrites a value that is already set — see Secrets for why that matters.

3. Check it is up

Ports are configurable in .env. Postgres stays on the internal Docker network and is not published.

4. Create your first agent

Authenticate, then create an agent through the API:
Then run it — see Sessions and runs.

Not shipped yet

  • Helm chart and Kubernetes manifests. The Docker Compose path is tested end to end; the Kubernetes equivalent is not, so it is not published.
  • Published container images. The compose file builds from source. Once apowerb/* images are published, the build: blocks become image: blocks and the source repositories are no longer needed.