Production

    Taking a Lovable app to production.

    Lovable gives you a real React and Supabase codebase in an afternoon, which is useful and not something to apologize for. What it does not give you is the unglamorous half: authorization that holds while someone pokes at it, row-level security configured rather than assumed, secrets that never reach the browser, and a deploy you can repeat. That half is what separates a working demo from something a paying customer can rely on.

    What usually needs fixing first

    This list is not a criticism of the tool. It is the same list for any codebase that was optimized for getting to a working screen quickly.

    Row-level security that is on and correct

    Supabase gives you row-level security. Generated apps often ship with it permissive or off, so the anon key in the browser reads more than you think.

    Authorization checked on the server

    Hiding a button is not a permission model. Every rule that matters gets enforced on the server, where the user cannot reach around it.

    Secrets out of the client bundle

    Service keys and third-party API keys move to server-side routes or edge functions. Anything already exposed gets rotated, not just moved.

    Billing that handles the unhappy path

    Stripe webhooks, proration, failed payments and dunning, with your database kept in step rather than assumed to be in step already.

    Tests where money and access live

    Not full coverage. Automated tests on authentication, permissions and billing, so those fail in CI instead of on a paying customer.

    A deployment anyone can run twice

    Environments, migrations and a pipeline that ships on push, plus a written runbook, so shipping does not depend on one person's memory.

    Harden it or rebuild it

    Most Lovable projects are worth keeping. The generated code is ordinary React and TypeScript, and ordinary code can be refactored. We recommend a rebuild only when the data model is wrong in a way that would have to be undone anyway, which is a decision about the schema rather than about the tool that produced it. You get that verdict in writing, with the reasoning, before anyone starts.

    What you have at the end

    Your own repository

    Source-code ownership from day one, with a commit history you can actually read.

    Infrastructure you control

    Running in your own accounts and on your own bill, not on someone else's plan.

    A written handover

    Architecture notes, setup, environment variables and a deployment runbook.

    A product ready for a customer

    Auth, permissions and billing tested, and a clear path to the next feature.

    Answered before you ask

    Is a Lovable app good enough to build on?

    Usually yes. It produces conventional React, TypeScript and Supabase code rather than a proprietary format, so there is nothing to escape from. The work is not translation, it is the production hardening any fast-built codebase needs: permissions, secrets, billing, tests and deployment.

    What is the most common serious problem you find?

    Row-level security left permissive on Supabase tables. Because the anonymous key ships in the browser, that means the data is readable by anyone who opens developer tools, not just by the app. It is quick to fix and worth checking today whether or not you hire anyone.

    Can you add Stripe subscriptions to what we already have?

    Yes, and it is one of the more common single pieces of work we get asked for. Plans, upgrades, proration, failed payments and the webhooks that keep your own database in agreement with Stripe. Scoped on its own it is a small, self-contained piece, quoted as one number before it starts.

    How much does a Lovable rescue cost?

    A production-readiness audit is a small, self-contained piece of work, priced on its own. The remediation depends on what the audit finds, and it comes back as one price agreed before anything starts. You get the findings and a number before committing to the work.

    Do we have to stop using Lovable afterwards?

    No. Plenty of teams keep prototyping new screens there and bring the ones that prove out into the main codebase. Lovable is a good place to try an idea and a poor place to keep a paying customer's data, and those two facts sit together perfectly well.

    Related

    Tell us what it has to do.

    Describe what you’re building, what it has to do and when it needs to be live. You’ll get back the architecture we’d use, the trade-offs, and a realistic timeline, before anything is signed.