Historically, Spacelift was only able to handle one VCS integration per type. Not anymore! Take a look at our new approach to handle version control systems.The VCS settings have moved from the Settings page to the left sidebar under Source code menu, and the following new features have been added:<ul><li>No limitations on the number of VCS integrations. For instance, you can have 10 GitHub and 5 GitLab integrations at the same time. Note that you can create multiple integrations pointing to the same VCS as well.</li><li>Two integration types: default and Space-level. Default integrations are accessible by everyone (same as before), while Space-level integrations are controlled by <a href="https://docs.spacelift.io/concepts/spaces/access-control" target="_blank" rel="noopener nofollow">Space access controls</a>. Note: all existing integrations have been marked as default integrations.</li><li>Fine-grained access control. Have any repositories that should only be available to certain people or teams? Use Space-level integrations! When a VCS integration is tied to a Space, the <a href="https://docs.spacelift.io/concepts/stack/creating-a-stack#name-your-stack" target="_blank" rel="noopener nofollow">stack Space</a> needs to have access to the integration Space, similarly to any other Space-level entity such as Policies, Contexts, Cloud Integrations.</li><li>The VCS details (id, name, labels, description, Space, is default) have been added to the <a href="https://docs.spacelift.io/concepts/policy/push-policy/index.html#data-input" target="_blank" rel="noopener nofollow">Push policy input</a>.</li><li>You can organize your integrations with custom names, labels and descriptions.</li></ul><div><figure> <img alt="Image #1" loading="lazy" data-featurebase-content-key="6697afd8db026456df4b91e0/changelog/68cc127dab2f29e05b5a3433/01995d28-3eee-7a7e-bf3c-6d62d0061b6b/b64u-MDE5OTVkMjgtM2U5My03ZTE1LWI1NzktYWVhOWEwNTczZWNh.png" data-featurebase-content-filename="01995d28-3e93-7e15-b579-aea9a0573eca" src="https://6697afd8db026456df4b91e0.featurebase-attachments.com/c/changelog/68cc127dab2f29e05b5a3433/01995d28-3eee-7a7e-bf3c-6d62d0061b6b/b64u-MDE5OTVkMjgtM2U5My03ZTE1LWI1NzktYWVhOWEwNTczZWNh.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260916T170000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260916%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=a1deb26296cd5a9d361b3c86c2e7e7274f24a382934bc2fb7fe9681b9b005b2d"> </figure></div><a href="https://docs.spacelift.io/integrations/source-control/" target="_blank" rel="noopener">Find out more in our documentation!</a>

Enhanced VCS integrations

Help Center

Security

Improvement

Announcement

spacelift

👀 In Review

⌛ Waiting for User

⬆️ Gathering votes

🔭 Discovery

➡️ Planned

⚙️ In Progress

✅ Completed

❌ Rejected

🗑️ Archived

Access Control

Ansible

Blueprints

CloudFormation

Contexts

UI/UX

Integrations

Stacks

Workers

IaC Workflows

Spaces

Policies

Resources

Filters

Spacectl

Pulumi

Kubernetes

Dashboard

Terraform registry

Terragrunt

Stack Dependencies

Logs

Drift Detection

Spacelift Provider

Notifications

OpenTofu

Helm

OIDC

Observability

Self-hosted

Search

This is the roadmap for a Spacelift deploy.

Discovery

Planned

In Progress

Released

Spacelift Deploy Roadmap

Got an idea for a feature request? Let us know! Share your ideas on improving existing features or suggest something new. Vote on ideas you find useful!Make sure to read our <a target="" rel="noopener noreferrer nofollow" class="link" href="https://docs.spacelift.io/product/feature-requests">guidelines</a> before posting 📖

Feature Requests

Hey {name|there}! 👋