Pricing built around Mapped Issues
You only pay when we deliver a Mapped Issue: a structured bug report, or a code-actionable feature request, with the file and function identified in your codebase. PR drafts, customer RCA, and tracker sync to Jira, Linear, GitHub Issues and Azure Boards are bundled, never billed.
14-day free trial of Growth. Up to 3 repositories, with fixes that span them, and 10 Mapped Issues included. No credit card required.
Final billing currency is set at checkout from your billing address.
How cancelling and refunds work: Refund and cancellation policy.
Enterprise
From $24,000/yr
Committed Mapped Issue volume at a lower per-issue rate, on a contract that fits your procurement.
Talk to sales- Everything in Scale
- Custom Mapped Issue volume and rate
- Unlimited connected repositories
- Annual contract, paid by invoice
- DPA and security review support
- Shared Slack channel with the founders
- Hands-on onboarding
What counts as a Mapped Issue
A bug, or a specific feature request, that Watari is confident about and has mapped to your code. Everything else that arrives is handled and never billed.
- Checkout hangs on SafariBug mapped to your code: counted (Mapped Issue 1)
- How do I export last month’s invoices?How-to: answered, not billed
- Booking times are an hour offBug mapped to your code: counted (Mapped Issue 2)
- Checkout spins again on my iPadRepeat of an issue already counted: billed once, not per ticket
- Could you add a dark mode?Open-ended request: filed to your tracker, not billed
- Add the order number to the receipt emailSpecific feature request mapped to your code: counted (Mapped Issue 3)
- Reports page is slow some morningsNot confident in the code: needs your review, not billed
- Where do I find my API key?How-to: answered, not billed
Mapped Issues this month
3of 8 tickets
Draft pull requests, the customer update and tracker sync come with every Mapped Issue and are never billed.
Compare plans
| Features | Starter | Growth | Scale | Enterprise |
|---|---|---|---|---|
| Included Mapped Issues / month | 20 | 60 | 150 | Custom |
| On-demand Mapped Issue rate | $25 | $20 | $15 | Custom |
| Hard cap (auto-pause) | 50 | 150 | 400 | Custom |
| Connected repositories | 1 | 3 | 10 | Unlimited |
| AI bug & feature extraction | Included | Included | Included | Included |
| Bug-to-code mapping | Included | Included | Included | Included |
| Draft pull requests | Included | Included | Included | Included |
| Customer-facing RCA | Included | Included | Included | Included |
| Slack, Microsoft Teams, Linear, Jira, GitHub Issues, Azure Boards sync | Included | Included | Included | Included |
| 80% / 100% spend alerts | Included | Included | Included | Included |
| Inferred CODEOWNERS (ownership map + 1-click PR) | Included | Included | Included | Included |
| Cross-channel bug clustering + RCA fan-out | Included | Included | Included | Included |
| Multi-repo bug fan-out | Not included | Included | Included | Included |
| Slack support channel | Not included | Not included | Included | Included |
Frequently asked questions
What is a Mapped Issue?
A Mapped Issue is a structured bug report, or a code-actionable feature request, extracted from a customer support ticket or an issue your team hands to Watari, and paired with the file(s) and function(s) in your codebase that our retrieval ranks as the most likely cause. Draft pull requests, RCA back to your customer, and tracker sync to Jira, Linear, GitHub Issues and Azure Boards are bundled with every Mapped Issue and never billed. We do not claim the top-ranked file is always the right one: on our published benchmark the top-ranked file is correct 87.0% of the time, which is why the Mismapped credit below exists and why the whole benchmark is public.
How often is the mapping right?
87.0% at rank 1 on out-of-sample public repositories, measured against a protocol we registered before running it. Published bug-localization research on customer-written reports lands between 28% and 42%, so we are ahead of it, and we would rather you read the number than take the word "mapped" on trust. Every case, every miss and the raw results are on our Proof page.
When does the meter fire?
The meter fires the moment a Mapped Issue is persisted: extraction is confident and at least one code location is a confident match. We never charge for downstream delivery (PR, RCA, sync), for a question, or for an open-ended feature request. A small, specific feature request that we map to your code counts the same as a bug, and only once however many tickets ask for it. If we map the wrong file or function, flag it as Mismapped within 7 days, from the bug itself, for a credit on your next invoice.
After my trial ends?
Nothing is charged automatically, because the trial takes no card. When it ends, Watari stops reading new reports until you choose a plan, and your connections, repositories and issues are kept. You can change plan or cancel any time from the billing settings page.
Can I change my plan later?
Yes. Upgrade or downgrade at any time from billing settings. Upgrades take effect immediately; downgrades take effect on the next billing cycle.
What happens if I exceed my included Mapped Issues?
Growth and Scale flex with on-demand Mapped Issues at $25 / $20 / $15 per Mapped Issue. Starter pauses at the hard cap with an in-app upgrade prompt, no surprise bills.
Do you offer annual billing?
Yes. Starter, Growth, and Scale all offer annual billing for the equivalent of 2 months free (≈17% off). Enterprise is an annual contract.
Do you offer volume or enterprise pricing?
Yes. Enterprise contracts start at $24,000 a year and commit to a Mapped Issue volume each year at a lower per-issue rate than the self-serve plans, with unlimited repositories, annual invoicing, DPA and security review support, and a shared Slack channel with the founders. Talk to sales and the founder replies within one business day.
What is “Ownership intelligence”?
Watari reads your repo’s CODEOWNERS to auto-route reviews on the PRs we draft. When you don’t have a CODEOWNERS file, we suggest the right owners from who actually changes each file and offer a one-click PR to adopt them. Bundled, available on every plan.
What if the same bug is reported by multiple customers?
Duplicate reports across your help desks become one bug, one PR, and one update to every customer who reported it. You’re billed per fix, not per ticket. Bundled, available on every plan.
Do issues from our tracker count differently?
No. An issue Watari picks up from Jira, Linear, GitHub Issues or Azure Boards is billed exactly like a support ticket, only when it becomes a Mapped Issue. Progress comments on the issue are included.
When a support ticket reports a bug, your engineers get a drafted fix.
Connect your help desk or your issue tracker, then GitHub or Azure DevOps. Watari maps each bug to the exact file and function in your code and drafts the fix as a pull request your CI checks.
14 days free. No card. Cancel any time.