yala
← help

custom domains.

every yala account ships on lnk.yala.la/yourname. if you’d rather use go.yourband.com — fully your domain, full TLS — that’s a few minutes of DNS.

why bother.

  • brand consistency — fans see your domain in posts, instagram bios, posters.
  • portability — if you ever leave yala, you keep the domain. links can redirect cleanly to wherever next.
  • tracking quality — first-party cookies (when relevant) work better; ad platforms trust your domain more than a shared one.

adding a domain.

  • go to workspace → domains.
  • click + add domain, paste go.yourband.com (or whatever you want — a subdomain works best; root domains require apex CNAME flattening which not all DNS providers support).
  • yala validates the hostname (RFC-1123ish label check), calls cloudflare’s POST /custom_hostnames, and returns DNS instructions for you.

the DNS records.

you’ll get two records to add at your DNS provider (route53, cloudflare-as-DNS, namecheap, godaddy, whatever):

  • verification TXT — proves you control the domain. yala’s domain-verify worker polls this; once it sees the value, the domain status flips to verified.
  • CNAME — points your subdomain at cloudflare’s fallback hostname (we’ll show the exact value). this is what actually serves your fans.
dns
go.yourband.com.   CNAME   yala-edge-fallback.cloudflare.com.
_yalachallenge.go.yourband.com.   TXT   "ya-12345abc"

DNS propagation usually takes a few minutes; sometimes up to an hour. yala polls every 60s and surfaces the verification status in the UI.

TLS / HTTPS.

once verification is in, SSL provisioning is automatic. cloudflare mints a cert via SSL-for-saas; we don’t touch your private key. the whole flow takes 2-10 minutes after DNS resolves.

renewal is automatic. you don’t need to think about it.

multiple domains.

the pro tier ships with 1 custom domain, teams with 5, enterprise unlimited. each domain has its own slug namespace — the same /abc123 can resolve to different links across different domains. handy for per-region domains (go.yourband.com + go.yourband.eu with different rules).

migrating from linkfire / feature.fm.

  • point your existing domain at yala (CNAME flip).
  • recreate your most-trafficked links in yala with the same slugs as the old service.
  • for everything else, yala’s edge worker can be configured with a fallback policy that 302s unknown slugs to the old service for a transition window. drop us an email — we’ll help wire it.
next uppublic API + webhooksREST routes for every CRUD; signed HMAC webhooks for the events you care about. free at every tier.