Providers

Works with the DNS your customers already use.

We only call a provider automatic after a real connection on a real zone. Every other provider gets the same window, with the exact records.

See how each provider works

Free and public: live demo · CNAME checker · CNAME guides for Registro.br, Hostinger, Locaweb, HostGator and KingHost, Cloudflare, GoDaddy

Automatic

Your user pastes an API token or access key once. Cnamio creates only the records you asked for.

  • Cloudflare
  • Hostinger
  • Amazon Route 53

Guided

Each record with its type, name, value and TTL, ready to copy, checked until it is live.

  • Registro.br
  • HostGator
  • KingHost
  • Locaweb
  • Umbler
  • GoDaddy
  • any other provider

How it works

One script, one route, one webhook.

Your product keeps its look and its flow. Cnamio handles the DNS providers, the records and the propagation.

  1. You add
  2. Your user sees
  3. Your backend receives

Follow the quickstart

  1. You add

    One script and a session route

    Call connectDomain with the DNS records your service needs. The session token is created on your server, so your secret never reaches the browser.

    <script src="https://connect.cnamio.com/sdk/v1.js"></script>
    <script>
      cnamio.connectDomain({
        applicationId: 'app_…',
        token: SESSION_TOKEN, // POST /token on your server
        dnsRecords: [{ type: 'CNAME', host: '{SUBDOMAIN}', value: 'app.yourproduct.com' }],
      });
    </script>
  2. Your user sees

    A window that knows their provider

    They paste a token and the records are created, or they copy the exact records. In English, Portuguese or Spanish. When someone else manages the DNS, such as an agency or the IT team, you can send them a connection link that works without your keys.

    Connect domain · Your App

    Connect with Cloudflare

    shop.example.com · DNS hosted at Cloudflare

    shopCNAMEapp.yourproduct.com

    API token

    We use the token only now, to create these records. It is not stored.

    Connect

    Records created · checking the nameservers

  3. Your backend receives

    A signed webhook when the domain is live

    Every authoritative nameserver is checked until the records are there. Then domain.added arrives, signed with HMAC-SHA256.

    POST /webhooks/cnamio
    Cnamio-Timestamp: 1790000000
    Cnamio-Signature: sha256=9f2c…
    
    {
      "user_id": "user-42",
      "domain": "shop.example.com",
      "subdomain": "shop",
      "provider": "cloudflare",
      "type": "domain.added",
      "setup_type": "automatic",
      "propagation_status": "success",
      "cname_target": "app.yourproduct.com"
    }

For AI agents

Point your coding agent at it.

Give it one line. It reads the Cnamio skill and adds the session route, the connect window and the webhook, in your framework's conventions. You review the change like any other.

Everything for agents

Copy and paste into your AI coding agent:

Add custom domains for my users with Cnamio: read and follow https://cnamio.com/agent-onboarding/SKILL.md. If I don't have a Cnamio account yet, start in the sandbox right away and ask me before signing me up for a free account with my email.
What your agent does with it
  1. follow cnamio.com/agent-onboarding/SKILL.md
  2. read SKILL.md the steps, the routes and the webhook payload
  3. add POST /token a session route on your server; the secret stays there
  4. add cnamio.connectDomain() the connect window, where your users manage domains
  5. add POST /webhooks/cnamio checks the signature, then handles domain.added
  6. done The change is ready for your review.

Questions

Before you ask, the honest answers.

Something else? Write to contato@cnamio.com

Which DNS providers connect automatically?

Cloudflare, Hostinger and Amazon Route 53, each tested with a real connection on a real zone. Your user pastes an API token or access key from that provider and Cnamio creates the records. We only call a provider automatic after that kind of test.

Do you store my users' provider tokens or passwords?

No. Cnamio never asks for a provider password. A token or access key is used during that single request to read the zone and create the requested records. It is never written to disk, a database or a log, and it is discarded when the request ends.

Can Cnamio break DNS that already works?

It is built not to. Cnamio reads what exists first; if a record is in the way, nothing is written and your user sees what is already there and decides. It never deletes existing records, and the only one it can change is an SPF policy, extended with the new service while every existing term is kept.

Does Cnamio issue TLS certificates or serve traffic?

No. Cnamio handles DNS: finding the provider, creating or showing the records and confirming them. Your hosting keeps serving the domain and issuing its certificate; the domain.added webhook tells you when to do it.

How long does a connection take?

It depends on the provider's DNS: usually a few minutes, sometimes a few hours. Cnamio checks every 10 seconds for the first 2 minutes, then at growing intervals for up to 72 hours, and tells your backend if the records never appear. Once it is connected, Cnamio keeps checking the records and sends your backend a signed webhook if one disappears; this monitoring is included.

How is it charged?

By plan, with public prices: a free plan with 10 connections a month, paid plans with larger monthly allowances and custom plans by contract. Each domain counts once per month, a connection that never propagates does not count, and you follow the count in your dashboard.

How do I get access?

Create an account with your email at the end of this page. You get a test application, which connects any domain against a simulated provider without touching real DNS, and a live application on the free plan. For a paid plan or a contract, use the contact form or write to contato@cnamio.com.