One price per engineer a month, whichever agent they use and however much it does — never per token, and never for the people who only read.
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.
Seats and prices set for your organization, paid by card or by bank transfer on invoice terms. Arranged with a person, and put in writing.
We quote a buyout at 6–10× the annual plan value, depending on scope and transfer support. It is arranged with a person, and the number is put in writing.
There is none. VerGen runs no agent: your engineers keep Claude Code, Cursor, Codex or Gemini on their own machines, and Tollgate reports each session. VerGen estimates the ticket before the work, records what Tollgate pushes, and judges the trail it left.
Orchestration platforms optimise how much your agents get through. VerGen estimates each ticket before the work starts and judges how it was delivered. You can run both.
No. It is read from what the work left behind: the estimate, the sessions, the pull request, its CI and review, the release. There is nothing to fill in, and an estimate made late is never shown as made first.
Anthropic's and Atlassian's AI-native SDLC playbooks, which describe the same loop: plan, design, build, test, review, deploy, maintain. VerGen reads each stage from what it left behind, and a stage it cannot read shows as unknown, never as passed.
Per person, per month. Tollgate is $1. VerGen, which adds ticket estimates and the delivery trail, is $10. There is no base fee and no limit on people, teams or projects, and invoices never carry a token figure.
It is recorded, not stopped. When the change merges, the band is set beside what every session on the ticket sent, and the trail says whether it landed within it. Every band names where it was made: in VerGen or on the machine.
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.
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.
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.
No. A failed check is flagged and a week outside its usual band is reported; a person decides what happens next. Oversight never reverts, retries or blocks a change.
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.
No. VerGen runs no agent and holds none of their credentials. It estimates before the work, records what was done, and judges each stage; a stage it could only partly see is shown as partly seen, never as passed.