Infrastructure

Custom Domains

Every BRICQS deployment gets a live HTTPS endpoint on bricqs.run automatically. You can also bind a custom domain — your own apex or subdomain — to any running deployment.

Default endpoint

Immediately after a deployment reaches running state, your model is reachable at:

https://<app-name>.bricqs.run

This endpoint is TLS-secured, globally accessible, and requires no DNS configuration on your end.

Adding a custom domain

Custom domains are managed from the deployment's Settings tab in the dashboard. The process:

1
Add the domain
Enter your domain (e.g. api.yourdomain.com) in the Custom Domains panel. BRICQS generates a DNS verification token.
2
Add the DNS records
Add the CNAME and TXT records shown to your DNS provider. BRICQS verifies ownership automatically.
3
SSL is provisioned
A managed TLS certificate is issued and renewed automatically. No certificate management required.
4
Traffic routes to your deployment
Once the certificate is ready, all traffic to your custom domain is routed to the bound deployment.

DNS records

Subdomain (CNAME)

bashType:  CNAME
Name:  api   (your chosen subdomain)
Value: <app-name>.bricqs.run

Apex domain (A record)

Apex domains require an A record pointing to the IP returned during domain setup. Some DNS providers support ANAME/ALIAS records — use those if available since they handle IP changes automatically.

Note: DNS propagation typically takes 5–30 minutes. Certificate issuance follows within a few minutes of verification. Both are automatic — no manual renewal is needed.

Multiple domains

A single deployment can serve multiple custom domains. Each is independently verified and gets its own certificate. You might use this to serve both api.yourdomain.com and chat.yourdomain.com from the same running container.

Rebinding to a new deployment

To move a domain from one deployment to another (e.g. promoting a preview to production), remove the domain from the old deployment and add it to the new one. Certificate state is separate per binding — the new deployment gets its own certificate issued within minutes.