convex-domains

Set up a custom domain with your own provider Walk the user's own registrar through pointing their domain at the Convex app: identify the target (hosting or deployment URL), create the DNS records, attach the custom domain, and rebind the auth origin if the app uses auth. Workflow Identify the target: the published site host (for *.convex.app static hosting) or the deployment's HTTP actions URL. Detect an ALREADY-AUTHENTICATED DNS CLI for the user's provider and OFFER to create the records automatically: Cloudflare → flarectl dns create (note: wrangler itself doesn't manage DNS records) or the CF API via their token env; Route53 → aws route53 change-resource-record-sets ; Google Cloud DNS → gcloud dns record-sets create ; DigitalOcean → doctl compute domain records create ; Vercel DNS → vercel dns add . Check auth read-only first ( flarectl user info / aws sts get-caller-identity / doctl account get ); show the exact commands and get a yes before running. If no authed CLI (or the user declines), tell the user exactly which records to create at THEIR registrar: the CNAME (or A/ALIAS at the apex) plus the TXT verification record — with concrete host/value strings, not placeholders. Attach the domain as a Convex custom domain (dashboard or CLI) and wait for verification; note DNS propagation can take minutes to hours. Verify records landed with dig +short . If the app uses auth (passkeys/OAuth), rebind the auth origin (SITE_URL / RP_ID / ORIGIN env vars) to the new domain and re-deploy/re-publish. Verify: the domain serves the app over HTTPS, including the apex → www redirect if configured. Rules Show more Installs 910 Repository get-convex/agent-skills GitHub Stars 42 First Seen 2 days ago Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass