How does Watari connect to GitHub — an App or a token?

A GitHub App, installed from Settings → Integrations. An App installation is scoped to one organization and to the repositories you select, and any org admin can revoke the entire installation in one click. Watari never uses a personal access token — those are user-bound, harder to revoke cleanly, and carry broader scope than the pipeline needs. One GitHub installation maps to exactly one Watari workspace.

What permissions does the GitHub App request?

The minimum the pipeline needs: Repository contents (read + write) to index code and push draft-PR patches; Pull requests (read + write) to open drafts, request reviewers, and answer iteration comments; Issues (read + write) for GitHub Issues sync when enabled; Metadata (read, required by GitHub for all Apps); and Checks (read) to surface CI status on drafts. The App cannot delete branches, force-push, or change repository settings.

Does Watari respect branch protection and CODEOWNERS?

Yes to both. Reviewers are assigned from your `.github/CODEOWNERS` file (Watari synthesizes and offers one if you have none). Draft PRs open against your default branch and sit behind your protection rules — if you require passing status checks or a minimum number of approvals, the PR will not merge until your CI and your human reviewers satisfy them. Watari observes CI; it never bypasses a protection rule.

Does Watari work across multiple repositories?

Yes. When a bug maps to code across more than one repository in the same GitHub App installation, Watari opens linked draft PRs in each repo and tracks them as a stack, each routed via that repo’s own CODEOWNERS. The customer-facing RCA is held until every contributing PR merges and the production deploy confirms the fix is live across all affected repos. Multi-repo fan-out is available on Growth and above.

Does Watari support GitHub Enterprise Cloud or self-hosted GitHub Enterprise Server?

Today Watari connects to repositories on github.com, including organizations on GitHub Enterprise Cloud. Self-hosted GitHub Enterprise Server (behind your own firewall) is not supported yet — if that is a requirement for your team, tell us and we will scope it. You can also mix GitHub and Azure DevOps repositories in a single Watari workspace.

You pay per Mapped Bug — a structured bug paired with the file and function in your repo, both at ≥ 0.7 confidence. Draft PRs, customer-facing RCA, and Jira / GitHub Issues / Linear sync are all bundled, never metered. The meter fires at persist time of a qualifying bug; non-bug tickets (billing questions, account requests) never cross the gate. If Watari maps to the wrong file, flag it Mismapped within 7 days for a credit on your next invoice.

Is my source code safe?

Watari does not store your source code — only vector embeddings and metadata. The actual code is fetched from GitHub on demand and discarded after use. Tokens and secrets are AES-256-GCM encrypted before they hit the database, and tenant data is isolated via Postgres row-level security on every table. We never train models on your code. Full detail at watari.ai/security.

GitHub App · Source control

Watari for GitHub

Your support tickets become draft pull requests — in your repos.

Install the Watari GitHub App and your Zendesk, Intercom, and Freshdesk tickets arrive in GitHub as draft pull requests, each mapped to the exact file and function responsible. Reviewers are routed via CODEOWNERS, the draft sits behind your branch protection, and the customer-facing RCA waits for your production deploy to confirm the fix is live.

Install Watari free See pricing

The GitHub App installs from your Watari dashboard — sign up free, then Settings → Integrations → Install GitHub App. Setup and permissions are documented at the GitHub connection guide.

Trial: 14 days · 10 Mapped Bugs
Card required: No
Connect: GitHub App · 1 click
Mismapped credit: 7 days

What is Watari for GitHub?

Watari for GitHub is a GitHub App that turns customer support tickets into draft pull requests. It indexes your repositories, extracts a structured bug from each ticket, maps it to the responsible file and function at ≥ 0.7 confidence, and opens a draft PR routed via CODEOWNERS — behind your branch protection. The customer-facing RCA is published only after the merge lands in a successful production deploy.

Why support and engineering teams install the Watari GitHub App

The ticket lands as a diff in your repo

Support tickets from Zendesk, Intercom, and Freshdesk arrive in GitHub as draft pull requests — the patch and the test already written, type- and lint-checked. Your reviewers open a diff, not another board.

Mapped to the exact file and function

Watari indexes each connected repo and pins every bug to the responsible file and function, each with a 0–1 mapping confidence. A Mapped Bug clears a dual ≥ 0.7 gate — extraction and code-mapping both — before a PR is ever drafted.

CODEOWNERS-driven reviewer routing

Reviewers come straight from your `.github/CODEOWNERS` file. No CODEOWNERS? Watari synthesizes candidates from your commit history and opens a one-click adoption PR — the draft PRs still open either way.

Respects branch protection — never bypasses it

The draft sits until your required status checks pass and your required approvals are given. Watari observes CI but cannot force-push, delete branches, or merge past a protection rule. Your gates stay your gates.

Multi-repo fan-out across the installation

When a bug spans more than one repository in the same GitHub App installation, Watari opens linked draft PRs in each and tracks them as a stack — every contributing PR routed via that repo’s own CODEOWNERS.

Customer reply gated on production deploy

The customer-facing RCA is held until the GitHub `deployment_status` webhook reports success and the Compare API confirms the merge SHA is live in production. A later rollback parks the RCA and raises a banner.

How Watari turns a support ticket into a draft GitHub PR

Install the Watari GitHub App
From Settings → Integrations, click Install GitHub App. You are redirected to GitHub to choose the organization and select which repositories Watari may access — All repositories or a hand-picked set. Any org admin can revoke the whole installation in one click. It is a GitHub App, not a personal access token.
Watari indexes each selected repository
Watari fetches each repo and builds a searchable index of its code — a few minutes for a typical SaaS repo, longer for a large monorepo (progress is visible under Codebase). Pushes to the default branch trigger an incremental reindex automatically, so the index stays current with no manual step.
Connect a support tool and let tickets flow in
Connect Zendesk, Intercom, or Freshdesk. From the next qualifying ticket onward, a vision-aware model extracts a structured bug — severity, reproduction steps, expected vs actual, customer impact, and original-language verbatim. Below 0.7 extraction confidence, the bug queues for review and is never billed.
Each bug mapped to the file and function
Watari searches your indexed code and narrows to the exact file and function responsible, each with a 0–1 mapping confidence. A Mapped Bug requires both extraction and mapping at ≥ 0.7 — below that, the bug queues for review and is never billed.
Draft PR opened, CI watched, customer reply held for deploy
The draft pull request opens in GitHub with the patch, the test, and reviewers from CODEOWNERS. CI status is observed; reviewer comments trigger non-force regenerations. After the merge lands in a successful production deploy — confirmed via the deployment_status webhook and Compare API — the customer-facing RCA is posted back to the originating ticket in the customer’s language.

What GitHub access Watari needs

The Watari GitHub App requests the minimum permissions the pipeline needs, granted at install time and scoped to the repositories you select. The App cannot delete branches, force-push, or change repository settings.

Read: contents, pull_requests, issues, checks (CI status), and metadata (required by GitHub for all Apps) — for the repositories you select at install.
Write: contents (push the draft-PR patch to a new branch), pull_requests (open drafts, request reviewers, answer iteration comments), and issues (only when GitHub Issues sync is enabled).
Store: Vector embeddings and metadata — never your source code, which is fetched on demand and discarded after use. The installation token reference is AES-256-GCM encrypted before persistence. Tenant data is isolated via Postgres row-level security on every table.
Never used for: Model training. Your source code and tickets are not used to train any model — ours or any third party’s. Full detail at watari.ai/security.

Pricing

You only pay when Watari delivers a Mapped Bug — a structured bug paired with the file and function responsible, both at ≥ 0.7 confidence. Draft PRs, customer-facing RCA, and Jira / GitHub Issues sync are bundled.

Starter

$400/mo

20 Mapped Bugs included · $25/bug on-demand

For small teams shipping their first Mapped Bugs from a single repo.

Growth

$900/mo

60 Mapped Bugs included · $20/bug on-demand

For teams running customer support against a multi-repo product.

Scale

$1,800/mo

150 Mapped Bugs included · $15/bug on-demand

For multi-repo SaaS with a dedicated support function.

Indian buyers (with GSTIN) are billed in INR; everyone else in USD. 14-day free trial · 10 Mapped Bugs included · no credit card required. Annual billing saves 17%. Full plan comparison at watari.ai/pricing.

Security & privacy

GitHub App — org-scoped, one-click revocation, minimal permissions.
We never store your source code — only embeddings and metadata.
Tokens and secrets AES-256-GCM encrypted at rest.
Postgres row-level security on every tenant-scoped table.
Your source code and tickets never train any model.
Full security posture at watari.ai/security.

Frequently asked questions

Your next support ticket arrives as a draft PR.

Connect Zendesk, Intercom, or Freshdesk, then GitHub or Azure DevOps. Tickets land mapped to the file, function, and line — ready for your reviewer to take over.

Start free trial

Trial length: 14 days
Bugs included: 10 Mapped
Card required: No
Mismapped credit: 7 days
Cancel: Any time

You only pay when we know what to change.