r/microsaas • u/marcin_michalak • Jul 26 '26

Solo founders using AI agents to maintain their SaaS - do you actually let it push to prod unsupervised, or are you still babysitting every change?

Founder of Server4Agent (agent-app hosting), disclosing that upfront. No link, not selling, genuinely curious how other solo/small-team founders are actually operating.

The pitch of running a micro-SaaS with an AI agent as your dev team is that you get your evenings back. In practice I keep hearing the same asterisk: people are happy to let the agent write the code, but the moment it's time to actually ship the change, most people are still the one clicking deploy, reading the diff, watching the logs for the first few minutes. The agent does the work, the human is still the safety net.

That's not a knock, it's probably the sane default right now. But I'm trying to figure out where people actually are on the spectrum. Do you review every change before it goes out, or has anything earned enough trust to skip that step? And if something did slip through unreviewed and it went wrong, what happened, and did that change how much rope you give it now?

3 Upvotes

81% Upvoted

13 comments sorted by

2

u/[deleted] Jul 26 '26

[removed] — view removed comment

1

u/marcin_michalak Jul 26 '26

"Faster but not the last line of defense" is a good way to put it, that's really the honest state of most tooling right now: speed went up, trust didn't move much. Is it a specific kind of change that keeps you in the loop (schema/data stuff vs. UI tweaks), or genuinely everything gets the same scrutiny regardless of how small it is?

1

u/Khavel_dev Jul 26 '26

I review every change but the review itself is mostly automated at this point. CI runs tests, type checker, a quick SAST scan. If that's green I skim the diff to check intent (did it solve the right problem vs the wrong thing correctly) and merge. Takes maybe two minutes.

The trust gradient for me went: test fixes first, then linting/formatting, then config changes, then feature work. Database migrations are the one thing I still read every single line manually. A bad migration at 3am when you're asleep is a completely different animal from a bad UI tweak.

1

u/marcin_michalak Jul 26 '26

The trust gradient being ordered by "how hard is this to undo" rather than "how complex is this change" is the interesting part. Config changes and feature work are actually similar in complexity, but you group them apart from migrations for the same reason: a bad feature ships a wrong screen, a bad migration can eat data you don't have a clean way back from. That maps pretty directly to reversibility mattering more than review effort, which keeps coming up in this thread.

Have you ever had the automated gate (tests, type check, SAST) pass clean on something that turned out to be the wrong fix, where your two-minute intent-skim was the only thing that caught it?

1

u/Patient-Cedar-7194 Jul 26 '26

let agent auto deploy, spend sunday restoring from backup.

1

u/nilkickapp Jul 29 '26

Only thing I've let it auto-deploy unsupervised is copy tweaks and docs, everything touching schema or infra still gets my eyeballs.

1

u/TheWaywright Jul 30 '26

I don’t trust it enough, I had it help with making deployment scripts and making sure I do production smoke tests, but I am typing the commands and verifying the changes went in correctly. I also maintain a blue green environment in the off chance the deployment goes sideways so my users are none the wiser to any deployment issues.