
My favorite thing about Entri Connect is how it seamlessly automates domain setup, which is the most complicated and frustrating part of our user journey. We use it within Neweb.ai, our AI Website Builder, and our users are primarily non-technical founders and small businesses.
The connect flow feels native. The user types in their domain, we determine everything else for them, then let them login to their registrar from inside the modal. It looks native to our product, not some 3rd party pop-up, and we were able to customize it to match our branding.
Integrations: Install on our side was simple. The SDK and docs were concise, and we had it working in our onboarding flow without a huge engineering sidetrack. It even is compatible with the big registrars that our users actually use, like GoDaddy, Namecheap and Cloudflare.
Performance: Records propagate quickly and consistently. The overwhelming majority of users go live with their site in just a matter of minutes, not hours or days, as they watch and wait for their DNS to propagate.
Ai / Intelligence: The smart part of this is the auto-detect, which automatically finds the registrar and DNS provider and figures out the records to add or change so you don't have to know what an A record or CNAME does. That, to us, is the "it just handles it" side of an AI website builder.
Support / Onboarding: We had a few questions during integration, and the Entri team responded quickly; onboarding was frictionless enough that we didn't require much hand-holding.
Pricing / ROI: The return is realized in two ways – way fewer DNS support tickets and a significantly higher number of people publishing their sites rather than abandoning at the domain step. That alone pays for us. Review collected by and hosted on G2.com.
While auto-setup is fantastic for big providers, some of our users at smaller and regional registrars have to enter manual DNS settings. Given that many of our users are international, we're seeing this more often than we want, and the few instances end up in our support queue.
Records clash: Sometimes when a domain already has records pointing somewhere else, e.g. an old website or email system, the flow just needs a bit more background to help users. More explanation on what is going to be altered/replaced would make non-technical users more comfortable.
The volume pricing makes sense at the beginning and into a commercial, but as volume connection volume rises we watch it as a line item. Additional flexible tiers for expanding platforms would be appreciated.
It would be valuable if you could provide further insight into how many users abort the connect flow, so we know which ones to target with our outreach.
Not a single one of those is a dealbreaker. I think the core experience is really good and these are just more like room for improvement. Review collected by and hosted on G2.com.