Custom domains
Pointing a domain you own at an application is not available on Gigadrive Network yet.
This page is a draft
Gigadrive Network does not support custom domains yet. An application is reachable on the gigadrive.app URLs generated for it, and there is no supported way to put a domain you own in front of one.
Not available yet
There is no console screen, API endpoint, CLI command, or SDK method for adding a domain, and the edge does not route
a hostname outside gigadrive.app. Do not plan a launch around custom-domain support. Gigadrive Network will publish
the procedure, records, and verification flow when the feature ships.
What you can control today
You choose the label your production URL uses, so my-app.gigadrive.app can be whatever reads best for the product rather than whatever the repository happens to be called. Deployment URLs has the procedure and the rules a label has to satisfy.
Labels are unique across the whole platform. If a name matters to you, claim it on the application before someone else does. You can hold it before you have deployed anything: the label is reserved immediately and starts serving after your first production deployment.
What does not work
Fronting a gigadrive.app URL with your own proxy or CDN is not a workaround. The edge picks the deployment from the Host header of the request, so a proxy that forwards your own hostname resolves to no deployment, and one that rewrites the header hides the real host from your Function.
Certificates work the same way. Gigadrive Network issues one wildcard certificate for the URLs it generates, described in SSL certificates, and nothing for a hostname it does not control.