4. Deployments
Create a deployment
- From the dashboard, open your project.
- Choose Create New Deployment.
- Pick a type: Server Deployment, API Deployment, Website Deployment or Database Deployment.
- Fill in the form. The form shows the price of each plan.
Every form has a Deployment guide button. It opens a panel that explains how to package your build, upload it and connect to it, with examples.
Which type do I need?
| You want to host | Type | Guide |
|---|---|---|
| A multiplayer game server, or any long-lived socket server that players connect to directly | Server | Server Guide |
| An HTTP service: a backend, a REST API, a web app with server code | API | API Guide |
| A static site: HTML, CSS, JavaScript and assets from a build folder | Website | Website Guide |
| A MySQL or PostgreSQL database | Database | Database Guide |
The deployments list
Inside a project, the deployments are shown as cards. Use All Deployments or Favourites, and filter by Deployment Type. Star a deployment to add it to Favourites.
What every deployment page has
Open a deployment from its project. The details differ by type, but these parts are common:
| Part | What it does |
|---|---|
| Refresh | Reloads the page's data |
| Update | Changes the deployment's build or settings |
| Scale | Changes the regions and how many containers run. Server, API and Website |
| Update on the plan panel | Changes the hosting plan. A database uses Change plan |
| Start / Stop | Starts or stops the deployment. See the billing note below |
| Logs | Opens the logs page |
| Delete | Deletes the deployment. Type its name to confirm |
| Endpoints | The addresses to connect to. View all endpoints lists every one |
| Metrics | CPU, RAM, bandwidth, storage and container counts |
| Usage & cost | What the deployment costs per hour, and any usage over the plan |
| Activity | What happened to the deployment, filterable by All, Warnings+ and Errors |
| Integration guide | How to connect, with your deployment's real values filled in |
| Webhooks | Sends events to your own HTTPS endpoint |
| Access Keys | The access keys attached to the deployment. See Section 5 |
While a change is running, a progress bar shows it and the action buttons are disabled. Only one change runs at a time.
Rollback on failure is on by default when you update a deployment or change its plan. If the change fails, the previous configuration or plan is restored.
Stop does not stop billing
Stop keeps the deployment's reservation, and it keeps billing. A stopped deployment costs the same as a running one. Only Delete ends the charge.
Use Stop to take a deployment offline for a while. Use Delete when you no longer need it.
Logs
The Logs button opens two tabs:
| Tab | What it does |
|---|---|
| Live tail | Shows the last lines a running container printed. Choose the Container and the number of Lines (100, 200, 500 or 1000) |
| Download by date range | Choose From (UTC), To (UTC) and one or more containers, then Request logs. A download link is emailed to you |
Upload and redeploy limits
To protect your account from a script that loops, or from a deploy key that has leaked, MultiConnectCloud limits how fast builds can be uploaded and deployed:
- how many uploads a deployment may have unfinished at once;
- how many uploads an account may start in a day;
- how many times a deployment may be redeployed in an hour;
- how many deploy requests one access key may make.
Ordinary work, including a busy CI pipeline, stays well inside them. When a limit is reached, the upload or redeploy is refused with a message saying which limit it was, and you get an alert that names the access key involved. If that key should not be deploying, delete or regenerate it on Access Keys (Section 5).
An upload that is started and never finished is cleaned up automatically.
Webhooks
- On the deployment's page, open Webhooks.
- Turn on Enable webhook and enter a Webhook URL. It must start with
https://. - Choose Reveal secret to see the signing secret, and Send test event to check delivery.
Event reference lists every event and the headers each delivery carries. The panel shows Healthy, or Failing with the number of failed deliveries in a row. The type guides explain each type's events.
A new address on a new domain
A deployment may show a warning that it has a new address on a new domain. Your current address keeps working in the meantime.
- Update your apps and game clients to use the new address.
- Choose the button on the warning, turn on Yes, my apps and clients now use the new domain, and choose Confirm.
The new address becomes the main one shown. The old one will be retired later, so update everything that uses it. You can Undo the confirmation.

