onMain Agency
Your clients see what’s on main.
You deliver client software with AI agents. onMain gives those agents a process they actually follow, and gives your client a portal built from that same work. Nobody writes a status report from memory again.
A 14-day free trial, and no card.
Refunds now go through the provider’s API. Wallets start next week, on plan for M3.
Drafted from the records · published by your team
Whichever seat you’re in
One job: deliver the work, and let the client see it.
Your agents build. Your client pays and waits. Today someone sits between them translating the work into a report. onMain removes that seat.
Built from the work
A portal built from the work, not written for it.
Most client portals show whatever someone typed into them. onMain’s shows the records your agents already work from, through a boundary the database enforces.
Where the money went
From the contract to the line of code.
A contract has milestones. A milestone is delivered by cards. Each card is built from a plan and lands on main. Showing a client where the money went means reading that chain, not writing a report about it.
A change request amends the contract, and the client sees exactly what moved.
An invoice follows an accepted milestone, so every line points at delivered work.
AI-native
Built for agents, not bolted onto a ticket tracker.
Most tools add an MCP server to a workflow designed for human ceremony: sprints, story points, status fields. The agent inherits all of that complexity and guesses at the rest. onMain was built for the agent from the start. It reads the plan, the loop tells it the next step, and what it writes is what your client reads.
- Tickets and statuses designed for a stand-up
- An MCP adapter that exposes the old complexity
- The agent guesses at the process
- Someone still writes the client update
- Records the agent reads and writes natively
- Three loops guide each step, from idea to main
- Every plan is reviewed before anything is built
- The client’s view comes straight from the work
› claim_next_card card 212 claimed · in progress › read_plan card=212 Plan 31 · executing · phase 2 of 3 › record_pull_request recorded · lands on main when green › add_status_report draft saved · you publish, the client reads
- 1An idea becomes a cardYour client files it in the portal, or you do.
- 2The card takes a planPlanned, reviewed and approved before anything is built.
- 3Agents build it, tests firstThe Engineering Loop keeps every step on the record.
- 4The client sees it deliveredOn the roadmap you share, with nothing to rewrite.
Your clients, in your brand.
Your clients will sign in at yourname.onmain.dev from sign-up, or a domain you verify — under your own name, colours and email sender.
- yourname.onmain.devYour firm’s own address, in your brand, from sign-up.
- Or your own domainBring one you’ve verified — at no extra charge.
- Your name, logo and paletteRead from your firm’s settings.
- Your clients’ own sign-inIsolated from every other firm.
Pricing
One plan for the agency.
Up to 20 people, every client you serve, and the same engine your developers would run.
Building your own product? It’s the same onMain.
The team edition runs your own product on the same MCP, loops and records, without the client portal.