[email protected]

Have your Lovable app audited

You built your application with Lovable and want to know whether it can go live. We review code, data access and operations and attack a test instance. Confirmed findings come with proof. Every finding carries one of four states: confirmed, refuted, suspicion without confirmation, or not tested.

Reviews
Cloud Wolke HerausforderungServer NachhaltigkeitIT Beratung Service Consulting SoforthilfeTimo Wevelsiep Robin ZinsExperten für Innovation Migration AWSHetzner Hosting zuverlässig

Customers from mid-sized business, industry and the public sector, in Germany and internationally

  • Stadtwerke Brühl
  • DGHO e.V.
  • solarwerkstatt berlin
  • Krüger Dirndl
  • ABCO Water Systems
  • Golem.de
  • EVADXB
  • nextGYM
  • AInergy
  • ml&s
  • Odiseo Solutions
  • Annota
  • ARGE
  • SweetConnect GmbH
  • Aphy AG
  • CORGOS
  • Rekorder
  • SolidProof
  • Yonju
  • Keymate
  • Paritel
  • Mr. Clipart
  • Millenium
  • Negosh
  • Führerscheinmacher
  • BTI
  • Deutsche Gesellschaft für Datenschutz
Read client reviews

Audit focus

What we look at closely in Lovable apps

Lovable builds web apps on a fixed stack: older projects run as a React app with Vite in the browser, projects created since 13 May 2026 (since 22 June 2026 in Enterprise workspaces) on TanStack Start with server code. Data, sign-in and files sit in the built-in backend Lovable Cloud, which is based on the open-source foundation of Supabase, or in your own Supabase project. For a security audit this matters because the browser can send requests straight to the database. What a stranger can read or change there is decided mainly by the access rules (row level security) together with table grants, views, functions and keys.

  • Supabase Cloud dependency for auth, storage, realtime and edge functions
  • Unclear or missing row-level security rules
  • Secrets and environment variables without a clean deployment concept
  • SEO and AEO foundations such as rendering, metadata, sitemap, robots.txt and structured data

Lovable in detail

Lovable app security: what we check in practice

Lovable ships its own security scans and names the app owner as responsible for the app's security. We read their results alongside our own review of database, server code, repository and operations (state of the vendor documentation: November 2026).

01

Database, RLS and keys

  • Row level security and table grants for anon and authenticated on every table, including tables that were only added later by prompt
  • Policies that give every visitor access, views that bypass RLS by default, and permissions based on user_metadata
  • Secret key (service_role) in the frontend, in the repository or in the git history
  • Legacy anon and service_role keys: Supabase is deprecating them by the end of 2026, and creating new keys does not switch the old ones off
The public key in the browser is meant to be there, so the protection of the data rests on the rules behind it: row level security, table grants, views and functions.

02

Edge functions and server code

  • Sign-in and permission checks in every edge function and every server route
  • Functions that use service_role, bypass RLS and therefore have to limit access themselves
  • JWT verification (verify_jwt) on functions that users call, and functions that answer without sign-in
  • Credentials in the secrets area instead of variables with a VITE_ prefix that reach the browser
Code on the server is not private by default, so every call has to establish who is asking and what they may do.

03

Built-in scans and operations

  • Quick scan (runs on every publish) and deep scan (does not run automatically while you work, scheduled on the Enterprise plan): which findings are open, which were ignored?
  • Dependencies: the quick scan only reports critical vulnerabilities, high and medium ones appear in the list only
  • GitHub sync of one branch, and a code export that leaves out database contents and uploaded files
  • Visibility of the published app and the workspace setting that blocks publishing with critical findings
We place the results of the Lovable scans in context and check what repository, publishing and operations require on top.

Audit levels

Three audit levels, bookable separately

The audit says what has to be fixed before launch. The pentest proves what can be exploited. Continuous review accompanies changes during operation within the agreed scope.

01

Production Readiness Audit

  • Code, configuration, data access and operational readiness
  • Split: fix before launch or later
  • Action plan in order of priority
from €1,490 excl. VAT

02

Pentest

  • Attack on a test instance, with insight into the source code
  • Confirmed findings with proof, every finding with a status
from €1,000

03

AI Code Review

  • Review of changes during operation, within the agreed scope
  • You keep developing with AI tools
  • Fixed monthly price
from €990 excl. VAT / month

Process

From handover to operations

You can keep developing the application yourself with AI. We audit, fix on request and take over operations.

  1. 01

    Handover

    Repository, test instance and test accounts per role. We verify that the application belongs to you.

  2. 02

    Audit

    Audit of code and operations, on request a pentest against the test instance. Your production system stays untouched.

  3. 03

    Report

    Findings with proof, severity and remediation, plus a clear order.

  4. 04

    Fix and operate

    We fix the findings in the code and take over hosting and operations if you wish.

Frequently asked questions about auditing Lovable apps

Answers to the most important questions

Reviews & projects

Software projects with reliable outcomes

Proof for modernization, API extension, architecture, deployment and ongoing operations.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.

Selected projects

Read client reviews

Enquiry

Have your Lovable app audited

Describe the application, the tool and the current state. You speak directly with the people who are technically responsible.

  • You speak directly with Timo and Robin, who are technically responsible
  • A professional assessment of your situation
  • Concrete next steps for infrastructure, software or AI

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
Timo and Robin, founders of WZ-IT

What should happen next?

Choose the appropriate starting point for the current product stage.

We usually respond within one business day. Please do not send access credentials yet.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH