▲ ▼ Configuring custom domains for SaaS is difficult
Mature SaaS products often allow users to bring their own domain / subdomain. This allows for customizability and familiarity for their customers. Or perhaps you need to have a 3rd-party tool hosted under your domain for technical reasons. Scaling the SSL / TLS certificates for all these custom domains is very complicated!
In addition, your SaaS might need to support white-labeling so that clients can have their own branding on your app, such as their logo, colors, and other customizations to make it appear like part of their application. This is important when your user is trying to establish a consistent brand with their customers.
I implemented it for a few SaaS apps and noticed it's the same setup for all of them.
Then I decided to build a solution that anyone can use: https://saascustomdomains.com
It's pretty cool because it allows you to save ton of time and you won't have to manage any infrastructure.
Interesting, Can you explain a bit more about how you came about with your product and who are your target customers.
I had to scratch my own itch and create AppMasker ( https://appmasker.com ). Let me know what you think!
Basically built a node API server that coordinates a fleet of Caddy web servers configured as reverse-proxies. As users create new domains, I update the configurations in the caddy instances.
I faced this problem for https://Traverse.link and I found https://approximated.app which helped out beautifully (and worked with my firebase setup)
Very nice! Looks like it checks a lot of boxes. How did you find them?