Base44 builds a React app with its own database, login and hosting from a prompt, so there is nothing to connect and nothing to deploy. Every record your app stores lives in an entity, and each entity has security rules that decide who can read and change it.
I read the code, the entity rules and the backend functions as one system. You get a ranked list of what to fix, in plain English, with a fix prompt you can paste straight back into Base44.
1Line 6: This runs in the browser with the signed-in user's permissions; if the Order entity's read rule is true, every customer gets every order, whatever the page shows.
Common problems in Base44 apps
Not every app has all of these. The report tells you which ones yours has, where, and what to do about each.
Critical
Entities every user can read
An entity whose read rule is true gives every signed-in user every record. The Base44 SDK runs in the browser, so the rules are the only thing between a curious user and the whole table. I read every rule and say what it lets each kind of user see.
Critical
Checks done in the page instead of the rules
An admin page that checks the role in React and then lists the entity. The list call works from the browser console for anyone, with or without the page. I list every rule that has to move from the page into the entity.
High
Backend functions that run as the service role
A function using the service role bypasses the entity rules entirely, and Base44 leaves the access checks to the function itself. One that takes a user id from the request body and trusts it is a public endpoint for everyone. I check each function for what it verifies before it acts.
High
Private fields on public entities
A cost price, an internal note or an admin flag on an entity that customers can read. Base44 supports rules per field, so the fix is small. I find each field that should not leave the server.
Medium
Create rules that say who, not what
A create rule decides who may add a record, not what it may contain. A user who may create an order can create one with status paid and total zero if the page is the only thing setting those values. I say which fields have to be set by a backend function instead.
Low
Whole entities fetched and filtered in React
Pages that list every record and filter in the browser. Slow once the table grows, and every record sent to the browser is one the user can see in the network tab. The fix moves the filter into the query.
Treatment plan
How it works
1
Book a check-up
Choose a tier and tell me where to send the report. Add your app's address if it is live. Two minutes, no sales call.
2
Show me your code
Pay by card, then give me read-only access to your code on GitHub (you paste in a key I send you) and let me into your app with test accounts. Never done that? I send you step-by-step instructions for your tool. I measure your app and confirm it fits before I start.
3
Get your diagnosis
Ready to launch, or not yet. Problems ranked, critical ones proven on your live app, each with a prescription for your AI tool. A PDF by email, then 7 to 30 days of questions by email.
4
Fix it, then a free follow-up
Fix the problems yourself, with your AI, or let me do it with the Fix Pack. Tell me within 30 days and I check once more that they are really gone.
No idea how big your app is? That’s normal, and you never have to count anything. Book the review you want; I measure your app before I start and tell you. If it doesn’t fit, you choose: upgrade, narrow it down, or a full refund. “Lines of your code” means the code you and your AI wrote, not the packages and UI kit your tool installed; many apps built with Lovable, Bolt or v0 fit the Safety Scan.
Start small, upgrade later. The Safety Scan’s price counts in full toward a Launch Review or Fix Pack for the same app within 30 days of your report.
Why this price? Software does the first pass, so you pay for the part only a person can do: checking every finding in your code, proving the critical ones and deciding what matters for your app. I take at most 3 Safety Scans and 2 Launch Reviews (or one Fix Pack) a week; if this week is full, yours starts the next.
Prices in US dollars, paid once, no sales call and no surprise invoice: anything extra is your choice, told to you before I start. The clock starts when I can see your code. Reports arrive as a PDF by email, in English, or German if you prefer.
Need a few things fixed after a scan? I fix by the hour at $199, three hours minimum, with the list agreed before I start.
Bigger than 50k lines, or a real mess? Rescue jobs are quoted, from $3,000, no obligation. Email me.
Not for you if
you have a team of engineers who already review each other’s code,
your app’s backend isn’t JavaScript or TypeScript (Python Replit apps, for example), or it is over 100k lines,
you handle regulated data (health records, banking, children), or need a pentest, certificate or compliance sign-off. Taking card payments through Stripe is fine.
A review lowers your risk a lot. It can’t guarantee that your app is secure, and nobody honest will say otherwise.
Base44 questions
How do I get my Base44 app to you?
Connect the app to GitHub from Base44 and give me read-only access to the repository (I send you a key to paste in). Entities and their security rules stay in Base44, so I also need those; a screenshot of each table's security settings is enough.
Base44 already warns me about security rules. Is that enough?
It is a good start. Base44 flags rules that look risky and offers a fix. I check what that leaves open: rules that are allowed but wrong for your app, backend functions that bypass them, and pages that rely on them without knowing it. Critical findings are proven against your live app with test accounts.
Can I fix things inside Base44?
Yes. Each finding comes with a fix prompt written for Base44. For security rules I also give you the rule itself, so you can read it before it goes live, and I re-check the problems from your report once, free, within 30 days.
Why not just ask my AI to review it?
Do, and I will even give you the prompt. You will get a long list. What your AI cannot do is tell you which items are real, prove them against your live app, see your database and hosting settings, or check that its own fixes worked. If you cannot read code, that is the part you cannot do yourself either. It is what you pay me for.
I'm not a developer. Is this for me?
Yes, that is exactly who it is for. If you built an app with AI and cannot tell whether the code is any good, I check it and explain what matters in plain English. You never need to understand the code to act on the report: every problem comes with a prompt you paste into your AI tool. And you do not need to know what to ask. The report answers the questions you would have asked if you knew how.
How do I show you my code?
Most AI builders can push your app to GitHub, a free site that stores code. You give me read-only access by pasting a key I send you into your repository settings, which means I can look but not change anything. Never done it? After you book, I send you step-by-step instructions for your tool. A zip file works too. When the report is delivered, remove my access again; I remind you.
Is my code safe with you?
Every booking comes with an NDA, automatically. I never sell, publish or pass on your code. The only other party that sees it is the AI provider that helps with the first pass, under terms that do not allow it to train on your code. I never need your passwords or your live database, and I delete my copy within 7 days of delivering the final report.
From $149 for the first 10 customers (10 left). Ready within 2 business days. If the Safety Scan finds no problem rated medium or worse, you pay nothing.