Skip to content
New: see your fit and get a tailored quote in minutes.Try the estimator
Menu

The integration landscape

Keep the stack you already trust. Skip the migration.

You've already invested years in the tools your teams know. Adopting a platform shouldn't mean tearing them out and starting over. Your tools are the machines on the floor; IntegraCI is the line that connects them. Plug in what you run today and keep shipping. No rip-and-replace.

More than an API key

A connector isn't just a token in a box.

Wiring in a tool elsewhere usually means pasting a key into a settings field and hoping for the best. Here, every connector runs under the same governance: its credentials are sealed in a dedicated secrets store, every call it makes passes through your policy gates, and each action lands in a tamper-evident audit trail. The same rules hold whether it's a connector we ship or one you build.

  • Credentials are stored once, scoped to the connector, and never written to a log or a config file.
  • Calls are checked against policy as code, so a tool can only do what you allow.
  • Every action is recorded, so you can answer who did what, when, and under which approval.
connector lifecycle
  1. 01

    Install the connector

    connected

    Pick a tool from the catalogue and connect it to your tenant.

  2. 02

    Seal the credentials

    vaulted

    The key goes straight into the secrets store, scoped to this connector.

  3. 03

    Govern every call

    policy: allow

    Each request is evaluated against policy as code before it runs.

  4. 04

    Record the action

    audited

    The call and its decision are appended to the audit trail.

The landscape

Every tool you run, on one governed line.

114 connectors across 9 categories, and growing. These are the machines on your floor. IntegraCI is the line that connects, gates, and records every one of them.

Tap a category to filter, or search by name. A dot marks a connector we can also run for you as a managed add-on.

1AtAtlassian2GeGerrit3GiGitea4GHGitHub5GLGitLab6MiMicrosoft7AkAkuity8AWAmazon Web Services9BuBuildkite10CCCircleCI11CNCNCF Tekton12DCDrone CI13HaHarness14JCJenkins (CDF)15ApApple16APArgo Project (CNCF)17AWAWS18ClCloudflare19CNCNCF20CoCoder21CDCrunchy Data (pgBackRest project)22DaDaytona23EnEnv024GoGoogle25KeKeycloak26MDMongoDB, Inc.27OkOkta28OSOutSystems29PuPulumi30RSRancher (SUSE)31RHRed Hat32SoSonatype33SpSpacelift34SUSUSE (Rancher)35SySyntasso36TCTerraform Cloud37VMVMware (Velero project)38ASAqua Security39DDDefectDojo (OWASP)40ElElastic41GCGoogle Cloud42GOGreenbone (OpenVAS)43HCHashiCorp44IBIBM QRadar45ICIsovalent / Cilium46MeMend47MAMicrosoft Azure48OPOpen Policy Agent / CNCF49OBOpenBao (LF)50OWOWASP ZAP51PTPlexTrac52PDProjectDiscovery53PPProwler (ProwlerPro)54SCScanCode55SnSnyk56SSSonarSource57SpSplunk58SLSumo Logic59TeTenable60TFThe Falco Authors / CNCF61WaWazuh62BSBetter Stack63DaDatadog64GLGrafana Labs65OCOpenCost66OTOpenTelemetry67PLPixie Labs68PSPolar Signals69SeSentry70AJAppium project (JS Foundation / OpenJS)71CMChaos Mesh (CNCF)72GCGatling Corp / open-source community73GrGretel.ai74LCLitmusChaos (CNCF)75LoLocust (locust.io / open-source community)76PFPactFlow / Pact Foundation77ToTonic.ai78WiWix (open-source)79ACAlibaba Cloud80AnAnthropic81AWArgo Workflows82AAAsyncAPI Initiative (Linux Foundation)83BIBuf, Inc.84CACursor (Anysphere)85DIDatabricks Inc.86DHDataHub Project (LF AI & Data)87DSDeepSeek88EvEvidently89GHGitHub (Microsoft)90HFHugging Face91LOLiquibase (OSS)92MLMLflow93MAMoonshot AI94NeNeo4j95OlOllama96OAOpenAI97QdQdrant98SISnowflake Inc.99SoSoda100WBWeights & Biases101ZAZhipu AI102OLOpenLDAP103SCSCIM 2.0104BSBricks Software AS105FLFlagsmith Ltd106MWMeta (WhatsApp Business Cloud API)107MTMicrosoft Teams (Bot Framework)108NoNovu109PDPagerDuty110PHPostHog111SNServiceNow112SlSlack113TeTelegram114ZeZendesk

IntegraCI, the governed line

Not one more box on the board. The layer that runs under all of them.

connectgaterecord

Don't see yours?

Your in-house tool belongs here too.

The one tool that runs your shop is rarely on anyone's list. Wrap your internal or niche tool with the connector SDK and it shows up alongside everything above. No fork, no waiting on a platform team to get to it.

Declare it

Describe a simple REST integration in a short manifest. Fastest path for a tool with a clean HTTP API.

Code it

Drop into Python for custom auth, paging, or logic, reusing the building blocks the SDK already gives you.

Generate it

Point the SDK at an OpenAPI spec and it scaffolds the connector for you.

Bring your stack. Keep your tools.

Request a demo, connect what you already run, and put golden paths, policy gates, and a tamper-evident audit trail on top. Nothing gets ripped out.