op0

op0.dev

Op0 provides a runtime that converts every code-agent commit into a single signed Proposal containing the change diff, preview URLs, policy decisions, and a named rollback target. The platform emits a signed Manifest for each deployment, enabling operators to revert to a specific version and auditors to trace the full change history. It supports IDE, CLI, and analytics-driven agents, streamlining the path from commit to shipped product.

Traction –/10

HQ unknown

Developer Tools
Artificial Intelligence
AI Agents
Software Only

Updated 9 days ago

Funding

Funding rounds are not available yet.

Founders

Founder details are not available yet.

Product

Problem

Code-writing agents produce a high volume of commits, but there is no standardized, auditable object that captures the full context of a change—its intent, diff, preview, policy compliance, and rollback path. This makes it difficult for teams to review, approve, deploy, and revert agent-generated code safely, especially as agent autonomy increases.

Solution

Op0 provides a runtime that turns every agent commit into a single signed Proposal containing the change diff, preview URLs, policy decisions, and a named rollback target. The platform emits a signed Manifest for each deployment, enabling operators to revert to a specific version and auditors to trace the full change history. It supports IDE, CLI, and analytics-driven agents, streamlining the path from commit to shipped product. The system accepts typed signals—replays, errors, annotations, support notes, or analytics anomalies—and bundles them into a Context Bundle that agents use to draft Proposals. Delivery can emit a Git PR, a signed Surface Manifest, or both, with every deploy naming its rollback target.

Target Audience

Primary users are engineering teams and platform operators running IDE agents, CLI agents, autonomous engineers, always-on repo agents, and analytics-driven agents that propose code changes from user behavior data.

Features

Signed Proposal object containing intent, file-level unified diff, deployed preview URLs per route, policy decisions (lint, types, build, replay, custom checks), and a named rollback target
Signed Surface Manifest emitted per deployment, with rollback by named manifest or git ref
Signal ingestion pipeline that queues typed signals (replay, error, annotation, support, analytics anomaly) and generates Context Bundles with replay JSON, events NDJSON, screenshots, notes, state, and OTLP traces
Policy engine that runs lint, types, build, replay, and custom checks, with approval required on the whole Proposal object
Delivery options for Git PR, signed Manifest, or both, with GitHub bot integration that comments on PRs with diff, preview, policy, and rollback details
Editable Rig file that declares signals, agent definitions, capability grants, model slots, and required artifact bundles, abstracting the underlying substrate (sandboxes, browsers, source adapters, edge delivery, MCP transports)