Who it is for

Your Lovable app is up. Is sign-up?

Lovable builds and publishes your app. AxoWatch watches the published version: a real browser goes through login, sign-up and the way to payment on your own domain, and you hear about it when a step breaks after a change.

The preview works. The live app is a different place.

You test in the editor, as yourself, with your data. Your users arrive on the published app, logged out, on your domain. A lot can differ between the two:

  • Login sends people to the preview address or to localhost, because the live domain is missing from the Redirect URLs in Supabase.
  • A secret exists in the editor but not where the app runs.
  • Stripe test mode and live mode have different webhook secrets. After the switch to live, people pay and the app never unlocks their plan.
  • Confirmation emails come from Supabase's built-in email service, which only delivers to your team. You get them. Your users don't.
  • The custom domain loses its DNS record or certificate while the lovable.app address keeps working.

None of these shows up in the preview, and none of them takes the site down.

How it works

  1. 1

    Open your published app and press Record

    Use the AxoWatch Chrome extension on the live URL, not the editor. Log in with a test account the way a user would. Every click and field becomes a step; the password is added in AxoWatch, not recorded.

  2. 2

    Finish on what proves it worked

    End the flow with one check: the URL is /dashboard, your app's main screen shows, or the Stripe Checkout page opens with the right plan.

  3. 3

    Let it run after every change

    AxoWatch repeats the flow on a schedule, so it runs after every publish without you remembering. When a step fails twice in a row you get one alert with the step and screenshots, in Telegram, Slack, Microsoft Teams, a webhook or, on paid plans, email.

Lovable Project monitoring and AxoWatch: use both

Lovable's Project monitoring is in beta on Pro, Business and Enterprise. It reviews your code and recent visitor errors on a schedule (daily by default, or weekly) and emails you important findings. Lovable's browser testing clicks through the preview in a real browser when you ask it to.

Both look from the inside. AxoWatch looks from the outside, at the published app on your domain: it logs in every hour on Starter and every 30 minutes on Pro. Lovable is good at finding the cause in your code. AxoWatch tells you that real visitors can't get through.

They barely overlap, so turn on both.

Flows to set up first

  1. Login: log in with a test account and check that the dashboard appears. This catches broken auth, redirect URLs and missing keys.
  2. The sign-up form: fill in the form and stop before the final button, so no new accounts pile up. Or go all the way to "Check your email" if your app deletes test accounts.
  3. The way to payment: open pricing, pick a plan and check that the Stripe Checkout page opens. Stop there. Never let a check pay with a real card.
  4. Your main feature: the one action people pay for, done with the test account.

Then add an uptime check for your custom domain. It also warns you before the SSL certificate expires.

What AxoWatch doesn't do

It doesn't scan your app for security problems. Lovable has security scans built in, and for anything sensitive a review by a person is worth it. A flow also can't open your inbox, so it won't tell you whether a confirmation email arrived. Test that by hand with an address outside your team.

Questions

Do I need to change anything in my Lovable project?

No. AxoWatch visits your published app from outside, like any visitor. You record flows with the Chrome extension on the live URL; nothing is added to your code.

Does it work on a lovable.app address and on a custom domain?

Yes. Any public URL works. If you have a custom domain, monitor that one, since it's what your users open.

Is this a replacement for Lovable Project monitoring?

No, it's a different check. Project monitoring reviews your code and visitor errors on a schedule. AxoWatch goes through sign-up, login and checkout on the live app, as often as every 30 minutes on Pro.

Can AxoWatch collect the errors from my Lovable app?

We're testing error tracking for apps on Lovable's stack and will update this page once it's confirmed. For now a failed flow shows you the step that broke and a screenshot of every step.

Will the checks charge my Stripe account?

Not if the flow stops on the Stripe Checkout page, which is what we recommend. A check should never enter a real card.

Let the guard take the night shift.

Add your site, show the guard what matters, and fix what breaks before your visitors give up.