For agencies
Every client app you ship, still checked after handover.
You built it fast with AI. The client keeps prompting after you leave. PatchLabs watches every client app on one plan and tells you the moment a new leak appears, with the fix already proven.
Monitoring
Apps
Agency plan · 7 of 10 apps · 4 of 10 seats
The agency plan
One workspace for your whole portfolio.
Everything here works today. What’s missing is listed below.
Client labels on every app
Alerts and reports say “Client A” instead of a repo slug.
Weekly or monthly re-checks
Set per app. Only new findings raise an alert.
10 seats, owners and members
Invite your developers by email. Owners manage members and the webhook.
Into your Slack
One webhook for the workspace: every finished check posts the client name and report link.
API keys for your pipelines
Re-check from any client’s GitHub Actions after a migration merges.
Questions in plain English
When the fix depends on what the client intends, the report asks them, with a recommended answer.
How agencies use it
From handover to “we caught it first”.
The value isn’t one clean report at launch. It’s telling the client about a leak, fix in hand, before anyone else finds it.
Add the repo
Client label and schedule. Public repos today; private with our GitHub App.
client: Client A schedule: weeklyVerify
Someone with write access commits the verification file once. The first check queues.
patchlabs-verify.txtSend the report
Public by link, plain English: what leaked, the fix and the proof.
patchlabs.dev/check?id=…Re-check weekly
A new leak posts to your Slack and emails your team, with a proven fix ready.
#client-alerts Client A new leak
Not built yet
What agencies ask for that we don’t have yet.
We’d rather tell you now. Tell us which matters most and it moves up the list.
Client-only logins
Everyone in a workspace sees every app. Until client views exist, share each client’s report link.
White-label monthly reports
Reports carry PatchLabs branding today. A branded monthly summary per client is on the list.
Private repos and automatic PRs
Both need our GitHub App. Until then: public repos, and fixes as a file or one-click commit.
Can my clients see each other’s apps?
Only if you invite them into your workspace, because every member sees every app in it. Keep clients out of the workspace and send them their report links instead.
Do I need access to the client’s repo?
Someone with write access has to commit the verification file once. That can be you, or the client.
What if a client’s app doesn’t use Supabase?
Code checks still run. The Lab needs a supabase/migrations folder to rebuild the database, so apps on other backends can’t be lab-tested yet.
Can I resell this to clients?
Many agencies include monitoring in a care plan. Talk to us before you put our name in a contract, so we can agree how it is described.
Is there a free trial?
Your first app is free forever, with monthly re-checks. Try it on one client app before you request the agency plan.
Free check
Start with the client app you worry about most.
Paste the public repo. You’ll get the leaks, the fix and the proof on one page, ready to send.