In-portal assistance
The copilot works inside the portal and helps across the software lifecycle.
AI
AI Copilot
A governed copilot that drafts, you approve
A governed AI copilot lives in the portal and helps you across the SDLC, from understanding a service to drafting a change. Every action it takes runs through the gateway's policy and human-approval path, so nothing state-changing happens without a person signing off. Its output is a draft for you to review, not an autonomous actor working on its own.
- AI assistance that stays inside your policy and audit boundary
- Every state-changing action reviewed and approved by a person before it is applied
- A complete record of what the copilot proposed and who decided
The problem
When you want AI help inside your development workflow, you face a choice between tools that act on their own or tools locked down to read-only suggestions. Neither works for a team that needs to move quickly and stay auditable. You need a copilot that can draft and propose, while a person stays in the decision seat for anything that changes state.
Without IntegraCI
- AI suggestions with no policy gate or audit trail
- Context-switching to a tool that lives outside your portal
- Shared, long-lived credentials when AI touches your systems
- No defined boundary between what AI can propose and what it can apply
With IntegraCI
- Every proposed action evaluated against policy as code before reaching you
- Drafts reviewed in the same portal where your services and pipelines live
- Scoped, short-lived credentials issued per connector call by the gateway
- A person approves anything state-changing before it is applied
What you get
Governed by the gateway
Every action runs through the gateway's policy and human-approval path.
Drafts, not autonomy
Output is a draft you review rather than a change applied on its own.
Scoped tool access
When it uses a connector it gets the same scoped, short-lived credentials the gateway issues.
How it works
- 1
Ask in context
You pose a request from the portal where your services and pipelines live.
- 2
Policy and approval
Its proposed action passes through the gateway's policy and approval gate.
- 3
Review the draft
You receive a draft to inspect and decide whether to apply.
How it stays governed
The same gates everyone passes, applied here.
Gated by policy
The gateway evaluates every action the copilot proposes against policy as code before it can proceed. The same rules that govern your pipelines and access grants apply here, so the copilot cannot route around a control that is already in place.
Recorded, tamper-evident
Each proposal, approval, and outcome writes once to a tamper-evident audit trail. You can show what the copilot suggested, who reviewed it, and what was decided, not just that an action occurred.
A human in the loop
Any action that would change state pauses for a person to review the draft and decide. The copilot does not apply changes on its own. You receive a draft, inspect it, and choose whether to proceed.
Works with your stack
Connect the tools you already run.
The copilot calls connectors through the gateway using the same scoped credentials issued to any governed principal, so it sees only what policy allows.
- Atlassian
- Gerrit
- Gitea
- GitHub
- GitLab
- Microsoft
- Akuity
- Amazon Web Services
- Buildkite
- CircleCI
- CNCF Tekton
- Drone CI
- Harness
- Jenkins
- Alibaba Cloud
- Anthropic
- Argo Workflows
- AsyncAPI Initiative
- +20 more
Who it’s for
Where teams reach for it.
Drafting a change in an unfamiliar service
A developer needs to make a change in a codebase they do not own. They ask the copilot in context from the portal, receive a draft, and review it before deciding to open a pull request.
Getting service context before an incident response
An on-call engineer asks the copilot to summarize a service's upstream dependencies and recent pipeline state. The copilot returns a draft drawn only from what the gateway is scoped to read, and the engineer decides how to act on it.
AI assistance for regulated teams with audit requirements
A team in a regulated environment wants AI-generated drafts but cannot use a tool that acts without oversight. The copilot keeps a person in the decision seat for every state-changing action and records each proposal and outcome in the audit trail.
Questions, answered.
Will the copilot apply changes without my review?
No. The copilot produces a draft for you to inspect. Anything that would change state requires a person to review and approve before it is applied. The copilot does not act on its own.
Which tools and systems can the copilot reach?
It can reach the connectors your organization has already wired into IntegraCI. It uses the same gateway-issued, scoped credentials that any governed principal receives, so it is bound by the same policies and cannot exceed them.
How are the copilot's permissions defined?
Permissions are governed by policy as code in the gateway. The same rules that apply to your pipelines and access grants apply to the copilot, so you define what it is allowed to propose and what requires a human approval step.
Does IntegraCI replace the AI coding assistant my team already uses?
No. The copilot is an in-portal assistant that helps you interact with IntegraCI's connected SDLC context. It is not a replacement for standalone editors or coding tools. It adds a governed, auditable layer for the work that flows through IntegraCI.
Put AI Copilot on your stack.
Request a demo, or read the docs to see how it fits the tools you already run.