Portainer Templates

A self-hosted Azure Pipelines agent (Azure DevOps), built from Microsoft's official Dockerfile recipe - the agent ships no container image, this is the documented path.

A Buildkite agent: Buildkite hosts the UI and orchestration, your agents run the jobs - the hybrid-CI model where compute was always meant to be yours. This is the cleanest runner in the catalogue: official image, one token, done.

Your own private container registry - the CNCF Distribution registry (the same engine behind Docker Hub) - with https, basic-auth, and image storage on a Miget Bucket so the service itself holds no state. Listens natively on port 5000.

Forgejo - the community-governed git forge (the hard fork of Gitea, run by the non-profit Codeberg e.V.): repositories, issues, pull requests, packages, and CI via Forgejo Actions. One light Go binary + a managed Postgres.

A Forgejo Actions runner in host mode - CI for your self-hosted Forgejo or for Codeberg, with jobs running as shell steps in this container (no Docker daemon needed). GitHub-Actions-compatible workflow syntax.

A self-hosted GitHub Actions runner: your workflows, your hardware, zero per-minute billing. Uses myoung34/github-runner (the de-facto env-driven runner image) with PAT-based auto-registration.

A self-hosted GitLab Runner in shell mode: jobs run inside this container, your own compute, no CI-minute quota. Registers itself on first boot and persists registration on a volume.

Unleash - the open-source feature flag and toggle platform: gradual rollouts, user/segment targeting, A/B testing, kill switches, and SDKs for every language. Single stateless container on a managed Postgres (no Redis).