Compute basis
Three L workloads: forge, CI server and identity; isolated runner; registry and password manager. Builds, image sizes and retention determine sizing.
Git, CI and container registry with Forgejo
Code, builds and container images on one platform: Forgejo for Git, Woodpecker CI for pipelines, Harbor for images and Vaultwarden for team credentials, sign-in through your identity service.
- Forgejo, Woodpecker CI, Harbor
- Vaultwarden and SSO included
- Isolated CI runner
Starting point
What development teams use the platform for
Anyone who does not want to leave Git with a US service needs more than a Git server: builds, image storage and credentials have to come with it.
One delivery chain
Code, build and image sit together, the same accounts apply everywhere.
Run builds separately
Build code runs on its own runner, separate from CI server, forge and their credentials.
Credentials in one place
The team's passwords and credentials sit in the password manager instead of chats and files.
How it fits together
Git, CI, registry and passwords working together
Forgejo
Git hosting with pull requests, issues and packages; sign-in through OIDC.
Woodpecker CI
CI server with sign-in through the forge; no identity service of its own.
Harbor
Container registry with projects, roles and OIDC sign-in.
Vaultwarden
Password manager for team credentials; sign-in through OIDC.
Keycloak or Authentik
Included in the package price. Protocols and roles are defined per application.
Extensions and scope limits
Vaultwarden manages credentials for people and teams. Dynamic secrets for pipelines and builds per hour are not part of the package.
Operations
How your Git platform is operated
Core apps, monitoring and updates within the agreed scope.
Restore order
Planned restore order: identity, forge with Git and LFS, registry with metadata, CI database and credentials; the runner is rebuilt reproducibly.
Checks before release
Check version compatibility of forge, CI server, registry and runner; verify tokens and webhooks after the update.
Offer
What does the Git platform with CI and registry cost?
The price includes Forgejo, Woodpecker CI, Harbor and Vaultwarden on 3 L workloads. Keycloak or Authentik comes with the package at no extra charge. The isolated CI runner is a workload of its own and is priced like a further app.
Calculation
- 3 workloads, one app each included
- €389.70 net per month
- Compute L, 3 workloads
- €269.70 net per month
- 2 additional apps, including the isolated CI runner
- €199.80 net per month
- Keycloak or Authentik
- included in the package
- Service level: Essential
- included in price
- Total with Business
- €1,018.90 net per month
- Total with Priority
- €1,138.90 net per month
Straightforward provisioning within a few business days
- Bank transfer
One-time setup based on scope, specified in the proposal. Additional storage is booked in 50 GB steps: €4.99 net per month. Assess Priority for productive build and release paths. The service level remains selectable; the published ladder applies.
Selection
Sign-in for Git, CI and registry: Keycloak or Authentik
Keycloak or Authentik is included in the package price. You choose the identity service that fits your organisation.
| Choice | Scope | Configurator entry |
|---|---|---|
| Keycloak | OIDC/SAML, brokering and LDAP/AD federation. Realm and client configuration are operating tasks. | Configure package: Keycloak |
| Authentik | OIDC/SAML, sources, flows and LDAP/proxy providers. Account for outposts per integration. | Configure package: Authentik |
Selection
Which size fits your builds?
Single-app hosting operates one application. The package adds further apps and shared identity planning; integrations are scoped in the proposal.
| Compute | Resources from registry | Essential, net per month |
|---|---|---|
| S | 2 vCPU · 4 GB RAM · 80 GB NVMe SSD | €679.40 net per month |
| M | 4 vCPU · 8 GB RAM · 80 GB NVMe SSD | €739.20 net per month |
| L | 8 vCPU · 16 GB RAM · 80 GB NVMe SSD | €859.20 net per month |
- L is the starting size. WZ-IT checks which size your use needs before the proposal, based on builds, image sizes and retention. Users are not limited; XL can be selected in the configurator.
Licences and editions
Licences and editions: Forgejo, Woodpecker, Harbor, Vaultwarden
As of 25 October 2026. Free cores form the pricing basis. Commercial editions and vendor services are separate.
| Licence | Function and boundary |
|---|---|
| Forgejo (GPL-3.0-or-later) | OIDC/OAuth2 and LDAP belong to the core; SAML is not available. The vendor lists no paid edition. Licence file · Feature documentation |
| Woodpecker CI (Apache-2.0) | Users and sign-in come from the forge through OAuth2. Single sign-on comes from the forge's identity service. Licence file · Feature documentation |
| Harbor (Apache-2.0) | Database, LDAP/AD and OIDC sign-in belong to the core; SAML is not available. The sign-in mode is chosen before local users are created. Licence file · Feature documentation |
| Vaultwarden (AGPL-3.0) | OIDC sign-in from version 1.35.0 with documented Keycloak and Authentik; the master password stays mandatory. SAML and native LDAP are missing. Unofficial server, not affiliated with Bitwarden. Licence file · Feature documentation · Edition boundary |
| Keycloak (Apache-2.0) | OIDC, SAML and identity brokering in the free core. Licence file · Feature documentation |
| Authentik (MIT) | MIT core with OIDC, SAML, LDAP and proxy providers. Enterprise features have a separate licence and are not included. Licence file · Feature documentation · Edition boundary |
Questions about the Git platform with CI and registry
Answers to the most important questions
- Workload, compute, additional apps, storage and service level are summed from the registry. Keycloak or Authentik is included in the package price. One-time setup is based on scope and defined in the proposal; commercial licences are separate.
- Yes. The two entry links select exactly one identity service in the configurator. An existing customer identity provider can be connected after technical review. Sign-in, roles, blocking and emergency access are reviewed together before approval.
- The design uses a runner on its own instance. Build code runs there, separate from CI server, forge and credentials. Tokens and permissions per project are defined in the proposal.
- No. Vaultwarden stores credentials for people and teams. Dynamic secrets for pipelines are a separate requirement and are scoped in the proposal.
- Backup scope and retention are specified in the proposal using the registry components and your requirements. The recovery order shown describes the planning for this package.
- Original files, databases, configuration and customer-owned exportable keys are recorded in the exit scope. Export formats and handover are specified per app. See the data portability framework.
- Operations in data centres in Germany, Switzerland or Austria. A confidentiality agreement under Section 203 German Criminal Code (StGB) is available on request at the German location. A subdomain under wz-it.cloud and one .de domain are included; your own domain can be connected by CNAME. Monthly cancellation with 30 days notice to month-end, no minimum term. WZ-IT sets no user limit; size depends on Compute S to XL and edition limits.
Knowledge
Git, CI and registry in detail
Reviews & projects
Managed open source with consulting and operations
Customer feedback on open-source selection, implementation, maintenance and long-term operations.
Networking & Provisioning
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT

Read client reviews
Git, CI and registry
Configure Git, CI and registry and request an offer
Choose the identity service and add requirements in the configurator. WZ-IT specifies setup, sizing and operating scope in the proposal.
- Straight with Timo and Robin - no sales team, no pitch
- A professional assessment of your situation
- Concrete next steps for infrastructure, software or AI
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.


















