Everyone in the loop is doing their job. The bug still waits.
weeks
twenty minutes to a PR
Patcharc is the pipe and the policy between the three. Not another chatbot, coding agent or support tool.
One bug, start to finish. Patcharc does the legwork; your team makes every call.
It arrives from wherever your customers already write to you: Intercom, Zendesk, email, Slack or the built-in form. Or from your tracker, when an issue in Jira, Linear, GitHub or GitLab gets the label: it was approved there, so it skips triage. Nobody writes it up twice.
Before anyone opens it, the report carries the Sentry trace, the session before the error and the files the stack trace points at, with a confidence line. Duplicates and collisions are caught, so nobody has to reproduce it first.
Fix with AI or File a ticket: two buttons, both yours. Nothing is fixed and no ticket exists until one is clicked. A feature request never becomes a fix; it goes to the needs-human lane.
Fix with AI writes the fix in a fresh sandbox and opens it as a draft PR; your engineer reviews and merges it on GitHub. A ticket is closed by whoever fixes it. Either way, the customer hears “fixed” in the channel they wrote in.
Every click, connection, run, PR and setting change is logged, as a sentence, for the life of the workspace.
Follow one run, from the click to the merge.
Only a teammate with the button can, never the customer. The ticket is created, your Slack thread hears it, and the customer is told you’re on it.
A Firecracker microVM with its own kernel, and the toolchain and the agent already inside. It shares nothing with any other run.
It comes from the vault, encrypted under a master key in AWS KMS and unlocked for this run alone. Inside, the agent only ever sees a placeholder.
A GitHub token that lasts an hour and opens this one repo brings in a shallow clone. Dependencies install on their own five-minute clock.
Claude Code or Codex with your key, or Patcharc’s own agent on Managed AI. The customer’s words arrive labelled untrusted, next to the evidence and your team’s instructions.
It edits the code and runs the tests for what it touched. It can reach GitHub, the model and your package registries, nothing else, inside a ten-minute cap.
The agent never runs git: Patcharc makes one commit, co-authored by the person who clicked. The PR is linked on the ticket, posted in your Slack thread and noted for support.
Every merge is a person’s, on GitHub, and logged. The ticket moves to Done, your Slack thread hears it, and the customer is told it’s fixed.
At a limit the run stops, the machine is destroyed, and the card offers File a ticket, already filled in. Every run has a known maximum cost — yours and ours.
For the CTO who says no by default
These are not toggles a customer can flip. They are how Patcharc is built, in the open-source core and in the cloud, and they are the first thing to read in the code.
Locked in the code
End users never trigger code. Only a human on your team does, with a button.
Nothing merges automatically. Every merge is a human’s, on GitHub, and logged with who merged.
Every action is logged: who connected what, who clicked, what ran, what PR opened, who changed a setting.Each as a sentence, for the life of the workspace, exportable.
Product decisions and feature requests go to a needs-human lane. Never forced into a fix.
Report text is untrusted input — data for the agent, never instructions to Patcharc.
Pause Patcharc One click by an owner or admin stops runs, ingestion or both within seconds; webhooks are held, never dropped.
Only two things cost money per fix: sandbox minutes and, on Managed AI, model tokens. Both are capped before a run starts, and both are visible before they bite.
Fix with AIFile a ticket
Quota reached: buy credits or wait.
Every cap is shown on the button before it is reached and named when it is. No customer can trigger a cost they have not already paid for — that rule protects you as much as us.
The planevery connector, unlimited members
$199Sandbox minutes3,000 a month; a nudge before they run out
IncludedModel tokens on your keybilled by your provider
Your keyManaged AI credits5 included a month; more bought before use, under a ceiling you set
PrepaidEach fix attempthard limits on minutes, tokens, retries, memory
Known maximumFile a ticketunlimited, on every plan
FreeOverageNone. At a cap the run does not start.
Nothing runs without a click. Nothing merges without a human.
Nothing else.
Encrypted per workspace, revocable by you, added at the machine’s edge. The agent only sees a placeholder.
New for every run. It reaches GitHub, the model and your package registries. Nothing else.
Who connected, clicked, ran and merged, as a sentence, for the life of the workspace.
Encrypted, with point-in-time recovery. Restored within an hour.
No SOC 2 report yet. We publish the threat model, the subprocessor list, the retention table and the restore drill instead.
The core is AGPL-3.0. Read the connectors, the sandbox limits and the five rules before you give it a key. Run it yourself, or let us run the same core.
packages/adaptersEvery connector: a report in, actions outpackages/coreThe pipeline and the five rulesapps/workerFix runs and their sandbox limitscloudBilling and Managed AI, under a commercial licence. The open code never imports it.SECURITY.md90-day coordinated disclosuregit clone https://github.com/MahmoudSumairat/patcharc
cp .env.selfhost.example .env
docker compose upSelf-hosted: BYOK only, one repo, every safety rule.
Five slots for your tools and one for the AI agent, every one optional. Not built yet? Join its waitlist — the counts decide what we build next.
Where customers report it
None connected? The built-in form is always there.
The evidence
None connected? Paste a trace, a log or a screenshot on the card.
Where the ticket lives
None connected? Patcharc tracks it: Mark in progress, Mark fixed.
Where the PR opens
None connected? File a ticket still works, in full; Fix with AI says why it is off.
Where your team hears
None connected? A daily email digest.
Who writes the fix
None connected? File a ticket still works.
Watch a complaint arrive in Intercom, the evidence attach, an engineer press Fix with AI and the PR merge — on InvoiceHub, our demo SaaS.
For teams of three to thirty engineers. A workspace is one application, and the whole team comes in — engineers, support, QA, managers — with no seat math.
For one app in one repo.
$99 a month per workspace
annual at ten months’ price
Join the waitlist for Starter (opens in a new tab)In every plan
For a product across a few repos.
$199 a month per workspace
annual at ten months’ price
Join the waitlist for Team (opens in a new tab)In every plan
For several products, or a busy queue.
$399 a month per workspace
annual at ten months’ price
Join the waitlist for Business (opens in a new tab)In every plan
Bring your own key on any plan, or add Managed AI. Prepaid credits; one credit is one fix attempt. Never postpaid.
Free on your own servers
The open-source core, run by you, with your own key.
from $10k a year, annual up front
For organisations of fifty people and more, on your own key or Managed AI.
No free trial — the open-source edition is the free path. Money back if Patcharc has not opened a PR or filed a ticket for you in your first 14 days. Prices exclude VAT; billing by Paddle. Refund policy
Into a new virtual machine for the length of the run, as a shallow clone, and it is destroyed with the machine. On BYOK the model sees it through your key; on Managed AI through ours, added at the network edge, under Anthropic’s API terms, which the security page states.
Nothing ships: it is a draft PR. Your engineer reviews it like any other, asks for changes or closes it, and File a ticket is one click away.
Both, always. BYOK is the default and the only option in the open-source edition: your Anthropic or OpenAI key, your traffic. Managed AI adds prepaid credits on any plan for teams that would rather not manage keys.
Downgrades never delete. Your data stays readable; runs stop; delete the workspace whenever you like and nothing of yours remains — proven by a test.
Connect a support tool and a repo, press the button on the next bug, and watch the PR arrive. Or read the code first. Either way, nothing runs without you.
Built in the open by one founder. The roadmap, the decisions and the progress board are in the repository.