[Feature] Custom subdomain for cloud users

[areyabhishek]

Summary

Allow users to choose a custom subdomain or map to an existing domain.

Make it easy for users to set up a custom domain for their organisation. Wondering, if this will mean that the user can't access other organizations on this domain?

Front conversations

[somangshu]

@areyabhishek once a subdomain/domain is mapped with an A/CName record then it cant really be used for anything else.

With this are we trying to offer a white-labeling solution? Do we also map the Appsmith app with org as subdomain? Webflow follows a similar approach.

ex: xyz.appsmith.com will be your appsmith cloud app where xyz is the org and then cname mapping on this domain is possible > https://xyz.com - xyz.appsmith.com, as said before https://xyz.com cannot be used for anything else post this setup

[st-trade]

+1 to this!

[kidronnoc]

+1!

I’m using appsmith to build dashboards for my customers. This would make my apps a whole lot more secure than my current work around.

In the appsmith discord, another user reached out and said they wanted to see this feature.

[yan-hic]

+1, but seems request is stalled. I think this should be part of a broader offering, not seen elsewhere - hence a comp advantage !?...

Background: We are a B2B SaaS and planning on using A/S - or other low-code framework - as presentation layer to our clients and using something like customer_id.mydomain.com as entrypoint for apps would indeed look more professional. However we'd like to extend this to support multi-tenancy (own set of apps, users, security) and sub-domain specific SSO. On the latter, our clients use different IDPs and some require using their own to register "our" app in their directory, this means each subdomain should be mapped to a given IDP/url.

[kidronnoc]

Maybe we could make a new request and link back here

On Jan 18, 2023, at 10:30 AM, Yannick Einsweiler @.***> wrote:

 +1, but seems request is stalled. I think this should be part of a broader offering, not seen elsewhere - hence a comp advantage !?...

Background: We are a B2B SaaS and planning on using A/S - or other low-code framework - as presentation layer to our clients and using something like customer_id.mydomain.com as entrypoint for apps would indeed look more professional. However we'd like to extend this to support multi-tenancy (own set of apps, users, security) and sub-domain specific SSO. On the latter, our clients use different IDPs and some require using their own to register "our" app in their directory, this means each subdomain should be mapped to a given IDP/url.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[somangshu]

Hey @yan-hic @kidronnoc this issue is still active and can be used to track progress.

On that note, I don't think this is yet prioritised on the roadmap. Ill loop in @trishaanand & @sharat87 for a better answer!