Hostname to container
A domain is attached to a project, and the reverse proxy on your server is configured to match. Several projects can share one machine without colliding.
Networking
Point the hostname. The routing follows.
Attach a hostname to a project and requests reach the right container over HTTPS. The certificate is issued during the deployment, so bringing up a new domain is not a separate errand.
Capabilities
HTTPS by default
An origin certificate is issued as part of the routing setup, so HTTPS is not a separate step to remember after the deploy.
Changes are deployments
Routing changes go through the same recorded path as everything else, rather than being an undocumented edit on a live box.
01
The part everyone forgets until it breaks
Routing is invisible until it breaks, and then it is the only thing anybody cares about. Generating it rather than hand-editing it is not clever, it is just the difference between a product and a pile of scripts.
Because the proxy configuration is generated, the state of your routing is always something the system can describe. There is no drift between what you believe is deployed and what nginx is actually doing.
The complete product starts on Free.
Every plan includes every Deploy Bridge capability. Paid plans raise usage ceilings; they do not unlock this feature.