[email protected]

Have your Supabase security checked

Supabase provides database, sign-in and API. Whether one account can read the data of another depends on policies, table grants, views, functions and keys. We review them in the code and prove the result on a test instance.

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 check in a Supabase backend

Supabase provides sign-in, file storage, edge functions and an automatically generated data API on top of a Postgres database. The API is meant to be called from the browser: the publishable key (formerly the anon key) sits in the frontend, and what a request can reach with it is decided by table grants and row level security. The built-in backend of Lovable is based on the open-source foundation of Supabase, and Bolt runs its database check with the checks of the Supabase Security Advisor. A security audit therefore looks not at the key but at the rules, grants, functions and settings behind it.

  • Row level security: is it enabled on every table, and what do the policies really allow?
  • Keys: is the service_role key anywhere in the frontend, the repository or an unprotected edge function?
  • Access between accounts and tenants through the auto-generated API
  • Storage buckets, edge functions and database functions with elevated rights

Supabase in detail

Auditing Supabase security: what we look at

Supabase describes security as a shared responsibility: access management, data and applying security controls rest with the operator, and so does acting on the recommendations of the Security Advisor (state of the vendor documentation: November 2026). We read policies, grants, views, functions and settings in context and check on a test instance what an account can actually reach.

01

Row level security, grants and views

  • Tables without RLS in a schema that the data API exposes: any role with a grant can read and write them
  • Grants for anon and authenticated: on projects that grant privileges automatically, a new table in public receives all privileges, and policies do not take them back
  • Policies with the condition true, policies without a role and checks on user_metadata, which signed-in users can change themselves
  • Views that bypass RLS because they are usually created as the postgres user, and security definer functions in schemas that the data API exposes
Two checks run before every access to a table: grants decide whether a role may perform the operation, policies decide which rows it applies to.

02

Keys, edge functions and storage

  • The secret key (formerly service_role) in the frontend, in the repository or in the git history; a key found there is rotated once the cause is fixed
  • Legacy keys anon and service_role: they stay valid until they are disabled in the dashboard, and Supabase is deprecating them by the end of 2026
  • Edge functions: verify_jwt is on by default. Where it is switched off, the function has to check the caller itself, and a handler using supabaseAdmin without a filter on the user ID returns the rows of all users
  • Storage: buckets are private by default, in public buckets anyone with the URL can reach the file, and policies on storage.objects govern upload and listing
The publishable key is meant to be published, while the secret key bypasses RLS and belongs only in code that you control.

03

Auth, realtime and settings

  • Auth: email confirmation enabled, one-time codes and links expiring after at most 3600 seconds, test phone numbers removed, leaked password protection from the Pro plan
  • Site URL and redirect URLs: the site URL points to the production address instead of localhost, and redirect URLs in production are exact paths instead of wildcards
  • Anonymous sign-ins: anonymous users use the role authenticated, so existing policies have to tell them apart by the claim is_anonymous
  • Realtime and operations: RLS does not filter Postgres Changes DELETE events, and SSL enforcement, network restrictions and MFA for the organization come on top
The production checklist of Supabase names the settings that should be right before launch. We go through them one by one.
Sources, as of November 2026: Vendor documentation Supabase: Row Level Security (grants, policies, views, security definer, user_metadata, tests), as of 19 Nov 2026, Vendor documentation Supabase: Securing your API (grants, default privileges, data API), as of 19 Nov 2026, Vendor documentation Supabase: API keys (publishable, secret, legacy keys, rotation, limits), as of 19 Nov 2026, Vendor documentation Supabase: Securing Edge Functions (auth modes, supabaseAdmin), as of 19 Nov 2026, Vendor documentation Supabase: Authorization headers (verify_jwt), as of 19 Nov 2026, Vendor documentation Supabase: Storage Buckets (private, public), as of 19 Nov 2026, Vendor documentation Supabase: Storage Access Control (policies on storage.objects), as of 19 Nov 2026, Vendor documentation Supabase: Advisors (Security Advisor, list of checks), as of 19 Nov 2026, Vendor documentation Supabase: Production security checklist (Auth, Realtime, SSL, network restrictions, MFA), as of 19 Nov 2026, Vendor documentation Supabase: Password security (leaked password protection, Pro plan), as of 19 Nov 2026, Vendor documentation Supabase: Redirect URLs (site URL, wildcards), as of 19 Nov 2026, Vendor documentation Supabase: Anonymous Sign-Ins (role authenticated, is_anonymous), as of 19 Nov 2026, Vendor documentation Supabase: Shared responsibility model, as of 19 Nov 2026, Vendor documentation Supabase: Self-Hosting (responsibility, missing platform features, local stack), as of 19 Nov 2026, Vendor documentation Supabase: Self-Hosting with Docker (HTTP, reverse proxy, Studio password, services), as of 19 Nov 2026, Vendor documentation Lovable: Built-in backend (Supabase foundation), as of 19 Nov 2026, Vendor documentation Bolt: Database security (checks of the Supabase Security Advisor), as of 19 Nov 2026

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 AI-generated 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 AI-generated 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