Connect a tool

IntegraCI works with the stack you already have. You connect your source control, CI, scanners, clouds, and more, and the platform governs how those tools are used. Nothing gets ripped out.

Install a connector

Open Connectors in the portal and pick a tool from the catalogue. Provide the credential it needs, such as an API token or an app installation. That credential goes straight into a dedicated secrets store, scoped to this connector. It is never written to a log or a config file, and it is not visible to other tenants.

Once connected, the tool shows up where your teams already work: a source-control connector feeds the catalog, a scanner becomes a step your pipelines can gate on, a cloud becomes a deploy target.

How a connector stays governed

A connector is more than a stored key. Three things hold for every connector, whether we ship it or you build it:

• Sealed credentials. Stored once, scoped to the connector, never logged.
• Governed calls. Each call is checked against policy as code before it runs, so a tool can only do what you allow.
• A recorded trail. Every action is written to the audit trail, so you can answer who did what, when, and under which approval.

Connect your own tool

If the one tool that runs your shop is not in the catalogue, wrap it with the connector SDK and it shows up alongside everything else. You have three paths, from least to most effort:

• Declare it. Describe a simple REST integration in a short manifest. The fastest path for a tool with a clean HTTP API.
• Generate it. Point the SDK at an OpenAPI spec and it scaffolds the connector for you.
• Code it. Drop into Python for custom auth, paging, or logic, reusing the building blocks the SDK provides.

Next

See where your services live and how you read their health: Catalog and scorecards.