MultiConnectCloud › API Deployments
1. What an API deployment is
An API deployment runs a web service that answers HTTP requests: a REST API, a backend for a website or app, a webhook receiver. MultiConnectCloud handles HTTPS, so your code listens on plain HTTP inside its container and never handles a certificate.
| You want to host | Use |
|---|---|
| An HTTP or WebSocket service, in .NET, Node.js, Python, Go or Java | An API deployment (this guide) |
| A real-time game server built with MultiConnectSDK, or any TCP/UDP server | A Server deployment. See the Server Guide |
| Static files: a website, a WebGL build | A Website deployment. See the Website Guide |
| A managed database | A Database deployment. See the Database Guide |
What you get with an API deployment:
| Feature | What it means |
|---|---|
| HTTPS address | Every API gets its own https:// URL. You can add your own domain too |
| Regions | You choose where it runs, and how many containers run in each region |
| Autoscaling | Optional. Containers are added and removed with CPU and memory load |
| Zero-downtime deploys | A new build only takes traffic once it is healthy. If it never gets healthy, the old build keeps serving |
| Database link | Opens a MultiConnectCloud database's firewall to your API |

