Allow custom domains for API & Storage

[marcinkoziej]

Feature request

Hi!
I'd love to be able to set a custom domain alias for my supabase project url, so that instead:

the users would see "Chose an account to continue to myproject.mydomain.org".

Is your feature request related to a problem? Please describe.

The google sign in will show: "Choose an account to continue to dalihgspogdhpodshhofdgogdssg.supabase.co which looks completely like phishing to anyone who received an 101 phishing-defense training.
So this is not purely aesthetic problem, but a business one - imagine you prototype a product using Supabase (which it is great at) but you loose conversion because users are afraid to sign in (being worried that some strange jfdsljfdsfuds.supabase.co people will get access to their precious Google account)! 😨

Describe the solution you'd like

Implement a basic custom domain support using LetsEncrypt free/automatic cert generation to secure it. Not hard to implement!

This would require:

• setting custom domains in project settings
• supabase proxy generating LetsEncrypt SSL cert to be able to serve the domain securely (alternatively, let user upload a commercial SSL cert)

Describe alternatives you've considered

I did search GH issues to learn if you have considered custom domains and decided against them for reasons; but I could not find any such discussions.

Additional context

None, thank you for great work and FLOSS generosity of your enterprise!

[kiwicopple]

we're working on this 👍

[marcinkoziej]

Great! Waiting with anticipation! <3

[inian]

For this particular issue, you can submit a verification request to Google as documented here

[stingray21]

Apparently there is a way to set this up for Firebase link. I was wondering if the same approach would work for supabase, too. I couldn't get it to work yet though, but that could very likely be my fault.

[marcinkoziej]

Apparently there is a way to set this up for Firebase link. I was wondering if the same approach would work for supabase, too. I couldn't get it to work yet though, but that could very likely be my fault.

This can only work if Supabase will allow a authDomain parameter where you pass your custom domain that is mapped to supabase project domain. So we need to wait for the team to implement such feature.

[marcinkoziej]

Hey @kiwicopple ! Is there a timeline for custom domains ?
This issue got more pressing because now Google urges to verify the domains used in Oauth (they send emails like the one below).
Because I have no control over the Supabase project domain, nor can I put a verification file in there, there is not way to verify Supabase instance - and It's a matter of time before Google will cut of the Oauth provisioning. Help!

[gauntface]

I just went through the OAuth flow for Google and quickly realized this would be an issue for me as well.

[alvinsga]

Is there an ETA for this feature?

[amaralc]

Same issue here. This would be great indeed.

[joshdance]

Found this thread looking for info on Supabase custom domains, would love this feature as well.

[hatton]

Since we can't launch until this happens, I'm wondering if we should just use deno.land directly, as they do offer custom domains. We'd lose the nice built-in SUPABASE_SERVICE_ROLE_KEY environment variable but aside from that, is there anything else that we'd lose vs. doing the deno functions in Supabase itself?

[wh1337]

Just out of curiosity, do we have an ETA for this feature? 👀