Yes please.
Obviously I want backups and easy restore.
Would be great if there was a way to provide a secure public URL connection or at least an easy way to connect to the DB from outside Fly.
Any word on when managed Postgres will land?
Sorry, no ETA yet! We’re working on improving the FKS underpinnings right now, which involves lots of moving parts: supporting sidecars, init containers, etc. The upside here is that those features will flow back into the core Fly platform.
Any news on Postgres?
I want Percona PostgresSQL!
We’ve been quiet about this because the road to a good quality managed Postgres (and MySQL) had many obstacles. Many of them are being cleared now.
Essentially, we’ll be running Kubernetes operators, and our K8s implementation (FKS) is missing some important features (sidecars, init containers, etc).
We’ve had multiple people focused on this, and we’re close (weeks, not months) to be able to test internally. Meanwhile, we’ve been working on all the UI/API independently. It looks like these projects should line up nicely.
So, we can’t give you an ETA just yet. But we’ll post in a new thread as soon as we have something concrete to show.
Sorry to bother. I know it’s hard to give an ETA but do you think we’re going to have some news on managed Postgres in the coming months?
Hm… It looks like your request was heard and answered indirectly, 
: the latest newsletter, sent out today, said “it’ll be ready to play with within the next month-ish” and “[h]it us up if you’re interested in early access.”
It’s good to have a concrete (“-ish”) date now!
Aside: Apparently, “Fly MPG” is the official name. That’s better than my own proposal of Fly Postgres Definitely Managed Postgres…
What is this newsletter you speak of? I don’t see any emails from Fly.
It’s been coming out every month or so since June 2024 (with sender team@news.fly.io).
It’s rather well done: one of only two newsletters that I really read in any detail.
As far as I know, there isn’t a standalone HTTP link (unfortunately), but you may be able to send a message to that address and just ask for one. (They said at the end that they do read email replies, 
.)
Hmm thanks, my last email from them was from November 2024. I haven’t unsubscribed and I don’t see it in spam either.
[MID-RESPONSE]: I just got it 0 minutes ago… thanks!
Fly.io has a lot of customers so their newsletter emails get sent slowly over a few days. The emails are sent out in order of Signup by the looks of it as I have multiple accounts (personal and professional) and they seem to arrive based on the order that I created them.
And Koyeb just launched what they say is a fully managed postgres service (I don’t know the details of what that means as far as backups, restores, etc.) that bills only for running time (not when autoscaled to 0) and storage: Serverless Postgres GA: Production-Ready Databases for Large Scale and AI Apps - Koyeb
Any news about Managed MySQL ?
Is this ever going to get released? Or can I at least get in on the private Beta? Been using a managed MySQL cluster on another cloud provider but to minimize latency we would like to be bring it over to Fly and been waiting patiently for this to either enter Public Beta or GA, or at least get an invite to the Private Beta.
MPG has been GA for a while: Managed Postgres · Fly Docs
MPGv2 is currently in beta, but that isn’t any obstacle to using the existing MPGv1.
That’s great for Postgres users but what about MySQL???
Oh gosh sorry, my brain completely replaced “MySQL” with “Postgres” everywhere on this page.
I believe Managed MySQL was put on hold when MPG was released. We expected to be able to efficiently operate MPG (and managed MySQL) on top of k8s. As is probably evident from the MPGv2 announcement, k8s introduced complexity that has been detrimental to MPG stability, and we decided to invest in MPGv2 development, concurrent with maintaining and improving MPGv1.
I can’t speak to the MPG team’s plans once they have released and are happy with the state of MPGv2 maintenance (I’m not on the MPG team), but I think the advice for the time being is to stick with an alternative provider if you need managed MySQL.
Apologies again for my confusion in the original unhelpful response.