Skip to main content
apowerb is designed to run either as a complete stack with the web interface and PostgreSQL, or as a backend service connected to your own database and infrastructure. The deployment repository ships ready-to-use assets for the most common hosting models, from local Docker setups to managed cloud services and Kubernetes.

Docker Compose

The quickest path to bring the full stack up on a single host.

Kubernetes

Run the same stack in a cluster with declarative manifests.

Helm chart

Package and customize the deployment with a reusable chart.

Single VM / HTTPS

Expose the stack behind Traefik with TLS on a single VM.

​
Deployment options

Choose the operating model that fits your environment:
  • Docker Compose: best for local development, labs, and small production installs.
  • Kubernetes: best when you need scaling, rollouts, and cluster-based operations.
  • Helm chart: best for repeatable installs on Kubernetes and GitOps workflows.
  • Single VM / HTTPS with Traefik: useful for self-hosted environments behind a public endpoint.
  • Secrets management: keep environment variables, tokens, and credentials outside source control.

​
Managed and hosted platforms

The repository also includes references for common managed environments and platform-specific setups:

​
Repository assets

The deployment assets are concentrated in apowerb-hosting, which assembles the API, the web interface, and the database into a consistent stack. The same repository publishes deployment configurations and scripts for the supported environment types, making it easier to move from development to production without rewriting the stack.