Skip to content
HARDEX

Guide

How to check if your Bolt app is secure

Bolt can turn a prompt into a working app, with a database and sign-in, in an afternoon. What it builds is real software that real visitors can reach, so it is worth a look from the outside before you share it.

Bolt's documentation describes a security check for its databases, and it is worth using. This is the second look: four things to check on what is actually live, each with a way to check it yourself and what to do. You do not need to be a developer.

1Bolt's own database security check

Bolt can create a database for your app or connect one you own in Supabase. Its documentation describes a Security tab for the database that runs the same checks as Supabase's security advisor, and it suggests checking again after any change to the database. Those checks find common mistakes. They cannot know what you meant to keep private.

Check it yourself: Open the Security tab of your project's database and read every item it lists, not only the red ones. Run it again after you add or change a table.

What to do: Fix what it lists. If Bolt offers an “Ask Bolt to fix” button, use it, then read the list again to see that the item is gone. Treat a clean list as a good start, not as proof.

2The two-account test

An app can pass every automatic check and still show one person's records to another. The only way to know is to try it as two different people.

Check it yourself: Create two accounts with two different email addresses. With the first, add something private: an order, a note, a file. Then sign in as the second and look for it everywhere: in the app, and by changing the number or name in the address of a page that shows a record.

What to do: If the second account can see or change the first one's records, ask Bolt: “Make every table readable and changeable only by the signed-in user who owns the row, and show me what you changed.” Then repeat the test.

3Keys in the pages everyone downloads

Bolt apps read their connection values, such as the database address, from environment variables when they run. Whatever the page code needs in the browser is sent to every visitor. A public key, such as the one that lets the app talk to the database, is meant to be there. An admin key, a payment key or an AI service key is not.

Check it yourself: Open your live app and press F12. In Chrome, go to the Sources or Network tab and search the files for words like key, secret, token and sk-.

What to do: Move any private key to a server function and keep it where your host stores secret settings. Then create a new key and delete the old one, because anyone who saw the old one can still use it.

4Who can sign up

Sign-in decides who gets past the front door. If anyone can create an account without confirming an email address, anyone can fill your app with accounts, or sign up with someone else's address. For a public app that can be fine, but it should be your choice.

Check it yourself: Try to create an account with a made-up address and see whether the app lets you in without a confirmation email.

What to do: Turn on email confirmation if your app is for a limited group of people, and switch off the sign-in methods you do not use.

What a check can and cannot tell you

Passing these checks does not prove an app is safe. It means these problems were not found. A full review also looks at how your app handles each person's data, and that takes someone who reads the code or tries to get past the sign-in.

Check them all from the outside

Hardex scans a live app the way a stranger on the internet would, with nothing to install. By default it only reads: it never changes anything in your app. It looks for the problems above where they apply to your app, and more, then reports what it found.

What each plan includes is on the plans page.

Scan your app

Hardex is an independent product made by AryonX. Bolt and Supabase are named here only to say what this guide is about.