Unsure if I go here or through Supabase directly… but I can’t seem to connect to my DB via its public URL (I double checked credentials). Based on earlier responses I assumed the URL was publicly accessible.
Our focus is Postgres. The other tooling is simply in the service of making Postgres easier to use. For context on the tagline, we use "Firebase alternative simply for positioning: it means that developers think of us when they are starting a new project (and we offer a few features like Realtime for realtime database updates, similar to Firebase’s Firestore).
Self-serve HA/replicas is coming for everyone as part of our new connection pooler. That said, our Fly Postgres offering is still in Beta because there are other things that we need to work through first: platform stability, SLAs, pentests, and other fun things. We’ll move out of Beta as soon as we can, but we need to be confident that we’re offering a reliable/secure service so that everyone has a good time
2 Likes
You should contact Supabase support! To do that, run fly ext supabase dashboard to sign in, then visit the help form at https://supabase.help.
In case it’s useful to others, though, I’ll comment here.
This could be happening if you are trying to connect from home and your ISP doesn’t support IPv6. See the Supabase announcement about IPv6, and, test your IPv6 support here. If indeed this is the problem, you can connect using the DATABASE_POOLER_URL which supports IPv4.
@joshua-fly can you share a ballpark release timeline for public beta and release?
1 Like
Is there a timeline/are there plans to also bring the other Supabase features to the offering? Just noticed that literally only Postgres ist working in the beta, but auth, storage, realtime are all disabled.
We’re focused on the Postgres offering for now @badsgahhl, so that we can get out of beta as soon as possible. Now that Fly offers an object store (through Tigris) it certainly makes it easier to port the rest of the features.
We will also start using Tigris for walg backups, so the entire system is contained on Fly infra
4 Likes
Will there be an official migration path from a “vanilla” Fly postgres cluster to Supabase? I’ve looked through the forum but couldn’t find any hint. Thanks!
1 Like
What about the bandwidth? Does it still apply even though both are in the same region - 250GB free then 0.09$?
We will not charge for in-region bandwidth, eventually. We’d switch this on now, but we’re in the middle of a big billing project that will include this change soon. If you’ve got a big in-region bandwidth bill, do contact support!
1 Like
I’m a little confused by what’s included in this partnership. How much of this diagram would be “inside” of fly?
My main motivation for trying to move everything into fly is so that requests between my app server, my cache server, and my database are all in the same data center (it’s pretty laggy without this).
Would moving supabase into fly solve this problem (eg. the GoTrue/PostgREST server are now in the same data center as my app/redis server)?
All of those services run on Fly.io! One exception is the connection pooler. For now, you should use the direct connection string.
2 Likes
That’s great to hear! Hoping to get into the beta!
To turn off connection pooling do I just edit Project > Settings > Database?
Yes, by unchecking the box there, you’ll see the direct connection string.
Note that if you want to connect from your home or workplace, you might want to use the pooler connection string, which resolves to an IPv4 address. The direct connection only resolves to IPv6, which isn’t supported by all ISPs.
As a current Fly.io and Supabase customer, will there be a way to migrate my Supabase Org over in to a Fly.io hosted Supabase Org? That might be asking a bit much but would love that capability 
Hi. I have an issue with my app thats using the supabase beta and I’m not sure where the best place to report or seek help would be. Should I post it here, in a new thread or to support?
You should post in a new thread or contact support Support · Fly Docs
First of all thanks for great feature in already amazing platform. I was just wondering - do you expect it to be ready for production use this year?
Yes, definitely! Coming very soon, we’ll be moving to public alpha (which in our world, comes after private beta 
).
Hey Joshua, does that include private DBs? (Ie. Within our wire guard network so they are not accessible publicly?)
Private databases won’t be ready at launch time, but it will be worked on during the beta.
1 Like