Custom Domains

Telbase supports three ways to give your apps custom domains: per-project domains, organization subdomain routing, and organization path routing.

Per-Project Custom Domains

The simplest option. Point a single domain to a single project.

Add a domain

telbase domain add app.yourcompany.com

Add DNS records

The CLI returns a CNAME record to add at your DNS provider. Point your domain to your project's Telbase URL.

Verify

telbase domain verify app.yourcompany.com

Organization Domains: Subdomain Mode

Subdomain mode creates URLs like dashboard.acme.com and api.acme.com. Each project gets its own subdomain under your organization domain.

When to use subdomain mode

• You want clean, isolated URLs for each project
• Your DNS provider supports wildcard records
• You prefer app.acme.com over acme.com/app

Setup

# Add your organization domain
telbase org domain add acme.com

# Add DNS records (the CLI shows what to add):
# 1. TXT record for verification
# 2. Wildcard CNAME: *.acme.com → cname.vercel-dns.com

# Verify DNS propagation
telbase org domain verify acme.com

# Deploy a project — it automatically gets a subdomain
telbase deploy
# → https://my-dashboard.acme.com

Once verified, every project you deploy automatically receives a URL at {slug}.acme.com. No additional configuration needed per project.

Organization Domains: Path Mode

Path mode creates URLs like acme.com/dashboard and acme.com/api. All projects share a single domain with path-based routing.

When to use path mode

• You want all projects under one domain for SEO benefits
• Your DNS provider does not support wildcard records
• Corporate proxies or firewalls block subdomain resolution
• You prefer acme.com/app over app.acme.com

Setup

# Add your organization domain in path mode
telbase org domain add acme.com --mode path

# Add DNS records (the CLI shows what to add):
# 1. TXT record for verification
# 2. CNAME: acme.com → cname.vercel-dns.com

# Verify DNS propagation
telbase org domain verify acme.com

# Deploy a project — it automatically gets a path route
telbase deploy
# → https://acme.com/my-dashboard

DNS Setup Walkthrough

After adding a domain, you need to configure DNS records at your registrar. Here is the general process:

1. Log in to your registrar (Cloudflare, Namecheap, GoDaddy, Route 53, etc.)
2. Add the TXT record shown by the CLI. This proves you own the domain. The record name and value are provided in the CLI output.
3. Add the CNAME record. For subdomain mode, add a wildcard CNAME (*.acme.com). For path mode, add a bare CNAME (acme.com).
4. Wait for propagation. DNS changes typically take 5–30 minutes but can take up to 48 hours.
5. Verify by running telbase org domain verify acme.com. Telbase checks public DNS servers (Google 8.8.8.8 and Cloudflare 1.1.1.1) for your TXT record.

Setup Reminders

Telbase helps you complete DNS setup at every step:

1. Email with DNS records — When you add an org domain, all org admins receive an email with the exact DNS records and a “Verify Now” link. Keep this email handy while configuring your registrar.
2. Verification confirmation — Once DNS is verified, a confirmation email explains the auto-deploy behavior.
3. Dashboard banner — Pending domains show an amber banner on the Projects page with a link to complete setup.

Plan Requirements

Domain features vary by plan:

• Free ($0) — No custom domains. No organization domains. Projects are available at {slug}.telbase.ai.
• Starter ($5/mo) — 1 per-project custom domain + 1 organization domain.
• Builder ($19/mo) — 3 per-project custom domains + 1 organization domain.
• Pro ($79/mo) — Unlimited per-project custom domains + unlimited organization domains.

See the CLI Reference → org section for the full command reference.