Deployment URL or Custom Domain: N/A - Project already deleted from Vercel
Environment (local, preview, production): N/A - Project deleted
Project Framework: Next.js (based on template used: vercel.com/templates/next.js/supabase)
Build Settings:
Framework Preset: Next.js
Build Command (if not default): N/A
Output Directory (if not default): N/A
Install Command (if not default): N/A
Node/Runtime Version: N/A
Package Manager: N/A
Relevant Packages: Supabase
Current behavior:
- Unable to delete Supabase database after deleting the associated Vercel project
- Supabase UI redirects to Vercel Marketplace for deletion
- Vercel Marketplace deletion attempt results in “Unable to delete the Database” error
- Database remains active in Supabase but cannot be managed through normal means
Expected behavior:
- Deleting the Vercel project that created the Supabase (and other) resource should automatically delete the Supabase resources. Barring automatic resource deletion, it should be able to delete the Supabase database either through Supabase UI or Vercel Marketplace
- Alternatively, clear instructions on how to delete an orphaned Supabase database after Vercel project deletion
Steps to reproduce:
- Create project using Supabase Starter – Vercel template
- Delete the Vercel project
- Attempt to delete Supabase database through Supabase UI
- Get redirected to Vercel Marketplace
- Attempt deletion through Vercel Marketplace
- Receive “Unable to delete the Database” error
Additional context:
This appears to be an edge case where the database management is locked to Vercel Marketplace integration, but the deletion flow breaks when the associated Vercel project is deleted first. This creates an orphaned database that cannot be deleted through either platform’s standard interfaces.
Kind regards