OpsDevCode

Portfolio

Independently adoptable products

Pick the job in front of you. Mint is a public developer entry, not a required first product. Delivery, infrastructure state, and economics stay distinct. Dispatch is how people ask across them — it does not replace them, and it is not yet a standalone four-product interaction surface.

Try a simulated lab

Talk to request access

OpsDevCode product comparison
DimensionMintRepaveOverpassTollDispatch
ProblemAutomation intent lives in tickets and scripts, with no governed language.Repositories drift from the approved path.Infrastructure change without durable, readable state.Cost without engineering ownership.Intent that cannot be proposed or refused with evidence.
InputA Mint project, catalogs, and declared realizations.An approved baseline, a repository, and a requested lifecycle change.Accepted Terraform or OpenTofu state the product already holds.FOCUS evidence and identified utilization samples.A request toward a domain product that already owns the work.
OutcomeCanonical MintIR and an offline governed plan — not an apply.A gated generate, adopt, update, upgrade, observe, or remediate record.Inventory, proven relationships, impact, drift, and a gated state transaction.Spend and utilization tied to engineering context — evidence, not an invoice.A proposal, a confirmation boundary, or a refusal — not a new store.
AvailabilityPublic preview / alpha. Local install. Not production-ready.Early access. Hosted generate is waitlist and invite.In development. Hosted custody is enabled per early-access partner.In development. Spend and waste execution still run in Repave.Emerging. Public identity exists; the hosted assistant still runs in Repave.
Maturity

Public preview

Early access

In development

In development

Emerging

Next stepGet startedRequest early accessExplore OverpassExplore TollExplore Dispatch

Mint

Problem
Automation intent lives in tickets and scripts, with no governed language.
Input
A Mint project, catalogs, and declared realizations.
Outcome
Canonical MintIR and an offline governed plan — not an apply.
Availability
Public preview / alpha. Local install. Not production-ready.
Maturity

Public preview

Next step
Get started

Repave

Problem
Repositories drift from the approved path.
Input
An approved baseline, a repository, and a requested lifecycle change.
Outcome
A gated generate, adopt, update, upgrade, observe, or remediate record.
Availability
Early access. Hosted generate is waitlist and invite.
Maturity

Early access

Overpass

Problem
Infrastructure change without durable, readable state.
Input
Accepted Terraform or OpenTofu state the product already holds.
Outcome
Inventory, proven relationships, impact, drift, and a gated state transaction.
Availability
In development. Hosted custody is enabled per early-access partner.
Maturity

In development

Toll

Problem
Cost without engineering ownership.
Input
FOCUS evidence and identified utilization samples.
Outcome
Spend and utilization tied to engineering context — evidence, not an invoice.
Availability
In development. Spend and waste execution still run in Repave.
Maturity

In development

Next step
Explore Toll

Dispatch

Problem
Intent that cannot be proposed or refused with evidence.
Input
A request toward a domain product that already owns the work.
Outcome
A proposal, a confirmation boundary, or a refusal — not a new store.
Availability
Emerging. Public identity exists; the hosted assistant still runs in Repave.
Maturity

Emerging

Invited-organization access

Team and Growth are invited-organization plans. There is no public price list or self-serve catalog.

  • TeamInvited-organization access for a single team adopting one or more products.
  • GrowthInvited-organization access when several teams share the same governed platform.

Talk to request access →

Open-source utilities from earlier platform work remain on GitHub. They are not the portfolio. Private product repositories are not published here. How the products fit.