No dates promised
Items move between Now, Next, and Later as we learn. Nothing here is a release date you can hold us to.
Public roadmap
Where IntegraCI is headed.
Six pillars guide the work: Deliver (golden paths, pipelines, and releases), Quality (scorecards, tests, and quality gates), Secure (scanning, supply chain, and access), Operate (reliability, observability, and cost), Govern (policy, evidence, and audit), and AI (a governed gateway, copilot, and agents). Below is what is in your hands today, what we are building next, and the directions we are thinking about further out. It is a sense of direction, not a delivery commitment. Priorities shift as we learn from teams building on IntegraCI.
Shipping now
In your hands today-
Governed AI gateway with HITL approvals
Route model calls through one gateway, gate the risky ones on a human approval, and keep a record of what the agent did. Built into the platform, not bolted on.
-
Database-enforced tenant isolation
Database-enforced row-level security keeps tenants apart in the database itself, closed by default. The boundary holds even when a query forgets to filter.
-
Golden paths and scaffolding
Paved templates that create a service wired to your CI, scanners, and deploy targets, so a new repo starts inside the guardrails instead of outside them.
-
Exportable audit trail
A tamper-evident, write-once trail of platform actions you can export when the review comes, with compliance policy bundles mapped to SOC 2, ISO 27001, and GDPR.
Working on next
In active development-
Deeper connector coverage
Broadening the set of CI systems, scanners, and clouds you can connect, with richer two-way sync so findings and deploy events flow back into the platform.
-
Policy authoring without the YAML wall
A clearer way to write and test policy gates, so the rule you mean is the rule that runs, and you can see what a change would block before it ships.
-
Wider self-healing and AIOps actions
More remediations an agent can propose and (with your approval) carry out, each one scoped, reversible where possible, and recorded in the audit trail.
-
Operate insights you can act on
Tighter delivery, reliability, and cost views inside the portal, so the signal that something needs attention sits next to the control to do something about it.
Thinking about later
Directional, not committed-
Formal attestations
Today we ship policy bundles mapped to common frameworks, not a certification. Formal attestations are a direction we are exploring, not a dated promise.
-
Federated and multi-cluster reach
Governing fleets that span regions and clusters from one control plane, with the same isolation and approval guarantees holding across the boundary.
-
Marketplace for shared paths and policy
A place to publish and adopt golden paths, policy bundles, and connectors built by other teams, so good defaults travel instead of getting rebuilt.
How to read this
Directional, not a contract.
We publish the roadmap so you can plan around the same picture we work from. That means being honest about its limits.
Order can change
Feedback from teams using IntegraCI reshapes priority. Something in Later can jump ahead, and the reverse happens too.
Your input counts
The fastest way to shape what ships next is to tell us what you need. We read every request.
Have something you need on this list?
Request a demo and tell us what would make IntegraCI fit your team. Self-host (up to air-gapped) or managed, the choice is yours. Your request goes straight to the people building it.