fix: deprecate Fly Postgres (#35002)

apps/docs/components/Navigation/NavigationMenu/NavigationMenu.constants.ts

@@ -2150,7 +2150,6 @@ export const platform: NavMenuConstant = {
         { name: 'Regions', url: '/guides/platform/regions' },
         { name: 'Compute and Disk', url: '/guides/platform/compute-and-disk' },
         { name: 'Database Size', url: '/guides/platform/database-size' },
-        { name: 'Fly Postgres', url: '/guides/platform/fly-postgres' },
         { name: 'HIPAA Projects', url: '/guides/platform/hipaa-projects' },
         {
           name: 'Network Restrictions',

apps/docs/content/guides/cron.mdx

@@ -19,12 +19,6 @@ For best performance, we recommend no more than 8 Jobs run concurrently. Each Jo
 
 Under the hood, Supabase Cron uses the [`pg_cron`](https://github.com/citusdata/pg_cron) Postgres database extension which is the scheduling and execution engine for your Jobs.
 
-<Admonition type="note">
-
-`pg_cron` is not fully supported on Fly Postgres. Learn more about [Fly Postgres limitations](/docs/guides/platform/fly-postgres#limitations).
-
-</Admonition>
-
 The extension creates a `cron` schema in your database and all Jobs are stored on the `cron.job` table. Every Job's run and its status is recorded on the `cron.job_run_details` table.
 
 The Supabase Dashboard provides and interface for you to schedule Jobs and monitor Job runs. You can also do the same with SQL.

apps/docs/content/guides/platform/fly-postgres.mdx

@@ -1,56 +0,0 @@
----
-id: 'fly-postgres'
-title: 'Fly Postgres'
-description: 'Deploy Supabase projects on the Fly.io platform'
----
-
-Fly Postgres databases are deployed on the Fly.io edge network. Fly Postgres is supported in [every region](https://fly.io/docs/reference/regions/) where Fly.io operates.
-
-<Admonition type="deprecation">
-
-Fly Postgres is being deprecated on April 11, 2025. Head over to the [announcement](https://github.com/orgs/supabase/discussions/33413) for more information.
-
-</Admonition>
-
-## Quickstart
-
-1. Authenticate via the CLI: `flyctl auth login`
-2. Access the Supabase dashboard by running `flyctl extensions supabase dashboard <app-name>`
-
-The full list of CLI commands for Fly Postgres are documented in the [Fly docs](https://fly.io/docs/flyctl/extensions-supabase/).
-
-## Connecting to your database
-
-If your network supports IPv6, connect directly to your Fly Postgres database, as its domain name resolves to an IPv6 address which can be directly used from within your Fly applications.
-
-If your network only supports IPv4, use Supavisor instead of connecting to the database directly. Supavisor's domain name resolves to an IPv4 address, allowing networks without IPv6 support to connect.
-
-To find your database's connection strings, visit the Supabase [database settings page](https://supabase.com/dashboard/project/_/settings/database).
-
-## Studio support
-
-Access the Supabase studio by running the following command: `flyctl extensions supabase dashboard <app-name>`. This command authenticates with Fly via OAuth and then logs you into the Supabase dashboard.
-
-In the dashboard, you gain access to several powerful tools, including:
-
-- SQL editor: Run SQL queries against your database.
-- Table editor: Create, edit and delete tables and columns.
-- Log explorer: Inspect real-time logs for your database.
-- Postgres upgrades: Upgrade your Fly Postgres instance to the latest version.
-
-## Permissions
-
-Supabase and Fly organizations have a direct one-to-one relationship. When you launch your first Fly Postgres database, it triggers the automatic creation of a corresponding Supabase organization if one does not already exist.
-
-User accounts on Supabase are also created on demand. Every Fly user gets a unique Supabase account, and this account is separate from any Supabase accounts you might already have.
-
-Upon launching a Fly Postgres database, the initiating user is granted the owner role within the new Supabase organization. All subsequent users are added with the `developer` role. Roles can be adjusted in the Supabase dashboard as required.
-
-## Limitations
-
-When using Fly Postgres, be aware of the current restrictions:
-
-- Direct database connections are only supported via IPv6. Read more in the [connecting to your database](#connecting-to-your-database) section.
-- [Network restrictions](/docs/guides/platform/network-restrictions) are not supported
-- Currently, only the database, Supavisor, and PostgREST are supported. Support for additional Supabase products such as Realtime, Storage, and Auth is planned.
-- The [pg_cron](/docs/guides/database/extensions/pg_cron) extension is not fully supported for Fly projects. Fly projects shut down after 15 minutes of inactivity, but transparently start up when an external request is received. However, this does not apply to pg_cron jobs, which aren’t triggered by external requests. ` pg_cron` jobs don’t run when the database is shut down due to inactivity.

apps/docs/content/guides/platform/regions.mdx

@@ -8,7 +8,3 @@ The following regions are available for your Supabase projects.
 ## AWS
 
 <RegionsList />
-
-## Fly
-
-Our [Fly Postgres](/docs/guides/platform/fly-postgres) offering (in private alpha) is supported in every region where Fly operates.

apps/www/_blog/2023-12-15-postgres-on-fly-by-supabase.mdx

@@ -14,6 +14,12 @@ image: lwx-supafly/fly-postgres-og.png
 thumb: lwx-supafly/fly-postgres-thumb.png
 ---
 
+<Admonition type="deprecation">
+
+Fly Postgres has been deprecated. See [deprecation announcement](https://github.com/orgs/supabase/discussions/33413) for more details.
+
+</Admonition>
+
 We're launching Fly Postgres, a managed Postgres offering by Supabase and [Fly.io](http://Fly.io).
 
 Fly Postgres databases launch on Fly.io's edge computing platform from any of their 37+ locations. You get everything you expect from a Supabase managed database:

apps/www/lib/redirects.js

@@ -2999,4 +2999,9 @@ module.exports = [
     source: '/features/fly-postgres',
     destination: '/features/postgres-database',
   },
+  {
+    permanent: true,
+    source: '/docs/guides/platform/fly-postgres',
+    destination: '/docs/guides/database/overview',
+  },
 ]