Skip to content

Add Managed Postgres Developer plan page - #2667

Open
kcmartin wants to merge 6 commits into
mainfrom
mpg-developer-plan
Open

kcmartin wants to merge 6 commits into
mainfrom
mpg-developer-plan

Conversation

@kcmartin

@kcmartin kcmartin commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

New page for the $4 Managed Postgres Developer plan, launching 23 Nov, plus Developer exceptions on the pages that assumed every plan has PgBouncer, a maintenance window, Support Portal access and 10GB volumes.

Merge after #2661 (this links to the Free plan page), and after Miguel's ui-ex stack is live: the Connect section says fly mpg attach sets the direct URL on Developer clusters.

Still to add: dashboard screenshots (Miguel will send them after the merge).

Tracking: https://github.com/superfly/docs-tracking/issues/396

@mintlify

mintlify Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
fly-io 🟢 Ready View Preview Nov 20, 2026, 10:58 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@kcmartin
kcmartin marked this pull request as ready for review November 20, 2026 17:22
@kcmartin
kcmartin requested a review from a team as a code owner November 20, 2026 17:22
@kcmartin kcmartin mentioned this pull request Nov 20, 2026

@miguel-fly miguel-fly left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worth saying how long backups are kept. dev-256 keeps one day of backups and other plans keep 10, so there's only about a day to restore from. On-demand backups are full only too: fly mpg backup create --type incr gets a 422.

backup_defaults.ex#L12-L17

Comment thread postgres/developer-plan.mdx Outdated

Your cluster starts with 1GB of storage and grows automatically, up to 5GB.

When your databases get close to 5GB, we email you and schedule an upgrade to the Basic plan. You can cancel the upgrade. If you cancel it and your data reaches 5GB, Postgres runs out of space and stops accepting writes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The scheduled upgrade to Basic and its cancel option aren't built, not even in an open PR. superfly/ui-ex#7026 only sends an email, when the fullest volume reaches 80% of the 5GB. The 5GB also holds WAL, so the data runs out before 5GB. And a full disk doesn't just stop writes: once Postgres can't write WAL it crashes and restarts, so the database goes down. Maybe: "When your cluster gets close to 5GB, we email you. Upgrade to Basic before it fills up, because a full disk takes your database down."

Comment thread postgres/developer-plan.mdx Outdated

## Pricing

The Developer plan costs **\$4 a month**, including storage. You pay for the whole month, including the time the cluster is paused.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jwnx, can you confirm this is how it works? I believe the $4 is priced for a 30-day month and billed by the second while the cluster exists. So, if the cluster is deleted before 30 days, the price is prorated.

See mpg_cluster_plan_rate_provisioning.ex#L26-L27

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All plans are billed by second and I didn't want to do it differently for this one, so a more accurate wording would be "plan costs $4 for 30 days, billed by second"

Comment thread postgres/developer-plan.mdx Outdated

## Connect to your cluster

Use the `DATABASE_URL` that [`fly mpg attach`](/postgres/create-and-connect) sets on your app. Its hostname starts with `pgbouncer`, like on other plans, but on the Developer plan it connects straight to Postgres. You don't need to change it if you upgrade to a plan with PgBouncer.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The hostname stays the same after an upgrade, but it then goes through PgBouncer in transaction mode, which ui-ex sets on every plan. An app built on Developer that uses prepared statements, SET, advisory locks or LISTEN/NOTIFY can break the moment it upgrades. Could this say to move those apps to the direct URL, or switch the pool mode to session, when upgrading?

See configuration_defaults.ex#L35

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When attaching, we now use the direct endpoint for dev-256, not the pgbouncer one

Comment thread postgres/developer-plan.mdx Outdated
| Storage | Up to 5GB | Up to 1TB |
| Storage cost | Included in the \$4 | \$0.28/GB a month |
| Restore | From a backup only | From a backup or a point in time |
| Postgres settings | Fixed | Can be changed |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No plan lets customers change Postgres settings today. The only setting they can change is the PgBouncer pool mode, which the pooling row already covers. Could this row go?

See settings.html.heex#L175-L200

fly mpg create --plan dev-256
```

Your cluster gets a 1GB volume by default.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other pages still say the default volume is 10GB: create-and-connect.mdx:41, plus the flag list at create-and-connect.mdx:50-52 (--plan basic, launch, scale; --volume-size default 10). postgres/index.mdx:50-51 also says 1TB max and up to 500GB at creation, with no Developer exception.

Follow the prompts to configure your cluster name, plan, and region. By default your cluster will be created with a 10GB initial volume, which grows automatically with your data; you can start larger using the `--volume-size` flag:

| Postgres settings | Fixed | Can be changed |
| Maintenance | Any time | In a [weekly window](/postgres/maintenance-windows) you choose |
| Auto-pause | Yes | No |
| Support | No direct support contact. We still respond to alerts on your cluster | Direct support from Fly.io |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This row is right, but other pages still promise support on every MPG cluster: postgres/index.mdx:17 ("24/7 support"), postgres/index.mdx:27 (Support Portal) and about/support.mdx:51 (orgs with MPG get the Support Portal). An org with only Developer clusters gets no Support Portal. Can those pages get the exception too?

## PgBouncer mode and your client

All MPG clusters include PgBouncer for connection pooling. The pool mode you choose on the cluster side affects what your client can do. See [Cluster Configuration](/postgres/cluster-configuration) for how to change modes.
All MPG clusters except those on the [Developer plan](/postgres/developer-plan) include PgBouncer for connection pooling. The pool mode you choose on the cluster side affects what your client can do. See [Cluster Configuration](/postgres/cluster-configuration) for how to change modes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lines 15-16 of this page still say the pooled URL goes through PgBouncer and the direct URL bypasses it, and lines 250-258 give every plan PgBouncer slots, with no Developer row.

## What's a maintenance window?

Every Managed Postgres cluster has one maintenance window each week. The window has a day, a start time and a length. Routine maintenance that we schedule for your cluster only starts inside this window. That includes updating Postgres and the software that runs alongside it, and applying configuration changes.
Every Managed Postgres cluster, except those on the [Developer plan](/postgres/developer-plan#maintenance), has one maintenance window each week. The window has a day, a start time and a length. Routine maintenance that we schedule for your cluster only starts inside this window. That includes updating Postgres and the software that runs alongside it, and applying configuration changes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other lines on this page still assume every cluster has a window: line 16 ("New clusters start with this window") and line 88 ("New clusters always start with the default window"). The flyctl section at lines 62-76 also doesn't say what fly mpg maintenance-window show and set do on Developer.

**Note**: You can't set the window when you create a cluster. New clusters always start with the default window, and you can change it after the cluster is created.

@jwnx jwnx left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left a few comments (:


## Storage limit

Your cluster starts with 1GB of storage and grows automatically, up to 5GB.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It grows automatically by 1GB at a time, up to 5GB


## Connect to your cluster

Use the `DATABASE_URL` that [`fly mpg attach`](/postgres/create-and-connect) sets on your app. On the Developer plan, it's the cluster's direct URL, which connects straight to Postgres.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestions (feel free to dismiss):

  • include the command fly mpg attach <cluster-id> -a <my-app>
  • mention that DATABASE_URL is the default secret fly mpg attach sets, but if it fails they can use another one with --variable-name (and maybe link to fly mpg attach docs)
  • when they upgrade, they can also unset the secret and attach again to get the pooled URL (fly secrets unset DATABASE_URL)
  • if I'm not mistaken, for it to work, you'll need the latest flyctl version.. others don't ship the dev plan

Comment on lines 49 to 53
-n, --name string The name of your Postgres cluster
-o, --org string The target Fly.io organization
--plan string The plan to use for the Postgres cluster (basic, launch, scale)
-r, --region string The target region
--volume-size int Initial volume size in GB (default 10)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
--enable-postgis-support Enable PostGIS for the Postgres cluster
-n, --name string The name of your Postgres cluster
-o, --org string The target Fly.io organization
--pg-major-version int The major version of Postgres to use for
the Postgres cluster. Supported versions
are 16 and 17. (default 16)
--plan string The plan to use for the Postgres
cluster: Dev-256, Basic, Starter,
Launch, Scale, Performance
-r, --region string The target region (see 'flyctl platform
regions')
--volume-size int Initial volume size in GB. Defaults to
the plan's size.

This branch was successfully deployed

1 active deployment
staging — 5c6719b3 Deployed Nov 20, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants