Custom Domains

Connect your own domain - for example app.cliniciq.com - so users land on your brand rather than a MIOSA fallback URL. This page is the setup-oriented entry point. Use Deployment Domains as the canonical reference for URL precedence, exact deployment domains, and production routing behavior. MIOSA has separate domain surfaces for sandbox previews, production deployments, computers, and exact resource hostnames. Use the URL returned by the API for each resource instead of building hostnames in client code.

Domain surfaces

Surface	What it controls
Preview domain	Sandbox preview URLs such as `https://5173-sbx01j9x.sandbox.cliniciq.com`
Deployment domain	Durable app URLs such as `https://lead-magnet.apps.cliniciq.com`
Exact deployment domain	One customer-owned hostname mapped to one deployment
Computer domain	One customer-owned hostname mapped to one computer service

Preview domains and deployment domains are intentionally separate. A preview domain does not automatically become the production app domain.

Setup wizard

Go to Settings → Domains and click + Add custom domain. The wizard walks you through three steps:

Enter your domain (app.example.com - no https://, no trailing path).
Add the DNS records shown to your domain provider.
Click Continue to verify - MIOSA checks your DNS and activates the domain.

Required DNS records

Type	Name	Value	Notes
CNAME	`*.yourdomain.com`	`proxy.miosa.ai`	Routes all subdomains through MIOSA

Replace yourdomain.com with the apex domain you own (e.g. cliniciq.com if your custom domain is app.cliniciq.com).

Apex domains (no subdomain, e.g. cliniciq.com directly) additionally require an A/ALIAS record - add _miosa-verify.cliniciq.com TXT <token> as shown in the wizard.

TLS certificates

Certificates are provisioned automatically once DNS propagates. There is nothing to upload. You will see a valid https:// certificate on first browser visit.

Propagation time

DNS changes typically take 5-30 minutes but can take up to 48 hours depending on your provider’s TTL settings.

To check current propagation status, run:

dig *.yourdomain.com CNAME +short

The expected result is proxy.miosa.ai.

Troubleshooting

Verification fails immediately after adding records

DNS propagation is not instant. Wait a few minutes and click Retry verification in the wizard. The page polls every 5 seconds automatically while the wizard is open.

dig shows the right value but verification still fails

Some DNS providers add extra trailing dots or spaces. Ensure the CNAME value is exactly proxy.miosa.ai with no extra characters.

Cache flush

If you changed the record and it still shows the old value, try flushing your local DNS cache:

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Linux (systemd-resolved)
sudo systemd-resolve --flush-caches

Or check propagation from a neutral vantage point using dnschecker.org.

Multiple domains

Use Deployment Domains for the full model. Exact custom domains are configured per deployment or per computer. Tenant-level preview domains are self-service. Tenant-level deployment-domain routing exists, but tenant-level management is operator-assisted while exact deployment domains remain self-service.

Branding

Once your domain is connected, customize the app name, logo, accent color, and favicon at Settings → General → Branding. The Domains page shows a live preview of what your users will see.