Custom Domains
Connect your own domain - for example app.cliniciq.com - so your users land on your brand rather than MIOSA. All sandboxes, computers, and deployments under your org will be accessible through your domain automatically.
Setup wizard
Go to Settings → Domains and click + Add custom domain. The wizard walks you through three steps:
- Enter your domain (
app.example.com- nohttps://, 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.comdirectly) 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
Currently each org can have one white-label custom domain (the wildcard CNAME). Per-resource custom domains (a specific computer at studio.yourdomain.com) are configured per-resource in the computer settings.
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.