📣 PSA: Supabase *isn't* going to keep supporting our existing projects

,
1

Re prior comms from Fly:

Existing databases will continue to work and be supported by Supabase.

This is inaccurate. You must take action before March 14th or your project is getting nuked from Supabase’s platform.

Here’s the full email I received from Supabase:

Important: Fly Postgres Deprecation Notice

Hello,

Supabase is deprecating Fly’s Postgres offering managed by Supabase on March 14, 2025.

Why are we deprecating this offering?

We are deeply committed to building the best Postgres development platform for our customers. Postgres is, and will always be, fundamental to our business.

This deprecation enables us to focus on a new architecture for scale-to-zero databases, zero-downtime upgrades (more on this later), and more. Afterward, we’ll re-evaluate multi-cloud deployments beyond AWS, our current cloud provider.

What’s the current status of Fly Postgres on Supabase?

We have disabled Fly Postgres signups and existing Fly Postgres customers will no longer be able to spin up new projects on Supabase. However, you can still access any existing Fly Postgres database.

What is the deprecation timeline?

Before March 14:

  • You will still be able to access your existing Fly Postgres projects. We strongly recommend that you transition to another Postgres provider as soon as possible.
  • You can migrate your Fly Postgres database to Supabase by following our migration guide.

On March 14:

  • Your Fly Postgres projects are removed from our platform.

Reach out to our support team if you have any questions or concerns regarding this deprecation.

Best regards,
Supabase Team

3 Likes
2

Also heads up that there’s no happy path for project transfer here; the option is disabled (at least for me), so Supabase’s linked guide to treat this like a regular database migration is the best we have atm.

Good luck y’all—I’m probably going to email Supabase support. Seems like the ball was dropped hard on this one :disappointed:

1 Like
3

Do we even have access to the supabase password? My guess is it is not fronted out as it is held as a secret?

4

If you’re referring to the account password, no I believe SSO via Fly’s extension program IdP is the only way (click on Supabase Postgres in the side menu of the Fly dashboard).

If you’re talking about the database password, I grabbed mine by smashing the reset button in the Supabase project dashboard and then extracting it from a console machine:

fly console --region den --entrypoint '/usr/bin/env' --command env \
  | grep '.supabase.co'
1 Like
5

The database is a critical facility and fly should not entrust it to an external vendor.

The next risk I observe is Depot.

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.