Pricing

Priced by person. Never by token.

One price a month for each person, whichever AI tools they use. The VerGen Agent is included for everyone.

INVOICE · ONE MONTHExample
People on the plan
12
  • GenSaS plan, first person$10
  • 11 more licenses$110
  • Tokens, runs, projects, teamsNot billed

Total a month$120

12 × $10, at the published price. No line is ever in tokens.

What you pay for.

Billed monthly

GenSaS

$10per person a month

Every ticket estimated in tokens before the work starts, and every stage of delivery judged from what it left behind — with tollgate for the whole team.

  • One price per engineer
  • Everything in Tollgate
  • Tickets estimated before work starts
  • The delivery trail on every ticket
  • Any number of teams and projects
Start on GenSaS
Questions

What people ask first.

Who is VerGen for?

Everyone who works with AI, not only engineers: they get a cost estimate and a plan for each task before the work starts. And the managers who answer for the spend, who read each project's retrospective: what the work cost, what was saved and what to change next.

How is a saving measured?

Against the same project's tasks of the same size that ran with no estimate: saved is what estimated tasks cost below them. Lost is what un-estimated tasks cost beyond what VerGen estimates for their size. Both are priced at the vendor's list price from recorded sessions, and too few tasks to compare shows as not comparable, never a guess.

Do I have to use your coding agent?

There is none. VerGen runs no coding agent of its own: your people keep Claude Code, Cursor, Codex or Gemini on their own machines, and the VerGen Agent beside them reports each session. VerGen estimates the ticket before the work and records what the VerGen Agent pushes.

How is it priced?

One plan, $50 per person a month, with the VerGen Agent included for everyone. There is no base fee and no limit on people, teams or projects, and invoices never carry a token figure.

Which tools does it work with?

Jira, Linear, Asana, ClickUp, Trello, GitHub Issues, Azure DevOps and monday.com for tickets; Zendesk, Intercom, Freshdesk and HubSpot for helpdesks; GitHub, GitLab, Bitbucket and Azure Repos for code; Slack and Teams for notifications.

Does it see what people do on their own machines?

Only on machines enrolled in the workbench. Each session's turns, tokens and setup are recorded and scored against your team's briefs; the text is kept for 90 days, the scores for good. Local work is never billed.

5 more questions
How is this different from an agent orchestration platform?

Orchestration platforms optimise how much your agents get through. VerGen estimates each ticket before the work starts and records what it cost. You can run both.

What happens if the work needs more than its estimate?

It is recorded, not stopped. When the change merges, the estimate is set beside what every session on the ticket sent, and the ticket shows whether it landed within it. Every band names where it was made: in VerGen or on the machine.

Who can estimate a ticket?

Anyone in the project allowed to request an estimate, while the ticket is still a draft. Once a session or a pull request names the ticket, its estimate is fixed; estimating again before then supersedes the last one.

What code does VerGen read?

To estimate a ticket it reads only the files it selects from the repositories the ticket changes, to size them; no model is called. The estimate lists exactly which files it counted.

Does VerGen stop or approve an agent's work?

No. VerGen runs no coding agent and holds none of their credentials. It estimates before the work and records what was done.

Know what AI work will cost, and what it saved.