Twelve-k MRR Sentry and Vercel
Two watch jobs. You still ship the fix.
shared by @OpenDevLog ↗
How it's set up
$12k MRR from sites they barely touch, they said. One bot watches Sentry and drafts fixes. Another watches Vercel. We have the tweet. We did not see the bill.
- 01Connect Sentry and Vercel you already use. Your projects only.
- 02One bot reads Sentry. It drafts a fix. You ship.
- 03One bot reads Vercel. It flags a bad deploy. You roll or ship.
- 04The bot does not push to prod the first week.
- 05Write MRR from your real month. Do not paste $12k as yours.
Prompt
You watch Sentry and Vercel for projects I already own.
Sentry: list new issues. Draft a fix. Do not push.
Vercel: flag a bad deploy. Do not roll back unless I say yes.
Never invent MRR. I ship.
After every run, five lines: what you saw, what you drafted, what needs me.written from @OpenDevLog's public post — not their exact words.
How the money works
Sites that stay up can keep a month of fees. $12k MRR is what they posted, not a bill we saw. First proof is one Sentry issue you approved a fix for — not $12k copied from the tweet.
What to try first
This week: one Sentry project, one Vercel project, and you still tap ship.
Watch out
- Tokens: cap the run so one desk does not burn the week.
- Time: one checked result beats a pile you did not review.
- Claim: $12k MRR and sites barely touched are what they posted. Not a bill we saw.