Compare · custom domain connection

An alternative for connecting your customers' domains.

If you are choosing a service to connect your customers' custom domains, here is what Cnamio does, what it does not, and how to compare any option on facts.

Reviewed on 18 November 2026

Read this with our bias in mind

We are the Cnamio team, so read this page with that in mind. We describe only our own product, with what it does today; we do not rate or describe other companies. Where a claim depends on a provider, it is one we tested on a real zone.

When Cnamio fits

  • You want public pricing and a free plan to start, without a sales call.
  • Your customers are in Brazil or Latin America: the connect window, guides and support speak Portuguese and Spanish, and Brazilian DNS providers are recognised.
  • You do not want your customers to type a provider password anywhere: Cnamio uses an API token once, a provider consent page, or exact records to copy.
  • You need existing DNS to be safe: Cnamio never deletes a record, and the only one it can change is an SPF policy, extended with every existing term kept.
  • You already have an integration built on the common token-and-window pattern and want to keep it (see the migration guide).

When another service fits better

  • You need TLS certificates issued and traffic proxied for your customers' domains. Cnamio handles DNS only; it pairs with your hosting or an edge service for that part.
  • You want to sell domains to customers who do not have one yet. Cnamio does not register domains.
  • Most of your customers use a DNS provider where you need automatic setup and Cnamio is still guided there. Today automatic means Cloudflare, Hostinger and Amazon Route 53.

What Cnamio does today

TopicCnamio
Automatic setupCloudflare, Hostinger, Amazon Route 53, with the customer's API token (used once, never stored)
Every other providerGuided: exact records with copy buttons, checked until live
Existing recordsNever deleted; only an SPF policy can be extended, keeping every term; conflicts are shown, not overwritten
PropagationConfirmed on every authoritative nameserver, for up to 72 hours
MonitoringIncluded: connected domains are re-checked and a webhook says when a record disappears or comes back
LanguagesConnect window and dashboard in English, Portuguese and Spanish
Developers and agentsREST API, browser SDK, one-file server SDKs (Node.js, Python), MCP server, OpenAPI and llms.txt
PricingPublic, with a free plan; see pricing
Not includedTLS certificates, traffic proxying, domain registration

Questions to ask any provider

  1. Does my customer ever type their DNS provider password into your window?
  2. What happens when a record is already at the name: is it replaced, or am I told?
  3. Which providers are automatic today, tested on a real zone, and which are guided?
  4. Is propagation confirmed on the authoritative nameservers, or on a cached resolver?
  5. Is monitoring after the connection included, or sold separately?
  6. Is the price public, and what exactly counts as a connection?

Switching

If you already connect domains with another service, the migration guide lists what changes in your code: usually the token URL, the script tag and the webhook URL.