Deploy an API service
Run an HTTP API on your instance and reach it over HTTPS through the platform edge.

What you'll run
A single container exposing an HTTP API on one port. The node edge terminates HTTPS and forwards requests to that port, so you do not need Caddy, a published host port, or a DNS record to get started.
Run the API
Or use Compose. The container only needs to listen on 8080 inside the instance; there is no host port to publish for HTTP traffic.
Set the origin port and open the URL
- Open the instance's Networking tab.
- In Sites, set the web origin to 8080 and save.
- Open the HTTPS URL shown there. A custom domain is optional.
Your app sees the original host and client address in X-Forwarded-* headers. If your framework has a trust proxy setting, enable it so generated URLs and client IPs are correct.
Raw TCP, gRPC, and other non-HTTP traffic
The website edge speaks HTTP. For a database, game server, MQTT broker, or raw TCP/gRPC service, use Publish a TCP port in the Networking tab. That gives you tcp://<node-ip>:<host-port>.
Practical -- try it now
Deploy your API in 5 minutes
- Provision an instance, SSH in, and run your container on port 8080.
- In Sites, set the web origin to 8080.
- Call /health on the HTTPS URL from your laptop.