Utplava Open dashboard

Learn

AI app safety for beginners. No code knowledge needed.

Short videos for people who build apps with AI. Each one explains, in plain words, one thing to get right before real people use what you built.

How to secure your AI app before you launch

4 minutes. Watch on YouTube

Last year, 29 million secret keys were leaked on GitHub, the most ever recorded in a single year. Keys for AI services went up 81%. Most weren't leaked by hackers. They were leaked by people building something, just like you.

The five checks

  1. Secret keys

    Open your code and search for the word "key". If you can see a key, so can everyone else. Keys belong in your server settings, never inside the app.

  2. Settings

    Many apps launch in test mode, with doors left open for the builder. Make sure test mode is off.

  3. Your data

    Change the number in a web address, say from /student/104 to /student/105. If a stranger can see someone else's details that way, your customers are exposed.

  4. The padlock

    Your app should always open with https and a padlock. Without it, anything typed can be read on the way.

  5. A way back

    If something breaks after launch, can you go back to the last version that worked? If not, don't launch yet.

Want a second pair of eyes? The free app safety check looks at any live app for leaked keys, exposed .env files and missing security settings, and tells you how to fix each one in plain English.

Numbers from GitGuardian's State of Secrets Sprawl 2026. Meera in the video is an example, not a real customer.

Hosting on Utplava? Your secret keys are kept encrypted in server settings, never in your app, and every app gets the https padlock. Put your app online free

How to avoid a huge AI or cloud bill after you launch

4 minutes. Watch on YouTube

A website with about 200 visitors a day got a $104,500 hosting bill. AI and cloud services charge like a taxi meter: every question, visitor and download adds to the fare. And on many platforms, a budget only sends you an email while the meter keeps running.

Five limits to set before you launch

  1. OpenAI

    Turn on a hard spend limit for your project, not just an alert. It can go slightly over before it kicks in, so set it a little below what you can afford.

  2. Google (Gemini and Firebase)

    A budget on its own only alerts you. Use a spend cap, which pauses the service when you reach it.

  3. Supabase

    Keep the spend cap on in your billing settings. Some add-ons aren't covered by it, so only add what you need.

  4. Your hosting

    Free plans usually pause at their limits. On a paid plan, set a spending limit so your app pauses instead of billing you.

  5. Everywhere

    Keep keys off your app, send billing alerts to an inbox you actually read, and look at your usage once a week.

Utplava's free plan needs no card, so there's no bill to run away. Put your app online free

Vercel vs Cloudflare: which is better for hosting?

4 minutes. Watch on YouTube

Half the internet says Vercel, the other half says Cloudflare, and both are right. The answer depends on two questions: what are you building, and is it making money?

The quick answer

Plan details from Vercel's and Cloudflare's own documentation, checked November 2026. Prices and limits change, so check before you decide.

Don't want to choose? Utplava puts your app online with its database set up, free for up to 3 apps. Try it free

How to host your Lovable app outside Lovable

3 minutes. Watch on YouTube

Want your own domain, worried about credits, or a client asking who owns the app? Your Lovable code is yours, and you can take it with you. The front of your app moves easily. The back, your database and sign-ins on Lovable Cloud, is where you need to be careful.

Four things that break when you move, and the fix

  1. Settings

    Your app needs settings such as your Supabase address and key, usually starting with VITE_. Your new host doesn't know them, so add them there.

  2. Page refresh

    Refreshing an inner page shows "not found". The host needs one rule so every page loads the app first.

  3. Sign-ins

    Add your new web address to the allowed addresses in your sign-in settings.

  4. Permissions

    If you moved your database to your own Supabase, sign in with a second account and make sure it can't see anyone else's data.

Lovable's documentation says there is no one-step move from Lovable Cloud to your own Supabase project, and that move is one-way. Lovable Cloud docs. There's also a written step-by-step guide.

Want it on its own link today? Utplava hosts Lovable apps, and you can add your own domain. Put your Lovable app online free

Is your Supabase data public? Row Level Security explained

3 minutes. Watch on YouTube

In 2025, a security researcher found more than 170 AI-built apps where anyone could read the database: names, emails, phone numbers, payment status, even API keys. No hacking was needed. The apps were missing one setting, Row Level Security.

Check and fix in a few minutes

  1. Table Editor

    Open your Supabase project. Tables without protection are clearly marked, often as "Unrestricted".

  2. Security Advisor

    It lists problems such as "RLS disabled in public", with a fix for each one.

  3. Ask your AI

    "Turn on Row Level Security for every table. Add rules so each signed-in user can only see and change their own data. Public things, like a menu, can be read by anyone, but only I can edit them."

  4. Test it

    Sign in with a second account and try to see someone else's data. You shouldn't be able to.

  5. Keep the secret key secret

    Never put the service role key in your website. And since 30 October 2026, new tables aren't opened to your app automatically: grant access, and turn on RLS for them too.

Sources: CVE-2025-48757 write-up, Supabase security retro 2025, Supabase changelog.

Checked your data? Then you're ready to launch. Put your app online free on Utplava

Turned on RLS and your app went blank? Part 2

3 minutes. Watch on YouTube

You switched on Row Level Security, and now your app shows nothing, or you see "new row violates row-level security policy". Your data isn't gone. With RLS on and no rules, nobody is allowed in, not even your own app. Each rule you add, called a policy, says who can get in and what they can do.

The fix

  1. Public tables: anyone can read

    For things like blog posts, products or a menu, add Supabase's "Enable read access to everyone" template. Visitors can read, nobody can change.

  2. Personal tables: only the owner

    For orders, notes or profiles, use "Allow users to only view their own data". Supabase matches the signed-in user's ID with the user ID on each row, so add a user_id column first if the table doesn't have one.

  3. Or ask your AI

    "Write Supabase RLS policies so each user can only see and edit their own rows in this table." Read what it wrote before you apply it.

  4. Never take the shortcut

    Don't switch RLS off, and never put the service role key in your app. That key skips every rule, and anyone who opens your website can find it. Run the Security Advisor when you're done.

Sources: Supabase docs: Row Level Security, Supabase docs: Advisors.

Rules in place? Then you're ready to launch. Put your app online free on Utplava

Users not getting your Supabase sign-up email? Part 3

3 minutes. Watch on YouTube

Sign-up works when you test it, then real users get no confirmation email, no password reset and no magic link. Supabase's built-in email sends only 2 emails an hour, and only to people on your own project team. It's meant for testing. For real users, connect your own email sender.

How to set it up

  1. Pick an email service

    Resend, Brevo, Postmark and Amazon SES all work, and most have a free plan that's plenty for a new app.

  2. Add your domain

    Emails then come from your own address, like no-reply@yourapp.com. Add the SPF, DKIM and DMARC records the service gives you, so emails land in the inbox, not spam.

  3. Connect it in Supabase

    In Authentication, open the SMTP settings, turn on custom SMTP, and paste the host, port, username and password, plus your sender email and name.

  4. Test with a stranger's address

    Sign up with a brand-new email that isn't on your Supabase team. Supabase now allows 30 emails an hour, and you can raise that in the rate limit settings.

Sources: Supabase docs: custom SMTP, Supabase docs: rate limits.

Emails working? Then you're ready to launch. Put your app online free on Utplava

Supabase "permission denied"? 4 errors and how to fix them. Part 4

5 minutes. Watch on YouTube

Your app worked yesterday and today it says "permission denied for table". You didn't break it. Supabase changed one rule: new tables are no longer open to your app automatically. That's one of four permission errors beginners hit, and each has a simple fix.

The four errors

  1. "permission denied for table"

    The table isn't shared with your app yet. Grant access to signed-in users (the authenticated role). For private data, don't follow the hint that suggests the anon role, which means anyone.

  2. "new row violates row-level security policy"

    Saving fails because no rule allows that row. Add an insert rule that checks the row belongs to the signed-in user.

  3. No error, just empty results

    No rule matches, so Supabase returns nothing instead of an error. Updates need a read rule too. And if nobody is signed in, the user ID is empty, so rules that check it match nothing.

  4. "infinite recursion detected in policy"

    A rule checks the same table it protects, so it keeps checking itself. Move that check into a separate function and call it from the rule.

One more thing: the Supabase dashboard and SQL editor skip these rules, so test from your app while signed in as a normal user.

Source: Supabase docs: row level security.

No more permission errors? Then you're ready to launch. Put your app online free on Utplava

Your AI app can spend money while you sleep. Set a hard limit

4 minutes. Watch on YouTube

If your app uses OpenAI or Claude, every message costs a little money. One bug that loops all night, or one leaked key, can run up a big bill by morning. A spend alert only emails you. A hard limit actually stops the spending.

Set it up

  1. OpenAI

    In your OpenAI dashboard, open the spend limit for your organization and type your monthly budget. Then switch on "Enforce a hard limit". Without that switch, the number is only an alert. Give each project its own limit too. The stop isn't instant, so set it a little below what you can afford.

  2. Claude Console

    Go to Settings, then Spend limits, and click Set limit. Once you reach it, requests are refused until the 1st of next month or until you raise it. Limits can also be set per workspace, but not on the Default workspace, so create a workspace for each app.

  3. Prepaid credit

    If auto top-up is on, your credit balance refills itself and stops working as a limit.

Rule of thumb: alert at half your budget, hard limit at the full budget. And make your app show a friendly message when the limit hits, instead of crashing.

Sources: OpenAI: spend limits, Claude docs: rate and spend limits.

Limits set? Then you're ready to launch. Put your app online free on Utplava

Put your app online

Step-by-step videos, each tested end to end before we published it.

Host a Lovable app on its own link From a Claude chat to a live app One sentence in Claude to a live website

Coming next

Deploy your app

What we can and can't see

Listed on awesome-remote-mcp-servers, the GitHub list developers use to find MCP servers for their AI assistants.