Orkestia
Blog
App Host

Your own domain

Point a subdomain you own at the App Host website or at Buzz, using a CNAME.

You can keep the Orkestia hostnames, or put your domain in front. Website and Buzz are two different names. Each needs its own DNS record.

Two targets

You wantOrkestia host to CNAME toConsole place
app.example.com as the website<slug>.app.orkestia.devSite → Domains
relay.example.com as the Buzz relaybuzz-<slug>.orkestia.devSite → Buzz → Your subdomain

Do not CNAME your marketing site and your relay to the same hostname.

Website custom domain

On the site, open Domains.

  1. Enter the hostname you own (app.example.com).
  2. Attach it. The console walks certificate validation.
  3. Create the DNS record the dialog asks for (usually a CNAME to the site host), or let a connected DNS provider write it.

Website domains follow the same idea as Cloud Deploy custom domains, but the target is the App Host site, not a Cloud Deploy CloudFront distribution.

When attach finishes (apphost.site.domain-attach), Orkestia also appends https://<hostname>/callback to the Identity app client. That is the default Sign-in path. If your app's SPA uses another callback (for example /app/), register it with identity.app.configure-client — domain attach will not invent /app/ for you.

Buzz custom domain

Copy the CNAME target

On the Buzz tab, the Your subdomain box shows the CNAME value. It is the Orkestia Buzz host:

buzz-<slug>.orkestia.dev

Create the record at your DNS host

At your registrar or DNS provider, add:

TypeNameValue
CNAMErelay (or whatever subdomain you chose)buzz-<slug>.orkestia.dev

Example: relay.example.com → buzz-acme.orkestia.dev.

Or let Orkestia write the record

Connect Hostinger or Cloudflare under Connections, then create the CNAME from there. You can also paste the record by hand at any DNS host.

Tell Buzz the hostname (optional but recommended)

Enter the customer hostname (relay.example.com) on the Buzz tab and Re-apply. That adds your name to the relay certificate so wss://relay.example.com presents a matching certificate.

DNS checklist

  • Use a CNAME (or ALIAS/ANAME at the apex if your DNS host supports it). Do not invent an A record pointing at a platform load-balancer IP.
  • Wait for DNS to propagate, then open https://<your-host>/_readiness and confirm { "status": "ready" }.
  • Point websocket clients at wss://<your-host>, not at the website.

Related

Files

Org members store files that belong to the identity app on the site MinIO — the Files tab, not Storage and not App Data documents.

Troubleshooting App Host

Fix the usual App Host, App Data, Files, and Buzz mix-ups from the console.