Primarily, they are solving a pain point. You will ask, "How?". Let me explain what I understood. Look at this scenario:

I have my domains domain1.com and domain2.com. Now, I want to "serve" domain2.com naturally with the hosted application of domain1.com. Here, it gets complicated—you will at least need a redirection from your DNS provider. And it will generally do a 301 redirect. OK, that means when people go to domain2.com, they see domain1.com. The approach isn’t great.

With Flexi Domain, you can set your primary domain as your Project and add as many domains (depending on plan limits) as you wish to display. Yes, there's an initial verification process for the primary domain using meta tags, but once that's done, you can add other domains to the project. Whether it's an “A” record for the root domain or any other domain, Flexi Domain will serve and display the Project domain without any redirects. It would also resolve if someone goes to domain2.com/page1 , which is from your main domain already having domain1.com/page1.

Now, I have some concerns about it.
- How is it handling SEO? Will it be counted as a duplicate page?
- I also want to note that the UX/UI flow is very unintuitive; you need to add a project twice to make it work.
- Other parts need to be addressed, such as CORS permissions.
- How would the application handle add meta tags for external domains (e.g., Cal .com)?
- There are also other larger aspects of client/team permissions management that are missing.

From my personal experience, I would rate this, at this point in time, as 4/5. I made a video and went through the process of it. The additional one star is deducted depending on the concern voiced in the video and listed above.

The process is seamless and pretty easy to configure. You will need “A” record creation skills on DNS, which should be reasonably straightforward. Here is my video coverage of it https://swiy.co/video-flexidomain