MultiConnectCloud › Website Deployments
1. What a website deployment is
A website deployment is a static site: a folder of files with an index.html, served as they are. Nothing runs on the server when a visitor opens a page.
| A website deployment is right for | Use something else for |
|---|---|
| React, Vue, Angular and Svelte apps | Server-side rendering, such as a Next.js app that needs a Node process. Use an API deployment, see the API Guide |
| A Next.js or Gatsby static export | Anything that reads a database or a secret at request time |
| Blazor WebAssembly | A game server. See the Server Guide |
| Documentation sites, landing pages, plain HTML |
Some terms used in this guide:
| Term | Meaning |
|---|---|
| Build | The .zip of your built site that you upload |
| Build output directory | The folder inside the zip that holds index.html |
| Container | One running copy of your site. You choose how many run in each region |
| Region | Where in the world containers run. One region is the primary |
| Hosting plan | The CPU, memory, storage and largest upload size each container gets. You pay the plan rate for every running container, by the hour |
| Operation | A change in progress, such as a deploy or a plan change. One runs at a time per website |
Every deploy is blue/green: new containers start with the new build, and they take over only when they are healthy. Until then the current build keeps serving. A build that never becomes healthy never replaces the one that works.

