ADR 0007 — Separate Supabase account, CLI-managed project

• Status: Accepted
• Date: 2026-07-13

Context

The primary Supabase account had reached its free-tier limit of two active projects. To create the Kredal project without pausing unrelated work, a different Supabase account was used. The Supabase MCP tool is authenticated to the original account and therefore cannot see or manage the Kredal project.

Decision

Create and manage the live Kredal project (cbrnyfninzpsspwygvnd, region ap-south-1) with the Supabase CLI, which is logged into the owning account and linked in kredal-app/. Use the CLI for all schema pushes, key retrieval, and inspection.

Consequences

• Positive: unblocked project creation on a fresh free tier; reproducible CLI-based ops.
• Negative: the MCP tool returns permission errors for this project — do not reach for it. This is documented in Apply DB migrations and the agent notes. If the accounts are later consolidated, revisit this.