Backend context with the project plan
Keep the linked Supabase project discoverable beside product requirements, delivery tasks, owners, and meetings rather than relying on a separate list of infrastructure URLs.
What you can do
Connect customer-owned Supabase projects to Kato with read-only OAuth access. Link a Supabase project to a record to see safe project metadata, database health, Edge Functions, storage, and environment context without exposing project credentials or customer table rows.
Shared operational visibility
Give engineering and project stakeholders a common starting point for understanding project health while detailed administration remains in Supabase.
Authorized project selection
Use Supabase authorization and link the intended project to the Kato record, preserving Supabase as the authority for account and resource permissions.
Connect Supabase
Kato uses a platform Supabase OAuth app with PKCE and read-only Management API scopes. An owner or admin authorizes access, selects projects, and chooses which Kato object types should receive the Supabase Project field. Kato proxies permitted project metadata to workspace members while keeping OAuth credentials encrypted on the server.
- 01In Kato, go to Settings → Integrations → Supabase and click Connect.
- 02Authorize Kato's read-only access to your Supabase organizations and projects.
- 03Choose the Supabase projects and Kato object types you want to track.
- 04Link the Supabase Project field on a record to see project health and development context.
Made for your workflow
Project setup documentation
Link the correct Supabase project when a Kato project begins so new teammates can identify the backend environment associated with the work.
Operational reviews
Review available project and resource status before a planning meeting, then create explicit Kato tasks for anything requiring deeper Supabase administration.
Cross-functional handoff
Let non-admin stakeholders see useful backend context while engineers continue to use Supabase directly for database, authentication, storage, and function changes.
Common questions
Does Kato administer the Supabase database?
No. Supabase remains the control plane and data system. Kato presents supported project context and coordinates work associated with the linked backend.
Can a Kato project link to a Supabase project?
Yes. Authorize the connection, then select the appropriate Supabase project from the Kato project record so future views use the correct environment.
What if a project is not available to select?
Confirm that the connected Supabase account can access the organization and project. Kato cannot present resources that the authorized account is not permitted to view.
Last updated Jul 16, 2026