All posts

Launch-ready AI-built app: what I check before real users

Your app works. You built it with Lovable, Bolt, Cursor or v0, it looks finished, and the first users are about to sign up and pay. The gap between "it works on my screen" and "strangers can pay for it" is mostly made of things the AI builder never saw: real payments, real email inboxes, real deploys and real bills.

This is the list I go through before an app takes real users and real money, on my own apps and on apps I'm asked to fix. The database part has its own post: 5 database checks for Supabase, Firebase and Neon. Everything else is below.

1. The price comes from your server, not from the browser

Generated checkout code sometimes sends the amount from the page to your server, and the server passes it on to Stripe. Anyone can change that number in the browser's developer tools and buy your product for one cent.

The fix: create the Checkout Session on the server with a Price ID from your Stripe dashboard, or look the price up in your own database. The browser only says which product, never how much.

How to test: start a checkout, change the amount in the request with DevTools and send it again. The Stripe page should still show your real price.

2. Webhooks: verified, repeat-safe, and actually arriving

The webhook is the part that turns "paid" into "account upgraded". It's also where AI-built apps break most quietly. Stripe's webhook docs list what the handler must do:

  • Verify the signature. Check the Stripe-Signature header with your endpoint's signing secret, using the raw request body. Without it, anyone can send your endpoint a fake "payment succeeded".
  • Handle repeats. Stripe says endpoints "might occasionally receive the same event more than once". Store the event IDs you've processed and skip the ones you've seen, so nobody gets two upgrades or two emails.
  • Don't rely on order. Stripe doesn't guarantee events arrive in the order they happened.
  • Answer fast. Return a 2xx status first, then do the slow work. In live mode Stripe retries failed deliveries for up to three days, so a crash can mean three days of retries before anyone notices.

After your first real payment, open the event deliveries list for your endpoint in the Stripe dashboard. Every event should say "Delivered".

3. Test mode and live mode are two different worlds

Everything worked in test mode. On launch day the live keys go in, and one thing still points at test. These are the usual culprits:

  • Price IDs copied from test mode, which don't exist in live mode.
  • The webhook signing secret: test and live have a different one, even for the same URL.
  • A secret key that ended up in the front end. Only the publishable key belongs in the browser; the secret key stays on the server.

Failed renewals, EU VAT, refunds and the Customer Portal are in taking payments in an AI-built app.

4. Every AI call: signed in, limited, capped

If your app calls OpenAI, Claude or Gemini, every request costs you money. An AI endpoint without limits is a bill that anyone on the internet can run up.

Make sure that:

  • the endpoint requires sign-in, or has a limit per visitor;
  • prompt length is capped;
  • each call's cost is logged;
  • the provider's dashboard has a hard monthly limit, not just an email alert.

I wrote about how I cap the AI costs of my own apps in what I learned shipping 5 AI apps.

5. Sign-up and password emails that arrive, and link to the live site

A classic: the confirmation email arrives, and the link opens localhost:3000. In Supabase, the Site URL is the default redirect for these links. Supabase says to change it "from http://localhost:3000 to your production URL" and calls it "critical for email confirmations and password resets". Add your live domain to the Redirect URLs list too.

Then make sure the emails don't land in spam. Since February 2024, Gmail requires every sender to set up SPF or DKIM for its domain. Senders of more than 5,000 emails a day also need DMARC. Set all three up once, in your email provider and your DNS. How: SPF, DKIM and DMARC explained.

How to test: on your phone, sign up with a fresh Gmail address. Confirm the account, log out, and reset the password. If you also offer Google or Apple sign-in, see what breaks with social sign-in.

6. Make sure the live site runs the code you think it runs

This one happened to my own site. For up to four weeks, dizid.com served an old build. Netlify was set to deploy the master branch, while every commit went to main. Nothing failed, so nothing warned me. The site just stopped changing.

After every deploy, compare the commit in your host's deploy log with your latest commit, and open a page you just changed on the live site. It takes a minute.

7. A backup you have restored once

Every database host offers backups or restore points, and what you get depends on your plan. Find out what yours keeps and for how long. Then do one test restore into a copy or a branch before launch. You don't want to learn how restoring works on the day a migration deletes a table. What each host keeps per plan: backups on Supabase, Neon and Firebase.

8. Errors you hear about before your users tell you

Most first users who hit an error don't report it. They leave. Before launch, set up three things:

  • error tracking for the front end (Sentry has a free tier);
  • a look at your server function logs;
  • an uptime check on your home page and your checkout.

Then you know about the broken payment button before the first refund request arrives. Step by step, on free tiers: uptime checks and error alerts.

9. The small EU bits

If you sell in the EU, you need three small things:

This is technical help, not legal advice.

A one-hour test before launch

  1. On your phone, sign up with a new account, confirm it and reset the password.
  2. Buy with a real card, then refund it in Stripe. Check that the account upgraded and the webhook says "Delivered".
  3. Log in as a second user and try to open the first user's data (the database post shows how), and the admin pages (see anyone can open your admin page). Search the live site's JavaScript for secret keys (see is your API key exposed?).
  4. Use the AI feature a few times and check the provider's usage page.
  5. Restore a backup into a copy.
  6. Check that the live deploy matches your latest commit.

If all six pass, you're in better shape than most apps on launch day.

Want a second pair of eyes before launch?

I'm Marc de Ruijter, a Dutch full-stack developer with 25+ years in IT, working remotely for clients in Europe. I've shipped 20+ products alone, with Stripe, Supabase, Firebase, Neon and AI APIs. I go through this list on your Lovable, Bolt, Cursor or v0 app and fix what's open, in Dutch or English.

See how to hire me or send me a message.