How GuardMike works
This page describes how GuardMike works; each part is labeled in the app as available or still coming.
1. Connect your app
Add your public website address and, separately, where its code lives (Lovable, Base44 or GitHub). Connections show as unavailable until they are really connected.
2. Confirm the blueprint
GuardMike lists what your app should do. Nothing counts as a requirement until you confirm it — no silent guessing.
3. Background Watch
Between scans, GuardMike notices new code and new live versions, compares them with your approved list, and checks anything unexpected right away. Changed is reported separately from broken.
4. Twice-weekly Full Scan
Every Sunday and Wednesday, a complete check. Results are always shown as Passed, Failed, Blocked or Untested — never “everything works”.
5. Repair safely
Repairs are prepared in an isolated copy and tested independently. Big fixes wait for your approval; optional safe auto-fix covers only small, low-risk, undoable ones, and your live app is rechecked afterwards.
Two kinds of protection
Background Watch (Starting soon)
Keeps an eye on your app between scans. It notices when new code is saved or a new version goes live, asks “was this you?” about anything that isn't on your approved list, checks it right away, and sends quick “is my site up?” pings. Included with paid plans once it's switched on.
Twice-weekly Full Scan (On for paid plans)
Every Sunday and Wednesday at 7 a.m. New York time: your public pages, real-browser checks, your approved test journeys, and a comparison with your known-good version. You get a short, honest note afterwards.
Twice-weekly Full Scan
Every Sunday and Wednesday at 7:00 a.m. New York time (adjusts for daylight saving).
A complete check of your app: your public pages, real-browser checks, your approved test journeys, and a comparison with your known-good version. Separate from Background Watch, which keeps an eye on changes in between.
One check at a time, never two at once, so your app isn't overloaded. Want to check right now? Press Check Everything anytime.
What happens next: this automatic check isn't switched on yet. We'll let you know when it's ready. Nothing runs on its own until then.
Safe auto-fix, and your OK for anything big
Optional safe auto-fix handles only small, low-risk, undoable problems — and only if you switch it on, prove you own the app, and the fix passes a separate test copy first. GuardMike then rechecks your live app before calling anything fixed. Changes touching sign-in, payments, security, your data or database are never published automatically: big fixes always wait for your approval.
What you get
Learns what your app does
Finds your app's features and asks you to confirm how they should work.
Checks real tasks, not just “is it up?”
Tries the things your customers do — signing up, booking, paying, totals adding up.
Spots when something that worked breaks
Notices when an update quietly breaks something that used to work.
Looks into problems for you
AI investigates what went wrong and explains it in plain words.
Prepares a fix and tests it
Writes a small, targeted fix in a safe copy and tests it before you see it.
You stay in charge
Small, undoable fixes can go live on their own only if you switch that on — and only after they pass checks, with an undo ready and a re-check afterwards. Sign-in, payments, security and database changes always wait for your OK.
Clear, honest results
Every check says Passed, Failed, Blocked or Untested — with the evidence.
Tell us in your own words
Report a Problem lets you describe what's wrong, no tech words needed.
A living blueprint of your app
Your list of what the app must do, kept up to date with you.
No surprise costs
See your usage. If you bring your own AI account, its charges are shown separately.
The repair journey
- 1
Issue detected
A problem was found by a check or reported by you.
- 2
Investigation
The cause is being diagnosed.
- 3
Patch prepared in isolation
A fix is written in an isolated copy — never in your live app.
- 4
Independent tests
The fix is checked by separate tests before it can move on.
- 5
Your approval (or safe opt-in auto-publish)
High-impact changes always wait for you.
- 6
Merged into main code
The approved fix was merged into your main code on GitHub. Your live app changes only when your builder publishes it.
- 7
Post-deployment verification
The live app is re-checked after publishing.
- 8
Rolled back
The change was reverted to the previous version.