Custom domains

Every app is reachable at https://<name>.flitzy.app. On the Pro plan you can add up to 5 domains of your own per app.

1. In the dashboard, open the app and go to Custom domains. Add the domain, for example app.example.com.

2. Create the DNS record shown there at your DNS provider:

   Subdomain (CNAME)

   Type	Name	Value
   CNAME	app.example.com	<name>.flitzy.app

   The CNAME must point to this app’s host, not any *.flitzy.app name.

   Root domain (A + TXT)

   A root domain like example.com can’t have a CNAME. Use both records:

   Type	Name	Value
   A	example.com	49.12.250.226
   TXT	_vibedeploy.example.com	vibedeploy-verify=… (shown in the dashboard)

   Use this too if your provider flattens CNAMEs (Cloudflare).

3. Click Verify. Once DNS is right, the certificate is requested from Let’s Encrypt; the status goes from issuing to active within a minute or two.

Certificates renew automatically. http:// redirects to https://.

Cloudflare

Set the record to DNS only (grey cloud). Behind Cloudflare’s proxy, verification fails, because the domain no longer resolves to Flitzy.

Rules

• A domain belongs to one app once it is verified. Before that, another app can claim it, so nobody can block a domain they don’t control.
• flitzy.app names can’t be added; every app already has its own.
• Domains are removed together with the app.
• DNS is checked against public resolvers (1.1.1.1 and 8.8.8.8). If verification fails right after a change, wait for the record’s TTL and try again.

With the API

POST   /v1/apps/:name/domains             {"domain": "app.example.com"}
POST   /v1/apps/:name/domains/:domain/verify
GET    /v1/apps/:name/domains             status: pending | issuing | active | error
DELETE /v1/apps/:name/domains/:domain