Deployment
Custom Domains
Serve your API from your own domain instead of the default Fimaflow Cloud URL.
Why attach your own domain
A backend deployed on Runtime gets a working URL immediately, but shipping an API under a fimaflow.app subdomain isn't something you want in front of real customers — it leaks your tooling choice, and it's not the domain your frontend, your docs, or your DNS-based email setup (SPF/DKIM) already expect. Attaching your own domain makes the API look and behave like a normal, first-party endpoint of your product, without changing anything about how the workflow itself runs.
Attaching a domain
Point a domain or subdomain you own — api.yourcompany.com, for example — at your deployed workflow. Add the DNS record your registrar asks for (a CNAME for a subdomain, an A record for an apex domain), and Fimaflow verifies and activates it automatically once the record propagates — usually within minutes, though DNS propagation can occasionally take longer depending on your registrar and existing TTLs.
SSL, handled for you
A certificate is provisioned and renewed automatically once your domain is verified — no manual renewal, no separate certificate manager to run, and no downtime around expiry. This holds for every domain you attach, production or preview.
One domain per environment
Attach a different domain to production than to your preview deployments — for example api.yourcompany.com in production and staging-api.yourcompany.com for everything still in review, so a frontend or mobile client can point at the right environment without a code change — only a different base URL. See Runtime for how preview environments are created.
Interactions with the rest of the platform
- • Custom domains only apply to workflows deployed on Runtime — a Framework Export project is a normal codebase, so its domain is whatever you configure on the infrastructure you deploy it to.
- • Traffic on a custom domain shows up in Monitoring & Logs the same way as the default URL — attaching a domain doesn't change what's tracked.
Limitations
- • Custom domains are a Runtime feature — there's nothing to attach a domain to until a workflow has been deployed at least once.
- • You need control over the domain's DNS records to verify ownership; a domain managed entirely by a third party without registrar access can't be attached.