Plan the size of your Git Service
STACKIT Git offers a managed Git hosting solution with integrated object storage for repositories and artifacts. Choosing the right plan from the start helps you avoid unnecessary upgrades and ensures smooth collaboration for your development teams.
Plan your needs
Section titled “Plan your needs”Before selecting your STACKIT Git plan, assess your team size, repository usage and expected data growth.
Usage patterns
Section titled “Usage patterns”Analyze how your teams work with Git:
- Commit frequency and repository size influence storage and object storage consumption.
- Teams with many binary assets (e.g. media, build artifacts) consume more object storage.
- Larger teams require higher user limits and can benefit from the higher plan to prevent interruptions.
Plans overview
Section titled “Plans overview”| Plan | Disk storage | Object storage | Max users |
|---|---|---|---|
| Git10 | 1 GB | 10 GB | 10 |
| Git100 | 10 GB | 122 GB | 100 |
When the storage capacity is exceeded, both disk and object storage are automatically increased to meet demand. However, user limits and base capacities remain defined by the selected plan.
Choosing the right plan
Section titled “Choosing the right plan”Ideal for:
- Small teams or individual developers
- Lightweight repositories (source code only, minimal binary assets)
- Development or test environments
Start with Git10 if your team has up to 10 users and your repositories stay below a few hundred megabytes. It’s an economical choice for early-stage projects or proofs of concept.
Git100
Section titled “Git100”Recommended for:
- Medium to large development teams (up to 100 users)
- Projects with multiple repositories or large binary artifacts
- Continuous Integration/Continuous Deployment (CI/CD) workflows
Choose Git100 if your repositories contain compiled binaries, build outputs or large assets that significantly increase object storage usage.
Scaling and upgrades
Section titled “Scaling and upgrades”Storage is automatically scaled when needed, so you don’t need to worry about running out of space. However, if your team exceeds 10 users or if your storage growth is continuous, consider upgrading from Git10 to Git100 proactively.
Best practice
Section titled “Best practice”- Estimate growth: Plan for team and repository expansion over 12–24 months.
- Monitor usage: Regularly check repository and object storage utilization.
- Upgrade early: Avoid workflow interruptions by upgrading before reaching user or performance limits.