Two editions, named by who reads them

The editions are named by audience, never by a domain. Pick by whether anyone outside your team needs to read the work.

onMain

your process stays on main

Pricing announced at launch

The word alone is the team edition: what a developer finds, installs and names. One product, its pinned Standard, its backlog, its plans and records, and the MCP your coding agent writes them through.

  • A product, its backlog and its cards
  • A pinned Standard, with your own extension-point fills
  • Plans, decisions and requirements as records, not documents
  • The MCP, and the feature-plan process

onMain Agency

your clients see what's on main

Pricing announced at launch

The same loop plus a second population: the clients who see it. Everything in onMain, and the surfaces a client reads it through.

  • Everything in onMain
  • Clients, contracts, milestones and invoices
  • Change requests and correspondence
  • The client portal, on your own verified domain
  • Your own staff host, if you want one

Promotion happens in place

A team firm becomes an agency firm by one owner-only, audited act. Nothing moves: the same product, the same backlog, the same records, with the client surfaces switched on. There is no migration and no second account.