Supabase Studio is a project management interface. Its public fingerprint can be small while the authority behind the project is substantial. A developer uses Studio to inspect tables, policies, functions, storage, and authentication settings. A mistake in project keys or network access can expose more than the Studio page itself.

A count-only ZoomEye run on 2026-11-21 measured app="Supabase Studio" at 367 index matches. The exact title query returned six. Both observations used sub_type=all, page 1, and page size 1. The very small title count shows why a single query should not be treated as the whole population. These are index records, not a count of vulnerable Supabase projects.

Supabase documentation separates publishable and secret project keys. A publishable key is designed for clients and reaches data through roles and Row Level Security. A secret key can map to the service_role and bypass Row Level Security. The documentation warns that a secret key exposes project data if leaked. That makes key handling the main verification item when an owner finds a public Studio-like surface or a project URL in inventory.

A modern deployment may also be migrating from the legacy anon and service_role JWTs to publishable and secret keys. Both key systems can coexist while the migration is in progress. An inventory that recognizes only one format can miss live credentials. Check the project's documented key state from an authorized administration session. Do not search public code for keys and then use them to test data access.

The public Studio URL and the data API URL are different surfaces. The Studio needs an authenticated owner or administrator session. The data API needs a project key and, when a user is signed in, a user access token. Keep the Studio on a private management network or behind an identity-aware proxy where possible. Restrict who can create secret keys. Log key creation and deletion. Give each workload its own key and use the server side only.

A practical review starts with an inventory of environment variables and build outputs. Confirm that browser bundles contain only publishable keys. Search CI configuration for secret names, not secret values. Check server functions and jobs for service-role use, then verify that those services perform their own authorization before acting on a user request. RLS protects database queries, but it does not protect a server endpoint that accepts an arbitrary table name and forwards it with a secret key.

The ZoomEye count is best used as an exposure lead. It tells the owner that Studio-shaped pages and project management patterns are measurable in the index. The owner can then reconcile the count with DNS, certificate records, cloud projects, and repository deployment manifests. Do not attach a count to a named customer or claim compromise.

Studio is a management UI with a focused fingerprint. The key model and the server-side authorization behind it determine the real risk.

Exact query: app="Supabase Studio"

Open the normalized ZoomEye search

References