Your domain, HTTPS included
Point a hostname at any running deployment. flowbit checks your DNS, issues a Let’s Encrypt certificate, and routes the traffic — no certificate files to handle.
1
DNS record
A single CNAME per hostname
5
Domain states
pending_dns → active
Auto
HTTPS
Let’s Encrypt via ACME
28
CDN points of presence
Coming soon
What Networking is
Networking covers how traffic reaches your applications. Its live part today is Custom Domains: from a project's Domains tab you map your own hostname to a running deployment, and flowbit handles DNS verification, routing and the HTTPS certificate.
Adding a domain is five steps: enter the hostname, pick the target deployment, add the CNAME flowbit shows you at your DNS provider, verify, and serve over HTTPS. Each domain moves through pending DNS, verifying, issuing and active, or failed with a clear next step, and the list shows the certificate expiry.
Certificates are issued automatically through Let's Encrypt. This is separate from Secrets → Certificates, which is an inventory only. Owners and admins add, verify and delete domains; every member can see them.
The global CDN is the next part of Networking. The dashboard already shows the network map with 28 planned points of presence across the Americas, Europe, the Middle East, Africa and Asia-Pacific; regional traffic and function-region data arrive in a later phase.
Live in five steps
Add the hostname
From the project Domains tab, enter the fully-qualified hostname.
api.example.comPick a deployment
Choose a running deployment in the same project as the target.
Create the CNAME
flowbit shows the exact record to add at your DNS provider.
Verify
flowbit checks DNS, then requests a certificate automatically.
Serve over HTTPS
The route goes live and the certificate expiry shows in the list.
One record at your DNS provider
Add a CNAME to the platform edge host shown after you create the domain, then click Verify.
- Works with any DNS provider
- Certificates issue and renew automatically
- Apex domains: follow the manual instructions
; Target shown in Flowbit after you add the domain
api.example.com. 3600 IN CNAME <platform-edge-host>.Always know where your domain stands
pending_dns
Waiting for your CNAME
verifying
Checking the DNS record
issuing
Requesting the certificate
active
Serving over HTTPS
failed
Fix DNS and verify again
Routing and TLS, handled
Custom domains
Map any hostname to a deployment in the same project.
Automatic HTTPS
Let’s Encrypt certificates issued through ACME, with expiry shown per domain.
Owner-controlled
Owners and admins add, verify, and delete domains; every member can see them.
Global CDN
Regional request share and function region maps across 28 PoPs — coming soon.
Planned CDN points of presence
- IAD Ashburn
- SFO San Francisco
- ORD Chicago
- DFW Dallas
- SEA Seattle
- MIA Miami
- YUL Montreal
- GRU Guarulhos
- SCL Santiago
- BOG Bogotá
- LHR London
- FRA Frankfurt
- AMS Amsterdam
- CDG Paris
- ARN Stockholm
- MAD Madrid
- WAW Warsaw
- DXB Dubai
- JNB Johannesburg
- SIN Singapore
- NRT Tokyo
- ICN Seoul
- HKG Hong Kong
- BOM Mumbai
- DEL Delhi
- SYD Sydney
- MEL Melbourne
- AKL Auckland
What ships today
| Capability | Status |
|---|---|
| Custom domains per deployment | Live |
| DNS verification + automatic HTTPS | Live |
| CDN regions & analytics | Coming soon |
| Wildcard certificates | Not yet |
| DNS provider API automation | Not yet |
Common questions
Can I use an apex domain like example.com?
Yes, with the manual instructions shown in the dashboard; ALIAS automation is not included yet.
How is this different from Secrets → Certificates?
Certificates in the vault are an inventory. Domains owns DNS verification, routing, and certificate issuance.
Verification failed — what now?
Check the CNAME points at the target shown in flowbit, wait for DNS to propagate, and click Verify again.
When does the CDN launch?
The network map is visible in the dashboard now; live CDN data is planned for a later phase.
Put your app on your own domain
One CNAME and HTTPS is on.

