Custom domains implementation

So we have waited for years for custom domains - and finally here!

BUT if you are on a standard site (i.e. not gen 4) - then what an absolute shockingly implementation.

I have a website totally served from knack… e.g. www.site.com

and the only way to make this work is to go back to 1990s!

I have to move my site from www.site.com - to a different sub domain.. e.g. exampleknack.site.com in order to be able to point to the slug e.g. exampleknack.site.com/myapp

then I have to sign up with someone like squarespace or another hosted website provider - to create a single page that says - to enter our website click here… and this will then link from www.site.com to exampleknack.site.com/myapp

they are now telling me the only way to serve a single site - e.g. www.site.com - is to upgrade to gen4 - and then loose all custom CSS etc etc.

How to Knack manage to continually year after year disappoint us with promises of features - only to implement then in such as way as they are all but useless.

The light at the end of the tunnel has just fused and gone off!

(I have tried to add a URL re direct - but the DNS provider and two others I have looked at do not allow a url direct to same route as name).

1 Like

Hi @andrew.uk
We’re sorry you are frustrated.
To quickly recap functionality:
In Classic Knack, custom domains work with subdomains only (like app.yourcompany.com), not root domains (like yourcompany.com). This is due to the technical architecture of Classic apps and how custom domains have always worked in Classic, before we were able to make them more widely available with our current recent releases.

In Next-Gen Apps, you can assign unique domains to different apps with full domain control.
Examples:
portal.mycompany.com
dashboard.clientname.org
inventory.manufacturing.net
crm.salesteam.com

The subdomain and landing/redirect approach is a standard & common practice across many SaaS platforms when dealing with legacy architecture limitations and compatibility, and should be fairly easy to set up. If your DNS provider does not allow URL redirects to the same root, there might be alternatives for you to look into like:

Cloudflare Page Rules - If you use Cloudflare as your DNS, you can set up page rules for URL forwarding
AWS Route 53 with S3 - Create a S3 bucket with redirect rules
Netlify Redirects - Use their redirect service for your root domain

Regarding losing Custom CSS functionality in Next-Gen, that is correct, for now.
Our plan to start rolling out custom code capabilities and frameworks next month (August 2025), beginning with custom CSS capabilities.

Thanks,
Kara

1 Like

How do we get to Next-Gen ? All I see in are app builder is Classic

Thanks

I recommend asking Support :man_technologist:

Thanks Kara for explanation,

For $25 a month (if you have more than one site) this is a very poor implementation. I have no choice to have a front page hosted else where saying “click here to enter” - something I have not had to do with any other SaaS platform since the '90s.

I apologise for having my entire site (well 8 sites under 6 accounts) on Knack - I didnt fully realise you only wanted us to use it for database type pages.

rgds

2 Likes

Thanks for getting this live. I actually like this implementation because I can create an index page on the root of the domain where I can then send people ib to the different knack apps on my account.

Things have changed so much since the net started so I get it might not be perfect for everyone but the new version has this.

Thank you to the knack team for getting this out.

Why don’t you just embed the app into a domain of your choice? Been doing that for years.?

1 Like

That is also what I have been doing for years, but I understand the usefulness of the app being the whole website directly.

That is what I am refering to in an other thread.

$25/month for each new Custom Domain is EXTRAORDINARY expansive!!

The Starter Plan is $59/month.

So 1 extra Custon Domain costs 42% of the whole Starter Plan.

???

it does not make sens at all.