Custom Domains

I wish Knack would bring back custom domains. Currently you can host your Knack app at your own custom domain by embedding your app but that creates other problems (can't use SSO, issues with design and the Embedded Login issue https://support.knack.com/hc/en-us/articles/360047758491-Embedded-Login-Sessions).

Having a custom domain would solve those issues and be greatly appreciated. 

1 Like

Out of interest @Knack Staff - why isn’t this possible? Is it so the Knack branding stays top of people’s minds when visiting apps? It would make my life so much easier if I could simply direct people to our website and access the app rather than having to embed it in our site which has issues with theme / plugin clashing etc.

3 Likes

Hi there! Thanks for posting and for reaching out to get some answers around custom domains.

In short - there are some technical limitations that have made supporting custom domains non-viable at this time. We’re balancing trade offs when it comes to the decisions we make for providing the best user experience for our builders and their live app users, while always considering security and engineering best practices.

I’d like to address some of the issues that have been brought up about embedded apps, which would be our recommendation in the absence of a custom domain offering.

  1. We are releasing an update very soon that will allow builder to choose their embedded apps’ login method. See more on how that will work here.

  2. We love to spread brand awareness for Knack, but that’s not our angle here. Wherever we can provide white-labeling, we will, but sometimes our hands are tied (as is in the case of the cookies login option for embedded apps). I’d encourage a quick read of this post by Google to understand the stance taken by them and other browsers recently on building a more private web.

  3. SSO should work for embedded apps in most cases. @Vincent94744 - have you reached out to support on this? We are limited in the resources we can provide to troubleshoot SSO and embedded apps due to the unknowns of your third party software, but we’ll try and point you in the right direction!

  4. While there are some known issues with the design, this article section in our knowledge base should help you identify the best CMS to host your embedded your apps on (see further down on that article for troubleshooting tips and links to our dev docs as well). We’re also working on some live app updates in an effort to continue to modernize our live apps, which could potentially make them more compatible with some of those host platforms.

We’ll do our best to support you in providing the best live app experience for your users. I hope this information helps more broadly, but do reach out to support@knack.com if you have any questions or issues specific to your app.

I agree, it makes so much easier for us to have a custom domain… I would pay extra for the service

1 Like

Custom domain, please

Dear Knack team. This is really an issue. There are many many places in Knack where embedding in a website is NOT a solution to whitelabelling.
For example: The links to the PAGE URL or PARENT PAGE URL in the Email Rules of a page direct to the knack.com link.
I, therefore echo the calls above. Please revisit this issue and add real custom domains that we can use.
In the meantime, I will not upgrade to get whitelabelling because the solution is not good enough.

1 Like

Hi Steve - thank you for expanding here, and I’m sorry to hear you’re still running into problems. We realize that custom domains are desirable for many customers, and of course are always open to revisiting issues!

With that being said, as I mentioned before, custom domains are still non-viable at this time due to technical limitations.

We’re very much invested in learning all of the reasons/examples why embedding on a website is not an acceptable solution to white labeling, so we can work towards solving each of those issues separately. It would be super helpful to get more information and feedback from all of you to break those issues down and identify the root problems (rather than solutions) for consideration.

Design Issues

Since I last came into this conversation, we have began work on solving some known design issues for embedded apps. We plan to allow builders to choose whether they want to include headers and font styles when embedding apps. Excited to get this one in your hands!

URL whitelabeling

The problem I'm hearing here is that you need to keep your end users on your embedded app, and away from the Knack URL. This may be for whitelabeling, or just to keep them within the full context of your external site. Could you expand a bit on why this is essential?

A possible solution here (depending on the root issue) would be to hard code the email paths that you are trying to direct your live app users to. See how appending the {Record ID} input on my email rule allows me to control the URL path:

I’m all ears if there are other problems/concerns/etc that have not been addressed, so we can break those down and make sure we’re solving issues individually. What I want to avoid here is getting too focused a single solution that we unfortunately cannot offer at this time. Thanks for the discourse, everyone!

We need custom domains. Many of your competitors offer it. So obviously can be done while being compliant with whomever.

1 Like