Reference
Find API documentation, CLI commands and Git documentation.
Find API documentation, CLI commands and Git documentation.
On October 27, 2026, from 20:00 to 23:00 (UTC), SSH access to STACKIT Git moves to one shared address. The name of your instance becomes the first element of the repository path. This reduces the publicly exposed surface of your instance and lets us improve the reliability of Git operations over SSH in one place.
git@ssh.<instance>.git.onstackit.cloud:<owner>/<repository>.gitssh://git@ssh.git.onstackit.cloud/<instance>/<owner>/<repository>.gitDuring the maintenance every Git instance is restarted once and is unavailable for about one minute. The restarts are staggered, so not all instances are affected at the same time. Access over HTTPS, your repositories, your users, your registered SSH keys and your IP allowlists do not change.
The previous address keeps working until April 27, 2027. Your existing clones and your automation continue to work after the maintenance, so you can move them at your own pace. We remind you before we switch the previous address off.
213.17.16.145 on port 22, if your network restricts outbound connections.ssh.git.onstackit.cloud, if your systems verify host keys. Its fingerprint is SHA256:I4jgl6ALgx5qOWwpQVC2M613dV7R0Wy6LfQQ5LQKwR4 (ED25519).ssh.git.onstackit.cloud is registered in your instance.Update the remote address of each repository:
git remote set-url origin "$(git remote get-url origin | sed -E 's#^(ssh://)?git@ssh\.([^.]+)\.git\.onstackit\.cloud[:/]#ssh://git@ssh.git.onstackit.cloud/\2/#')"If you have any questions, our Help Center is always at your disposal.
We are pleased to announce a major update to STACKIT Git & Pipelines, introducing enhanced security controls, pipeline governance, and advanced identity management features directly from the STACKIT Portal.
To ensure higher resilience and meet enterprise change management standards, we have introduced Pipeline Approvers. Empower your team to ensure the highest quality standards by enabling designated members to review and authorize critical deployment pipelines before execution. There are two ways to implement this functionality depending on your setup:
We have significantly improved user life cycle management and access security:
You no longer need to manage advanced configuration with API or backend support requests. The STACKIT Portal now offers full self-service capabilities for:
We are excited to announce the integration of STACKIT-managed Runners into STACKIT Git, significantly enhancing your Continuous Integration and Continuous Delivery (CI/CD) workflows. This new feature automates and validates your code changes, new features, and critical bug fixes without manual intervention, all within your STACKIT environment.
Key Highlights:
This release marks a significant step towards centralizing your entire SDLC within the STACKIT ecosystem.