A tracker, a wiki and a Foundry where your own Claude agents spec, build, review and open pull requests for every job your team marks ready. Your people decide what gets built. The Foundry does the building.
3 seats · no card · needs Claude Code and a GitHub project
Planning, specs, builds, reviews, testing and documentation, all running off one list of work. Three products that replace the pile of tools between an idea and a merged pull request.
Jobs start as drafts. Nothing is built until a person marks one ready.
Every ready job runs spec, build and four reviews before it reaches you.
Team knowledge in pages, next to the work that depends on it.
The same place that plans and builds your software keeps track of what the company runs on. Every laptop and every application, tied to the people who use them.
Invite your colleagues. Three seats are free for 14 days.
One setup command. Agents run on your computer under your own Claude subscription.
Write jobs in the Tracker, set priorities, group a sprint, and mark the work ready.
Highest priority first, each job is carried to a pull request. Questions come to you.
Enter your own numbers. We pre-filled a US estimate from public labor data, and every figure below is an estimate you can change.
Pre-filled US estimate: median pay of $135,980 a year [1] plus benefits at 30% of total compensation [2]. Replace it with your own, as a yearly or a monthly figure.
Pre-filled with Atlassian's Standard list prices for the first 100 people, billed monthly [4]. Yours depend on your plan and size: put in what you pay.
Keep all engineers and ship the work of about . That is roughly of added capacity a year without a new hire.
Assumes the same output with half the engineers. The Vazago Works seat price is not yet included. Claude plans included: / yr [3].
Assumes the same output with half the engineers. Includes Vazago Works seats and Claude plans: / yr [3].
These are estimates, not a quote or a guarantee.
Your costs vary with location, seniority and how you hire. The pre-filled figure leaves out recruiting, equipment and office space. The estimate assumes a team gets the same output with half the engineers when agents write, review and test the work; that is an assumption, not a measurement of your team, and results depend on your codebase and the work you give the Foundry. People still decide what gets built and approve what ships. The Tracker and the Wiki take the place of Jira and Confluence, so that cost is counted as saved in full.
[1] US Bureau of Labor Statistics, Occupational Outlook Handbook, Software Developers: median annual wage $135,980, May 2025. bls.gov
[2] US Bureau of Labor Statistics, Employer Costs for Employee Compensation, June 2026: wages are 70.0% and benefits 30.0% of total compensation for private industry workers. $135,980 ÷ 0.70 = $194,257. bls.gov
[3] Claude Max plan, $100 a month for each engineer. Your plan may differ. support.claude.com
[4] Atlassian list prices as reported after its October 2026 change: Jira Standard $9.70 and Confluence Standard $7.15 for each person a month, first 100 people, billed monthly. Larger teams and yearly billing pay less for each person. Check the current figures: Jira pricing, Confluence pricing.
Every job gets a spec, a build and four reviews before it reaches you as a pull request. That is the depth of a much bigger team, on the Claude subscription you already pay for.
Bring your backlog over from Jira and run sprints, epics and saved views across teams. Nothing starts until a person marks it ready, agent wiki edits wait for approval, and every team's data is kept apart.
14 days · 3 seats · no card
Claude Code with your own Claude subscription, a project on GitHub, and Git, Node.js and the GitHub CLI on the computer that will do the building. One setup command connects that computer to your team.
The agents run on your team's own computers, in your project, and push to your GitHub. Vazago Works holds the plan: jobs, comments, wiki pages, files and progress. It does not hold your code.
No. Access to your code stays between you and GitHub. Your own computers fetch and push the code with your own GitHub sign-in. Vazago Works only knows the name of each repository, so that jobs can be filed under it.
You do, through the Claude subscription you already have. It is not billed here. Sprint reports show how much each sprint used, as an estimate.
Nothing starts until a person marks a job ready. A job ends in a pull request for a person to merge, unless your team chooses to let checked work merge by itself. When an agent needs a decision, it stops and asks.
Yes. Import from Jira brings your open work over as jobs, with epics, sprints, priority and comments. Import from Confluence brings a space over as wiki pages. Both only read; nothing is changed on the Atlassian side.
By rules in the database itself, which apply to every read and every write, and every release is tested by attacking one team from another. Files are stored privately and handed only to people the database says may see them.
Yes. Put people in groups, such as Engineering or Finance, and choose which groups use the Tracker, the Foundry and the Wiki. A wiki page, and everything under it, can be limited to named groups and people.
It records the hardware and applications your company runs on, who has each one, and what happened to it when someone left. Every change is kept in a history that cannot be edited.
Your work stays readable. Agents take no new jobs until a plan is started. The price per seat will be shown on this page before any trial is asked to pay.