--- title: "Version control systems, pipeline types, and feature support" description: "An overview guide to the version control systems you can integrate with CircleCI and the features available to each pipeline type and organization type." platform: "Cloud, Server" doc_version: "Server" last_updated: "2026-10-26" --- > For current CircleCI product defaults, deprecated patterns, and Cloud/Server differences, see [AGENTS.md](https://circleci.com/docs/AGENTS.md). > > For the complete documentation index and site structure, see [llms.txt](https://circleci.com/docs/llms.txt). # Version control systems, pipeline types, and feature support CircleCI supports various pipeline types which map directly to the version control system (VCS) in which your code is stored, and the method used by CircleCI to get your code. Pipeline types are indicated with badges in the CircleCI web app, and the options are as follows: * GitHub App * GitHub App Server * GitHub OAuth * GitHub OAuth (Server) * GitLab * GitLab self-managed * Bitbucket * Cursor Origin This guide provides an overview of the VCS options, organization types, and pipeline types supported by CircleCI and the features available to each. The Cursor Origin integration is in beta. Cursor Origin is available on CircleCI Cloud, for `circleci` type organizations only. ## Which version control systems are supported? [CircleCI Cloud](https://circleci.com/pricing/) pipelines can be integrated with code repositories hosted on the following VCS providers: * GitHub.com * GitHub Enterprise Cloud * GitHub Enterprise Server * GitLab * GitLab self-managed * Bitbucket Cloud * Cursor Origin [CircleCI Server](https://circleci.com/pricing/server/) supports the following: * GitHub.com * GitHub Enterprise Cloud * GitHub Enterprise Server ## Which organization types support which VCS providers? For a full guide to organization types, see the [Users, Organizations, and Integrations Guide](https://circleci.com/docs/guides/server/permissions-authentication/users-organizations-and-integrations-guide/). `circleci` type organizations can be integrated with: * GitHub.com * GitHub Enterprise Cloud * GitHub Enterprise Server * GitLab * GitLab self-managed * Cursor Origin `github` type organizations can be integrated with: * GitHub.com * GitHub Enterprise Cloud * GitHub Enterprise Server `bitbucket` type organizations can be integrated with: * Bitbucket Cloud If you are using CircleCI Server you are using a `github` type organization. ## Feature support for each pipeline type The following table shows feature support for each pipeline type. * Features that are supported for a pipeline type are indicated with **Yes**. * Features that are not supported for a pipeline type are indicated with **No**. For an overview of users, orgs, and pipeline types, see the [Users, Organizations, and Integrations Guide](https://circleci.com/docs/guides/server/permissions-authentication/users-organizations-and-integrations-guide/). The table below is not a full list of CircleCI features. Only features where the pipeline type is relevant to support are included. If a feature is not in this table, it is supported for all pipeline types. | Feature | Category | GitHub App | GitHub App Server (Preview) | GitHub OAuth | GitHub OAuth on Server | GitLab.com | GitLab self-managed | Bitbucket Cloud | Cursor Origin (beta) | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **The method used to check out your code when using the `checkout` step in your configuration file. See more in the [Configuration Reference](https://circleci.com/docs/reference/configuration-reference/#checkout).** | Code checkout | HTTPS | HTTPS | SSH | SSH | SSH | SSH | SSH | HTTPS | | **Deploy key required for code checkout. See the [Users, Organizations, and Integrations](https://circleci.com/docs/guides/server/permissions-authentication/users-organizations-and-integrations-guide/#how-circleci-checks-out-your-code) guide for more information.** | Code checkout | **No** | **No** | **Yes** | **Yes** | **No** | **No** | **Yes** | **No** | | **Fine-grained permissions when integrating with CircleCI. Select a subset of repositories to be used with CircleCI.** | Security | **Yes** | **Yes** | **No** | **No** | **No** | **No** | **No** | **Yes** | | **Custom configuration file path. If _No_ then CircleCI config is stored at `.circleci/config.yml` in the repository.** | Configuration | **Yes** | **Yes** | **No** | **No** | **Yes** | **Yes** | **No** | **Yes** | | **Use an existing GitHub Actions workflow file as the pipeline configuration, instead of a CircleCI configuration file. Read more in the Use a GitHub Actions Workflow File as Your Pipeline Configuration guide.** | Configuration | **Yes** | **No** | **No** | **No** | **No** | **No** | **No** | **No** | | **Centralized configuration management and job overrides. Read more in the How to Override Config guide.** | Configuration | **Yes** | **Yes** | **No** | **No** | **No** | **No** | **No** | **Yes** | | **View your configuration file in the CircleCI web app** | Configuration | **Yes** | **Yes** | **Yes** | **Yes** | **No** | **No** | **Yes** | **Yes** | | **Edit your configuration file in the CircleCI web app** | Configuration | **No** | **No** | **Yes** | **Yes** | **No** | **No** | **Yes** | **No** | | **[GitHub Checks](https://circleci.com/docs/guides/server/integration/status-updates/) to track the status of your pipeline in the GitHub UI** | Notifications | **Yes** | **No** | **Yes** | **Yes** | **No** | **No** | **No** | **No** | | **[Cursor Origin Checks](https://circleci.com/docs/guides/server/integration/status-updates/) to track the status of your pipeline in the Cursor Origin UI.** | Notifications | **No** | **No** | **No** | **No** | **No** | **No** | **No** | **Yes** | | **[Outbound Webhooks](https://circleci.com/docs/guides/server/integration/outbound-webhooks/). Send real-time information about your pipelines to external services. Payload varies depending on pipeline type.** | Notifications | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | | **Cross-repo pipeline and trigger setups** | Triggers | **Yes** | **Yes** | **No** | **No** | **No** | **No** | **No** | **Yes** | | **Custom Webhook Triggers. Trigger pipelines from external services.** | Triggers | **Yes** | **Yes** | **No** | **No** | **No** | **No** | **No** | **Yes** | | **Schedule Triggers. Trigger pipelines based on a schedule.** | Triggers | **Yes** | **Yes** | **Yes** | **No** | **No** | **No** | **Yes** | **Yes** | | **[Scheduled Workflows](https://circleci.com/docs/guides/server/orchestrate/workflows/#scheduling-a-workflow). Schedules defined in the `config.yml` file.** | Triggers | **No** | **No** | **Yes** | **Yes** | **No** | **No** | **Yes** | **No** | | **[API Triggers](https://circleci.com/docs/api/v2/#operation/triggerPipeline). Trigger pipelines via the API.** | Triggers | **Yes** | **Yes** | **Yes** | **Yes** | **No** | **No** | **Yes** | **Yes** | | **[UI Triggers](https://circleci.com/docs/guides/server/orchestrate/triggers-overview/#run-a-pipeline-from-the-circleci-web-app). Trigger pipelines via the CircleCI web app.** | Triggers | **Yes** | **Yes** | **Yes** | **Yes** | **No** | **No** | **Yes** | **Yes** | | **Pull request event triggers. See more in the [Triggers Overview](https://circleci.com/docs/guides/server/orchestrate/triggers-overview/#run-a-pipeline-on-commit-to-your-code-repository).** | Triggers | **Yes** | **Yes** | **No** | **No** | **Yes** | **Yes** | **No** | **Yes** | | **Only build on push to pull/merge requests. See more in the [Pull Request Build Settings](https://circleci.com/docs/guides/server/integration/pull-request-build-settings/#only-build-pull-requests) guide.** | Triggers | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | **Yes** | | Rerun Failed Tests. | Testing | **Yes** | **Yes** | **Yes** | **No** | **Yes** | **Yes** | **Yes** | **Yes** | | **Use [Deploy Markers](https://circleci.com/changelog/release-markers-and-release-jobs/) to track deployments in the CircleCI web app** | Deployment | **Yes** | **Yes** | **Yes** | **No** | **Yes** | **Yes** | **Yes** | **Yes** | | **Set up Rollback Pipelines to manually revert your application to a previous stable version directly from the CircleCI web app** | Deployment | **Yes** | **Yes** | **Yes** | **No** | **No** | **No** | **No** | **No** | | **Set up Deploy Pipelines to automatically deploy your application to a target environment directly from the CircleCI web app** | Deployment | **Yes** | **Yes** | **Yes** | **No** | **No** | **No** | **No** | **No** | | [Build Pull Requests From Forked Repositories](https://circleci.com/docs/guides/server/integration/pull-request-build-settings/#build-pull-requests-from-forked-repositories) | Open source support | **No** | **No** | **Yes** | **Yes** | **Yes** | **No** | **Yes** | **No** | | [Pass Secrets to Builds From Forked Pull Requests](https://circleci.com/docs/guides/server/integration/pull-request-build-settings/#pass-secrets-to-builds-from-forked-pull-requests) | Open source support | **No** | **No** | **Yes** | **Yes** | **Yes** | **No** | **Yes** | **No** | | **Chunk, CircleCI’s AI CI/CD agent. Learn more in the Chunk Setup Guide** | Agentic support | **Yes** | **No** | **Yes** with GitHub App installed | **No** | **No** | **No** | **No** | **No** | ## Feature support for each organization type The following table shows feature support for each organization type. This list does not include all CircleCI features. Only features where the organization type is relevant are included. For a guide to organization types, see the [Users, Organizations, and Integrations Guide](https://circleci.com/docs/guides/server/permissions-authentication/users-organizations-and-integrations-guide/). Cursor Origin organizations are `circleci` type organizations, so the **CircleCI** column applies to them. | Feature | GitHub | Bitbucket | CircleCI | | --- | --- | --- | --- | | **Test Insights. View insights into your test performance.** | **Yes** | **Yes** | **No** | | **[Security Group Context Restriction](https://circleci.com/docs/guides/server/security/contexts/#security-group-restrictions). Restrict the use of contexts to specific users and groups.** | **Yes** | **No** | **No** | | **User management and permissions system within CircleCI including: Roles, Groups, SSO, MFA. See the Roles and Permissions Overview for more information.** | **No** | **No** | **Yes** | | **Project creation process.** | Imported from VCS | Imported from VCS | Manual | | **Multiple projects to track a single monorepo.** | **No** | **No** | **Yes** | | Set Up Multiple Pipelines and Configuration Files for a Project | **Yes** | **No** | **Yes** |