Group the signal
Merge duplicate reports and preserve the customer context.
Support that ships
Your users report it. Supportopus gets it shipped.
Turn customer feedback into grouped issues, tested fixes, and feature pull requests. Your developers stay in control without living in the support queue — the agent runs on infrastructure you own, and nothing merges until someone on your team says yes.
Three of five founding design-partner seats are still open.
One queue. No support spiral.
Route the work
Send each issue to the right agent with your repository rules.
Review and ship
Approve tested pull requests with a clear trail back to users.
One loop, from complaint to merged fix
Most support tools stop at the reply. Supportopus is built around the rest of the job: turning what your users say into code you can ship.
-
Reports land in one place
A widget on your site, in-app reporting on iOS and Android, App Store and TestFlight feedback, or plain email. Your users report where they already are; you read everything in one queue.
-
Duplicates become one issue
Related reports are clustered together, so fourteen versions of the same crash arrive as a single issue — with every affected customer attached, ready to be told when it's fixed.
-
You get a proposal, not a pile
For each issue, Supportopus names the problem, suggests the repository it belongs in, and lays out a short plan. Your triage becomes one decision: approve or dismiss.
-
Only then does the agent run
Nothing clones your code, pushes a branch, or spends a token until you approve. After that, a coding agent works unattended on always-on compute you control — a VPS, a Mac mini, a CI runner. Not your laptop, and not our cloud.
-
A tested pull request comes back
The agent works the plan, runs your checks, and opens a pull request with the plan and results attached. You review and merge it like any other PR. Nothing ships without you.
-
Customers get real answers
Supportopus drafts replies for you, and answers it can ground in your own knowledge base can go out automatically. Bug reports, refunds, and anything touching money or accounts always wait for a human.
The agent lives on your infrastructure
A coding agent with write access to your repositories is a serious thing to install. Supportopus keeps that agent inside a boundary you set.
-
Compute you control
The agent runs on an always-on machine in your world — a cheap VPS, a Mac mini on a shelf, the CI runner you already have. Your source code is checked out there, not on our servers.
-
Nothing moves without you
Approval is the ignition key. Until you click it, Supportopus only reads reports and writes proposals. No clones, no branches, no API spend happens on its own.
-
A trail you can read
Every proposal, every approval, and every agent run is recorded, so you can always answer "why did this PR exist?" — and show your future team how a fix came to be.
Autonomy is earned, not assumed
An AI that speaks to your customers should have to prove itself first. Supportopus starts careful and grows with its knowledge base — at the pace you set.
Day one
Grounded answers only
The assistant auto-sends a reply only when it can ground the answer in your docs and knowledge base. Everything else arrives as a draft for you to send, edit, or discard.
As it grows
You promote topics
As the knowledge base covers more of your product, you explicitly promote topics into auto-send — one at a time, on evidence. There is no confidence slider that quietly drifts toward unsupervised.
Always
Some things stay human
Refunds, billing, account trouble, legal questions, and angry customers are never auto-answered. And no reply ever claims a fix has shipped before you've merged it.
Built for the whole app, not just the website
Your product lives on the web and in the App stores, so your support system has to as well.
Web
A support widget for your site and app, plus email intake. Coding agents patch your web and backend repositories and open pull requests on GitHub.
iOS
In-app reporting where your users already are, with App Store and TestFlight feedback flowing into the same queue. Native fixes run on a Mac you control.
Android
The same in-app reporting for Android, with Play Store feedback alongside it. Native fixes ship through the same propose-approve-PR loop.
Who this is for
- You're the founder or CTO of a 2–20 person product company — and you are also the support queue.
- You have real users reporting real product problems, on the web or in the App stores.
- Your code lives on GitHub, and you have (or can stand up) an always-on machine you control.
- You want fixes shipped, but you still want to be the one who says yes.
Who it isn't for, yet
- Teams who want to keep Intercom or Zendesk and layer Supportopus alongside — ingest from other desks comes later.
- Support organizations with dedicated agents, SLAs, and hand-off workflows.
- Anyone who wants code changed without reviewing a pull request. That mode doesn't exist here.
Frequently Asked Questions
Does Supportopus replace my current support tool?
Yes. Supportopus is your support desk: your customers' reports live here, and the issue-to-pull-request loop hangs off those conversations. Pulling reports in from tools like Intercom while you keep using them is on the roadmap.
Does an AI talk to my customers?
Only within limits you set. Out of the box, the assistant auto-sends only answers it can ground in your knowledge base; everything else is a draft for you. Money, accounts, legal topics, and bug reports always get a human. You expand what's automatic — it never expands itself.
Where does my code go?
It stays where it is. The coding agent runs on a machine you control and checks your code out there. Supportopus orchestrates — it sends the approved proposal to your box and gets the pull request back. We never host your source.
What does "tested" mean?
The agent runs your project's checks on your machine before opening the pull request, and the PR arrives with the plan and results attached. It doesn't mean auto-merge: you review every PR, and only you merge.
What does it cost?
There's no public pricing yet. Our five founding design partners will shape it with us — that's part of the deal.
Three seats left
We're looking for three more of five founding partners
Not a waitlist — five named design partners with a real app, real users, and a machine they control. Two are already on board; three seats are open. You'll live in the desk, approve the proposals, and tell us where it's wrong. In return you get the loop working on your product, direct say over the roadmap, and pricing shaped around you.
Thanks — we'll read this and follow up if there's a fit.