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

Introduction

What IntegraCI is, and the ideas the rest of these docs build on.

IntegraCI is an AI-native internal developer platform. It gives your teams one place to build, ship, secure, and operate software, and it does that by governing the tools you already run rather than replacing them. You keep your source control, your CI engine, your scanners, and your clouds. IntegraCI connects to them, puts golden paths and policy on top, and records what happened.

The platform is organized around six pillars that cover the software lifecycle end to end:

  • Secure: governed AI, database-enforced tenant isolation, and policy gates that run before risky actions.
  • Deliver: golden paths, pipelines, and deploys that work the same way across targets.
  • Operate: delivery, reliability, and cost signals, sitting next to the controls to act on them.
  • Govern: policy as code, evidence collection, and a tamper-evident audit trail.

The through-line is governance

Most platforms help you move faster. IntegraCI helps you move faster and stay inside the lines, because the guardrails are built in rather than bolted on. A connector’s credentials go into a dedicated secrets store, every AI action that changes something pauses for a human to approve, and one tenant can never read another’s data because the database itself enforces the boundary.

That means the same work that ships your software also produces the evidence an auditor asks for. You do not assemble it after the fact.

What you connect, and what stays yours

IntegraCI orchestrates and gates the tools in your stack. It does not run your scanners for you or become your CI engine. When a pipeline runs, your build runners do the building and your scanners do the scanning; IntegraCI sequences the steps, enforces the policy gates, and rolls the results into one view.

Your credentials, your code, and your data stay yours. On a self-hosted install, all of it runs in your own infrastructure, up to a fully air-gapped deployment.

How these docs are organized

  • Getting started walks you from a fresh tenant to your first governed workflow, and explains the core concepts the rest of the docs assume.
  • Basic usage covers the everyday tasks: connecting a tool, scaffolding a service, deploying it, passing the security gates, and using the AI gateway.

If you have not created a tenant yet, start with the Quickstart. If you want the vocabulary first, read Core concepts.