The Mapped Bug meter

Watari bills on a single unit — the Mapped Bug — and bundles everything else into the subscription.

What is a Mapped Bug?

A Mapped Bug is a structured bug report that passes two independent confidence gates:

1. Extraction confidence — the AI extraction step produces a high-confidence structured bug from the ticket content (severity, repro steps, expected vs. actual behavior, customer impact). If the ticket doesn't clearly describe a software bug — billing disputes, account access requests, general questions — it doesn't pass this gate.

2. Mapping confidence — at least one code location (file path + function) in your connected repository is matched with high confidence. A bug without a credible code mapping does not qualify.

Both gates must pass. A bug that extracts cleanly but cannot be mapped to code is not a Mapped Bug. A ticket that mentions code but whose extraction is ambiguous is not a Mapped Bug. The specific threshold values are calibrated internally and subject to tuning; we describe them qualitatively here as "high confidence."

When the meter fires

The meter fires exactly once per qualifying bug, at the moment the bug and its mappings are persisted to the database — before any delivery channel runs. The meter fires before the draft PR is opened, before any Jira issue is created, before any Slack notification is sent.

Re-running extraction or re-mapping the same bug does not fire the meter again. The billing event is idempotent: if the same bug qualifies again after a retry, only the first qualifying persist counts.

What is bundled (never metered)

The following are included in every plan at no additional charge:

• Draft PR generation — the initial patch and test opened as a draft GitHub PR.
• PR iteration — re-generation triggered by reviewer comments or CI failures.
• RCA generation and publish — the customer-facing root cause analysis, posted back to the original ticket after the fix deploys.
• Jira, Linear, and GitHub Issues sync — bug records pushed to your issue tracker.
• Slack notifications — bug detected, PR opened, PR merged, PR failed.
• CI status surfacing — pass/fail check status shown on the PR and in the Slack notification.
• The Watari dashboard itself — all views at /tickets, /codebase, /settings, and /billing.
• Mismapped credit handling — flagging a wrong mapping and receiving the credit.
• 80% and 100% spend alerts — notifications when you approach your included quota.

Hard caps and processing pauses

Each plan includes a fixed number of Mapped Bugs per billing period. When you reach your included quota, Watari pauses ticket processing by default — you will not receive surprise overage charges unless you have explicitly raised your overage limit.

From Settings → Billing, you can raise your overage limit up to your plan's maximum. This enables Watari to continue processing tickets past the included quota at the per-bug overage rate for your plan. The limit you set is a ceiling — Watari stops again when it reaches that number.

Design Partner plans have a fixed cap with no overage option. Enterprise plans are uncapped by contract.

When processing is paused, an in-app banner appears and your billing admin receives an email notification. Processing resumes automatically at the start of the next billing cycle, or immediately when you raise the overage limit.

Mismapped credit

If a Mapped Bug was billed but the code mapping was wrong, you can flag it from the bug detail page within 7 days of the bug's billing date. Select the mismapped reason (wrong file, wrong function, not a bug, duplicate, or other) and submit.

What happens next:

• The bug is marked mismapped and your usage counter for the current period decrements.
• A credit for the overage amount appears on your next invoice. Razorpay does not issue retroactive refunds — credits apply to the next billing cycle only.
• Self-serve credits are available up to 10% of your plan's included quota per billing cycle. Requests above that threshold are reviewed by the Watari team (you receive HTTP 202 and a confirmation email).

The 7-day window is counted from billed_at — the timestamp at which the bug qualified and the meter fired, not the timestamp at which the ticket arrived.

Currency routing

Watari bills in one of two currencies:

• INR — if your organization is based in India and you have provided a valid GSTIN (GST registration number). INR pricing includes 18% GST.
• USD — all other organizations.

Currency is determined at checkout by your billing address, not by a UI preference or your IP address. Once your first subscription is created, the billing currency for your organization is locked. To change currency, contact support.

Indian IP addresses see INR pricing displayed by default on the pricing page, but the actual checkout currency is always determined by your billing address and GSTIN — this prevents arbitrage.

Plan tiers

Annual plans (Starter, Growth, Scale) are billed at the equivalent of 10 monthly periods — two months free.

Full pricing details including per-overage rates and INR equivalents are at /pricing.

Next: Invoices, credits, and caps — mismapped credit window and overage cap configuration and Plans and pricing — Starter, Growth, Scale, and Design Partner tiers.