Fixed-price audit
An audit for apps built with AI tools
Your app was built with Lovable, Bolt, Cursor, Replit or v0. It has users, revenue or a deadline, and now you are not sure whether the data is safe, whether it will hold up, or why App Review keeps sending it back. The audit answers that with a ranked list of fixes: 900 USD, report in 5 business days.
A good fit if
- The app is live, or about to be, with real users or paying customers.
- You have a date to hit: a launch, a client handover, a demo.
- You are stuck on data security, stability, or an App Store rejection.
- You want to know what to fix first, not a rewrite pitch.
Probably not yet if
- You are still prototyping, with no users and no deadline.
- You need a formal penetration test or a compliance certificate. This is a code and configuration review, not either of those.
In that case, start with the free guides.
What gets checked
Three areas. Mobile apps get all three; web apps skip the App Store part.
Data security
Whether a stranger with your public app URL can read or change data they should not see.
- Supabase Row Level Security: which tables are exposed, which policies are missing, and which ones let every signed-in user see every row
- Keys in client code: service role or secret keys in the bundle, the repo or environment files that ship to the browser
- Auth: sign-up and password reset flows, redirect URLs, session handling, admin and role checks done only in the UI
- Storage: public buckets, listable files, upload policies that let one user overwrite another user's files
- Views and database functions that bypass RLS
Production readiness
Whether the app survives real users, real data and the first bad day.
- Error handling and logging: what happens when a request fails, and whether you would know about it
- Data model: constraints, indexes on the queries the app actually runs, migrations kept in the repo
- Backups and restore: what your plan includes and whether a restore has ever been tried
- Costs: usage that grows with every user (polling, unbounded queries, AI calls without limits)
- Secrets and environments: where keys live, whether staging and production are separated
App Store readiness
For mobile apps: what App Review is likely to reject and what to change before you submit (or resubmit).
- App Review Guidelines risk: minimum functionality (4.2), spam (4.3), sign-in options (4.8), in-app purchase (3.1.1)
- Account requirements: in-app account deletion, demo account for the reviewer, Sign in with Apple when needed
- Privacy: privacy policy, App Privacy answers, purpose strings, disclosure of data sent to third-party AI
- Build setup: bundled web assets versus a remote URL, deep links for auth, push notifications
- Your developer account: individual versus organization, and what that means for the seller name
What you get
A written report. This is the table of contents of a typical one:
- Summary for the owner. One page, no jargon: what is at risk today, what to fix first, rough effort for each item.
- Ranked list of fixes. Every finding with severity, the evidence (query, request or file and line), and the concrete change that closes it.
- Data security findings. Table by table: RLS status, policies, grants, storage buckets, keys found in client code.
- Production readiness findings. Errors and logging, data model, backups, costs, environments.
- App Store readiness findings. Mobile only: guideline-by-guideline risk and what to change before submitting.
- What we did not check. The limits of the audit, stated plainly, so nothing is assumed to be covered when it was not.
- Fix plan. What you can fix yourself with your AI tool (with prompts), what needs a developer, and in which order.
Price and terms
Fixed price
900 USD
One price, agreed before work starts. No hourly billing.
Launch offer
500 USD
For the first 3 audits, in exchange for a public review once the audit is finished. An honest one - whatever you think of it.
The review mentions that you paid the reduced launch price, and is published on LinkedIn or on the Appience site - not on review platforms that forbid reviews given in exchange for a discount.
- Timing
- 5 business daysFrom the moment access to the code and backend is in place.
- Credit
- 100% of the priceCounts toward a fix sprint ordered within 60 days of the report. Fix sprints start at 2,500 USD.
How it works
- 01
Send a short brief
Through the contact form: the app URL, which tool built it, what it runs on, and what worries you. Mention a rejection message or a deadline if there is one.
- 02
Confirm scope and access
We reply with the scope, the price and the access we need - usually read access to the repository and an invite to the backend project. We never ask for your passwords.
- 03
Audit
The report arrives within 5 business days once access is in place. Checks are read-only: nothing is changed in your project or your data.
- 04
Fix it your way
Fix it yourself, with your own developer, or book a fix sprint with us. The full audit price counts toward a sprint ordered within 60 days.
Not sure yet? Check one thing for free
The self-check looks for Supabase keys that should never reach the browser and, from a query you run in your own SQL Editor, for tables without Row Level Security or with wide-open rules. It is a first signal, not an audit.
Free guides
The most common problems, with the checks you can run yourself.
Frequently asked questions
- Who does the audit?
- Appience is a small senior product team in Warsaw. Audits are led by Jan Lipmann, who has 16+ years of iOS development, including fintech work (RSA, JWT, PassKit), and builds with Supabase and Next.js.
- Is this a penetration test or a security certification?
- No. It is a review of your code, database configuration and setup, with read-only checks of what your public app exposes. It finds the common, expensive mistakes in AI-built apps and tells you how to fix them. It is not a certification, and the report says explicitly what was not checked.
- My app was built with Bolt, Cursor, Replit or v0, not Lovable. Does that matter?
- No. The tool matters less than what it produced. The audit is built around the stack these tools usually generate: a React or Next.js front end with Supabase behind it. If your backend is something else, say so in the brief and we will tell you upfront whether the audit fits.
- Do you change anything in my project during the audit?
- No. Access is read-only and the checks do not modify data. Fixes happen afterwards, by you or in a separate fix sprint.
- What does the launch offer involve?
- The first three audits cost 500 USD instead of 900 USD. In exchange, after the audit is finished, you publish an honest review of it - whatever you thought of it. The review mentions that you paid the reduced launch price, and it goes on LinkedIn or on the Appience site, not on review platforms that forbid reviews given in exchange for a discount.
- How does the credit toward a fix sprint work?
- If you order a fix sprint within 60 days of receiving the report, the full price you paid for the audit is deducted from the sprint. Fix sprints start at 2,500 USD.
- My app was rejected by App Review. Can the audit help?
- Yes, if it is an iOS app. Send the rejection text with the brief. The App Store part of the audit maps the rejection to the guideline Apple cited and lists what to change before you reply or resubmit.
Request an audit
Use the contact form and write “Audit” in the brief, with your app's URL, the tool that built it, what it runs on, and what worries you. Paste the App Review message if you have one. You get a reply within 24 hours.