AI App Builder Audits · AI Development Series
Appsmith App Audit
Appsmith keeps your data inside your own network, which is a genuine advantage. It also hands you a server to look after.
What Appsmith actually hands you
Appsmith is one of the most widely adopted open-source internal tool builders. The important structural difference from a cloud platform is that you can run it yourself, so your production data never leaves your network.
What a Appsmith application is made of
- Interface React components, assembled visually
- Data sources Your own Postgres, MySQL, MongoDB, REST or GraphQL
- Queries SQL and API calls defined in the platform
- Logic JavaScript, in event handlers and transformers
- Access Role-based permissions; SSO on paid tiers
- Hosting Self-hosted via Docker or Kubernetes, or Appsmith cloud
Self-hosting genuinely changes your compliance position for the better: the data path never leaves infrastructure you control. It also transfers a set of responsibilities that a cloud platform was quietly handling — keeping the software patched, controlling who can reach the instance, and making sure it is not accidentally facing the public internet.
Everything else follows the same pattern as any internal tool: a privileged connection to production, permissions enforced above the database rather than in it, and logic scattered across event handlers.
What we consistently find
These are the recurring issues, and the last one is specific to self-hosted deployments.
Permissions that hide controls rather than block queries
Roles typically govern what a user sees. Whether the underlying query is still reachable by someone signed in who knows it exists is a separate question, and it is the one that matters.
If the only thing stopping a viewer deleting a record is that the button is not drawn, that is presentation rather than protection.
What it costs you: staff reaching actions they were never granted.User input concatenated into queries
Filters and search boxes built by dropping input directly into query text are quick to build and are the standard route to SQL injection — here, from inside your own admin tool against production.
Prepared statements solve it entirely and the platform supports them.
What it costs you: SQL injection against your production database.An instance reachable from more places than intended
Self-hosted deployments frequently end up exposed to the public internet rather than restricted to an internal network or VPN, usually because that was the quickest way to let people use it from home.
That turns a tool with privileged database access into something anyone can attempt to sign in to. Add unpatched versions, and it becomes the most attractive target you run.
What it costs you: a privileged, internet-facing entry point into your production data.Business rules with no review and no tests
Logic accumulates in JavaScript attached to individual components. Each snippet is sensible on its own; together they become the part nobody can explain.
There is no code review, no tests and often no meaningful version history, so when the person who built it moves on the tool becomes something everyone is wary of.
What it costs you: a critical tool only one person understood, and now nobody does.Where Appsmith is genuinely good
For teams that need internal tooling without sending production data to a third party, Appsmith is a strong answer. It is open source, genuinely self-hostable, and it saves the months of pointless work that building admin panels by hand represents.
Genuinely well suited to
- Internal tools where data must stay inside your network
- Teams with the DevOps capacity to run and patch it
- Admin panels and operational dashboards
- Organisations with data residency or compliance constraints
- Replacing spreadsheets and direct database access
Where it needs engineering behind it
- Anything customer-facing or reachable from outside the organisation
- Tools performing bulk or irreversible actions on live data
- Regulated processes needing a defensible audit trail
- Deployments nobody is actively patching
- Logic complex enough to deserve review and tests
The honest summary: Appsmith gives you control, and control is a responsibility as much as a benefit. The tooling questions are the same as any internal builder; the difference is that the server it runs on is now yours to secure.
Prefer to watch? The short version of who we are and how we work
Do you need an audit?
Get it looked at if
- It can write to, or delete from, your production database
- The instance is reachable from outside your network
- You are not certain when it was last updated
- It touches personal data, payroll, pricing or payments
- The person who built it has left, or is about to
You are probably fine if
- It is read-only over data nobody would mind seeing
- It runs on an internal network with a couple of trusted users
- It is a dashboard rather than a tool that changes things
- Everything it touches is easy to reconstruct
Questions about auditing a Appsmith build
Self-hosting protects where the data sits, not who can reach it. What we find is permissions that hide controls rather than block queries, and user input pasted straight into SQL, which lets a value typed into a search box change what the query does.
It is open source, self-hostable and used for real internal tooling, all of which is fine. The exposure comes from what it connects to. An internal tool wired into production data with broad rights is a serious thing whoever is hosting it.
Yes, wherever queries are built by joining text and user input together. Appsmith supports prepared statements, which remove the problem entirely, but generated and hand-built queries often concatenate instead. It is one of the first things we check and one of the easiest to fix.
Where role permissions only govern which widgets appear, yes. The query remains executable by anyone who can reach it. Restricting the interface and restricting the data are separate jobs, and only the second one actually restricts anything.
It removes a third party from the picture, which is worth something, and it makes everything else your responsibility. In practice, self-hosted instances are the ones we find reachable from further afield than intended and running behind on updates, because nobody owns that job.
They can, once queries are parameterised, permissions are enforced at the data layer and the instance is properly bounded. What tends to fail a review is not the tooling but the absence of any review before it: business rules built ad hoc, with no tests and nobody having checked them.
Parameterising queries and scoping connections is quick work with a large payoff. Hardening the deployment is usually straightforward too. The audit is £495 + VAT and covers the app and the instance together. Credited back in full if we then do the work.
On data residency, yes, genuinely, and it is a real advantage if you have compliance obligations. What it does not do is make the tool itself safer. You have taken on patching, network exposure and access control for the instance, and an out-of-date Appsmith server reachable from the internet with a privileged database connection is a worse position than a well-configured cloud tenancy.
Read access to the applications so we can see queries, JavaScript and role configuration, the database schema and details of the credentials it connects with, plus how the instance is deployed and who can reach it. We do not need write access and we will not change anything.
No, and we would rather say so plainly than pretend otherwise. We build with Claude Code and Cursor, with senior developers designing the system, reviewing every change and testing it. What makes us useful here is not Appsmith expertise, it is that the thing being audited is SQL, a permission model, a production database and a deployment, which is what we have been working with for years.
Built with something else?
We audit what these tools produce, whichever one you used.
Other AI app builders
- Lovable app audit
- Emergent app audit
- Replit app audit
- UI Bakery app audit
- Bolt app audit
- v0 app audit
- Base44 app audit
- Firebase Studio app audit
- Databutton app audit
- Rork app audit
- a0.dev app audit
- FlutterFlow app audit
- Bubble app audit
- Glide app audit
- Softr app audit
- Adalo app audit
- Retool app audit
- Budibase app audit
- ToolJet app audit
- Xano app audit
- Airtable app audit
The audit
Find out what you are sitting on
The AI Code Audit is £495, fixed.
Tell us roughly what you built and how many people use it. If an audit is not the right thing for you, we will say so.
What the report covers:
- The query layer, including how user input reaches your database
- Whether your permission model is enforced or merely displayed
- What the tool can do to production data, and what is recorded
- How your self-hosted instance is deployed, exposed and patched
We reply within one working day.
