Custom domains
Plan requirement
Section titled “Plan requirement”A custom domain is part of the Pro plan and up (Pro, Business) — see Plans and pricing. Adding one on Free is refused with a message pointing at the upgrade.
Add the domain
Section titled “Add the domain”At Venue settings, the Custom domain card takes one hostname per venue, such as menu.yourrestaurant.com. Submitting it registers the hostname with Cloudflare and stores it as pending.
DNS records
Section titled “DNS records”Add two records at your DNS provider:
- CNAME: your hostname →
menus.qaema.ai - TXT: a name and value Cloudflare generates for that hostname, shown on the card once it’s pending — used only to prove you control the domain.
Checking status
Section titled “Checking status”Once the records resolve, click Check now. The domain moves from Waiting for DNS to Active once both the hostname and its HTTPS certificate are confirmed live; until then, the card shows whatever Cloudflare last reported and keeps the DNS records visible so you can compare them.
Both addresses keep working
Section titled “Both addresses keep working”Your {slug}.qaema.ai address is never disabled — a custom domain is additional, not a replacement. That also means renaming your venue’s address (see Venue settings) re-points an already-active custom domain to the new slug automatically, rather than breaking it.
Removing it
Section titled “Removing it”Remove on the card deletes the hostname from Cloudflare and drops the record; the menu keeps serving on the Qaema subdomain immediately. Deleting the whole venue removes any custom domain first.
Dashboard only
Section titled “Dashboard only”There is no MCP tool for adding or checking a custom domain — this is a dashboard-only action at /app/settings.