# Managed Postgres v2 is now in beta!

**URL:** <https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909>\
**Category:** Fresh Produce\
**Created:** [May 19, 2026, 3:41pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909 "2026-05-19T15:41:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![akshit-fly](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/akshit-fly/32/37188_2.png) [@akshit-fly](https://community.fly.io/u/akshit-fly)\
**Post date:** [May 19, 2026, 3:41pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/1 "2026-05-19T15:41:49Z")

</div>

We’ve started rolling out Managed Postgres v2.

The original Fly Managed Postgres runs on FKS. That caused some stability problems due to the unique problems that come with that. Managed Postgres v2 is built directly on Fly Machines, Fly networking, Flycast, and the same primitives the rest of your Fly apps use.

The main goal is stability. v2 was designed to make managed Postgres more predictable operationally: fewer moving parts, clearer ownership of the runtime, and a foundation we can keep improving without fighting the old architecture.

For now, v2 beta is only available in `dfw` and we are looking to expand it to more regions over time. It costs the same as the original Managed Postgres.

---

<div class="post-metadata">

**Author:** ![Luan\_Oliveira](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/luan_oliveira/32/37022_2.png) [@Luan\_Oliveira](https://community.fly.io/u/Luan_Oliveira)\
**Post date:** [May 19, 2026, 3:45pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/2 "2026-05-19T15:45:49Z")

</div>

Good to know!

What happens to us using the old MPG v1? Are we going to be auto-migrated after the full rollout?

---

<div class="post-metadata">

**Author:** ![akshit-fly](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/akshit-fly/32/37188_2.png) [@akshit-fly](https://community.fly.io/u/akshit-fly)\
**Post date:** [May 19, 2026, 3:47pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/3 "2026-05-19T15:47:33Z")

</div>

> [@Luan\_Oliveira](#):
>
> Are we going to be auto-migrated after the full rollout?

Not yet! We’ll provide a manual migration option down the line, and once MPGv2 and the migration path is stable, we MIGHT do an auto migration.

MPGv1 is still supported fwiw.

---

<div class="post-metadata">

**Author:** ![bcomnes](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/bcomnes/32/2563_2.png) [@bcomnes](https://community.fly.io/u/bcomnes)\
**Post date:** [May 22, 2026, 4:48pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/4 "2026-05-22T16:48:27Z")

</div>

Will pricing be the same?

---

<div class="post-metadata">

**Author:** ![halfer](https://avatars.discourse-cdn.com/v4/letter/h/df705f/32.png) [@halfer](https://community.fly.io/u/halfer)\
**Post date:** [May 22, 2026, 8:16pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/5 "2026-05-22T20:16:26Z")

</div>

> [@bcomnes](#):
>
> Will pricing be the same?

Yep:

> [@akshit-fly](#):
>
> It costs the same as the original Managed Postgres.

---

<div class="post-metadata">

**Author:** ![mmark](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mmark/32/47503_2.png) [@mmark](https://community.fly.io/u/mmark)\
**Post date:** [May 30, 2026, 12:17pm UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/6 "2026-05-30T12:17:01Z")

</div>

Very cool! Would this mean database migration tools for us doing self-managed postgres on fly machines too? I know it’s been listed in the “not there yet” column for v1.

---

<div class="post-metadata">

**Author:** ![Cavalato](https://avatars.discourse-cdn.com/v4/letter/c/cdc98d/32.png) [@Cavalato](https://community.fly.io/u/Cavalato)\
**Post date:** [June 23, 2026, 10:53am UTC](https://community.fly.io/t/managed-postgres-v2-is-now-in-beta/27909/7 "2026-06-23T10:53:37Z")

</div>

This is the 4th version of postgres on [fly.io](http://fly.io) and more often than not, it leaves customers in a tough spot with no auto migration. Please … take notes…
