What is STACKIT Git?
STACKIT Git is a fully managed Git hosting service in German data centers for version control, code collaboration, and CI/CD automation. The service is based on Forgejo, an open-source community fork of Gitea, offering a European alternative independent of GitHub and GitLab. As a German cloud provider, STACKIT ensures that source code and build artifacts remain in German data centers.
Core Features
- Git repository hosting: Private repositories with pull requests, issues, and wiki based on Forgejo
- STACKIT Pipelines: CI/CD built on Forgejo Actions, roughly 90% compatible with GitHub Actions
- Managed and self-hosted runners: STACKIT-managed runners (currently Forgejo Runner v12) are provisioned automatically on pushes and events and de-provisioned after the job completes; every job runs in a fresh, isolated environment with no data persisting between runs. Predefined images cover Docker, Node.js, Python, Ubuntu, Alpine, and Java (Amazon Corretto 21); other environments can be run via custom Docker images or self-hosted custom runners
- Approvals for critical stages: Manual workflow approval in the STACKIT Portal, or a split workflow using two files
- Identity provider integration: Automated user onboarding and federation via your corporate identity provider
- IP whitelisting: ACL control restricts inbound and outbound traffic to the repositories
- Container registry integration: Direct connection to the STACKIT Container Registry for building and publishing images
- Secrets integration: Connection to the STACKIT Secrets Manager for secure credential management in pipelines
Typical Use Cases
Source code management: Companies host their source code in STACKIT Git instead of with US providers. Repositories, commits, and branches stay in Germany with granular access controls.
CI/CD pipeline automation: Teams define pipelines as code and let STACKIT Pipelines run them automatically on every commit, including build, test, and deployment.
Migrating existing GitHub Actions workflows: Thanks to the high level of compatibility, many existing GitHub Actions workflows can be transferred to STACKIT Pipelines with manageable effort.
Benefits
- GDPR-compliant: source code and build artifacts remain in German data centers
- No dependency on US hyperscalers for code hosting and CI/CD
- Open, Forgejo-based platform without proprietary lock-in
- Seamless integration with STACKIT Container Registry and Secrets Manager
Integration with innFactory
As an official STACKIT partner, innFactory supports you with STACKIT Git: migrating existing repositories, building STACKIT Pipelines workflows, container registry integration, and secrets management configuration.
Typical Use Cases
Technical Specifications
Frequently Asked Questions
Is STACKIT Git based on GitLab or GitHub?
Neither. STACKIT Git is based on Forgejo, an open-source community fork of Gitea. For CI/CD, STACKIT Pipelines are used, built on Forgejo Actions, which are roughly 90% compatible with GitHub Actions.
Can I run CI/CD pipelines?
Yes, via STACKIT Pipelines. These support both STACKIT-managed runners (currently Forgejo Runner v12, with predefined images such as stackit-docker, stackit-ubuntu-22, or stackit-coretto-21 for Java) and your own self-hosted custom runners based on the Forgejo runner, each executed in isolated environments that are deleted after the job completes.
Is there a container registry?
STACKIT Git offers direct integration with the separate STACKIT Container Registry, so images can be built and pushed to it as part of the pipeline.
Can I reuse existing GitHub Actions workflows?
Largely, yes. STACKIT Pipelines are roughly 90% compatible with GitHub Actions, so many existing workflows and community actions can be adopted with minimal changes.
Can I enforce approvals before critical deployments?
Yes. STACKIT Pipelines offer manual workflow approval: a UI-driven configuration in the STACKIT Portal pauses a workflow and requires manual validation before high-risk deployment stages. Alternatively, the same behavior can be achieved with a split workflow using two files, with fewer customization options.
Can I connect my own identity provider?
Yes. Your corporate identity provider can be connected directly to your STACKIT Git instance to automate user onboarding and federation.
How can access to the repositories be restricted?
STACKIT Git supports IP address whitelisting (ACL control), which restricts inbound and outbound traffic to the Git repositories to defined address ranges.
What does STACKIT Git cost?
Billing is monthly based on number of users and storage. STACKIT offers, among other options, an entry package for small teams with 10 users and 10 GB of storage at a reduced price; details are on the official pricing page.
Note: All product information on this page has been compiled with care, but is provided without guarantee and may be outdated or incomplete. Cloud services evolve rapidly — features, pricing, SLAs, and availability change frequently. Authoritative and up-to-date information can only be found on the official product page of STACKIT (official documentation). This page does not represent an offer by STACKIT.
