HTTP Gateway
Put several services behind one hostname and route requests to them by path.
An HTTP Gateway is a service whose only job is routing. It takes one public hostname and sends each request to a different backend service based on the start of the path.
Without a gateway, each service you expose gets its own hostname:
api-x4k2.ng-west-1.cloud.simplifyd.com → api
auth-p8m1.ng-west-1.cloud.simplifyd.com → authWith a gateway, they share one:
app.example.com/api/... → api
app.example.com/auth/... → auth
app.example.com/... → webThat means one domain to configure, one certificate, and no cross-origin problems in the browser.
Creating a gateway
- Click + Add and choose HTTP Gateway.
- Enter a name.
- Click Apply.
The gateway gets its own hostname straight away. You can attach a custom domain to it like any other public endpoint.
Adding routes
Open the gateway's panel → Gateway Routes → Add Route.
| Field | Meaning |
|---|---|
| Path prefix | The start of the path to match. Must begin with /. |
| Backend service | The Docker service in this environment to send matching requests to. |
| Backend port | The port that service listens on. |
| Strip prefix | Whether to remove the prefix before forwarding. |
| Priority | Which route wins when more than one prefix matches. Higher wins. |
Only Docker services in the same environment can be backends.
Strip prefix
This decides what path your backend actually receives.
| Request | Prefix | Strip prefix | Backend receives |
|---|---|---|---|
/api/users | /api | on | /users |
/api/users | /api | off | /api/users |
Turn it on when the backend was written to be mounted at the root and knows nothing about /api. Turn it off when the backend already expects the full path.
Priority
Prefixes overlap. /api and /api/v2 both match a request for /api/v2/users. Give the more specific route the higher priority so it wins.
A catch-all route on / with the lowest priority is a common pattern — it sends everything not claimed by another route to your frontend.
Editing and deleting routes
Use Edit Route to change a route, or the trash icon to delete it. Changes apply without redeploying the backends.
Deleting a gateway
Open the gateway panel → Delete Gateway, then apply. The hostname stops serving. The backend services keep running and keep any endpoints of their own.
