OPI Forge

The problem this solves

Autonomous software delivery at scale needs more than a coding agent. It needs a governed lifecycle: specifications, reviews, commits, follow-ups, and deployment readiness, all operating inside review gates the organization controls.

Today, adopting agentic delivery means accepting either brittle one-shot outputs or uncontrolled multi-agent work. Neither survives contact with a regulated engineering org.

What changes when you adopt OPI Forge

• Specification-first workflow

  Stories and specs drive the work. Agents operate on structured inputs, not free-form chat.

• Mandatory review gates

  Mandatory checkpoints — review, QA, operational readiness — between every phase. None of them skippable.

• Auditable delivery

  Every step recorded. Reconstruct any change from specification to commit to deployment.

• Self-hosted delivery

  TUI and headless options run in customer-owned or customer-controlled infrastructure. Each option respects the same review gates.

How OPI Forge operates

1. 01

   Define the specification

   Stories, acceptance criteria, and constraints. The spec is the input; the agent operates on it.

2. 02

   Multi-agent orchestration with review gates

   Subagents work in parallel worktrees. Review gates validate between phases.

3. 03

   Carry changes through GitOps

   Approved changes flow through development environments, soak periods, and production promotion with human approval.

Component map

• Specification storeVersioned stories, acceptance criteria, and constraints.
• Agent harnessToken-efficient harness with token and cost controls.
• Review gatesMandatory checkpoints — review, QA, ops readiness.
• GitOps carrierCarries changes through environments with rollback protection.

For the full platform architecture, see /platform.

Who uses it and how

• Engineering leadership

  Scenario: You want to scale engineering output without sacrificing review and operational discipline.

  Gain: A governed agentic SDLC with mandatory review gates and an audit trail.

• Platform engineering

  Scenario: You want to embed agentic delivery into CI and internal tooling.

  Gain: A headless deployment option with the same review gates as the self-hosted TUI surface.

See the product surface

Supported systems

OPI Forge integrates with the providers and frameworks below. Each entry shows the current support status. Documentation for the full integration list is coming soon.

• GatewayGenerally available
• GitGenerally available
• BastionTech Preview

Where it runs and how data is handled

Chrysent sells self-hosted software only. Software and retained product data remain in customer-owned or customer-controlled infrastructure. Customer-configured external model providers receive provider-bound request data under the customer's provider agreement. This model supports data sovereignty and residency requirements. Data handling and retention are described on the Data handling & deployment page. Security architecture, encryption, and incident response are documented on Security & trust.

Benchmark and evaluation methodology

The first public benchmark study is in preparation. Until it ships, design partners can request the evaluation methodology and a private run report under NDA via the contact form.

Other Chrysent products

• Chrysent AI Gateway

  Private beta

  Chrysent AI Gateway provides centralized control over AI usage across multiple vendors and models.

• Chrysent Bastion

  Private beta

  Chrysent Bastion protects enterprise systems from unsafe AI generated actions.

• Chrysent Axis Code

  Private beta

  Chrysent Axis Code is a code graph platform designed for AI assisted software development.

Common questions

• How is OPI Forge available?

  OPI Forge is available in private beta as self-hosted software for customer-owned or customer-controlled infrastructure.

• Are review gates mandatory?

  Yes. None of the gates are skippable — that is the point of having a governed lifecycle.