Your first deploy

The flow is the same for every runtime — Node.js, Python, Go, Ruby, Rust, Elixir or Docker. The only thing that changes between them is the pair of commands you type in step three.

The five-minute path#

1. 1
   Connect your Git provider

   In the dashboard, open Account → Git providers and authorise GitHub, GitLab or Bitbucket. Grant access to the repositories you want Muerte Cloud to see — you can widen or narrow this later without redeploying.
2. 2
   Create a new service

   Click New → Web Service, pick the repo and branch. Muerte Cloud scans the tree and suggests a runtime; override it if the guess is wrong.
3. 3
   Set build and start commands

   Confirm the suggested commands or edit them. The build command produces artefacts; the start command boots the process that binds to $PORT. See the table below for typical values.
4. 4
   Add environment variables

   Paste a .env file or enter values one by one. Sensitive strings are encrypted at rest and never printed to logs. You can wire them up later, but most apps need at least a DATABASE_URL.
5. 5
   Create and watch

   Click Create service. The Deploys tab streams build and runtime logs live. When the health check passes, traffic swings to the new instance and the service URL becomes reachable over HTTPS.

Picking a service type#

Web services are the most common choice, but Muerte Cloud offers four other types for jobs that don't accept HTTP traffic. Use the cheat sheet below or read the full service types guide.

Build and start commands by runtime#

Minimal Node.js example

import http from "node:http";

const port = Number(process.env.PORT ?? 8080);

http
  .createServer((_, res) => res.end("ok"))
  .listen(port, "0.0.0.0", () => {
    console.log("listening on", port);
  });

What happens after you click Create#

Every deploy runs the same three-stage pipeline:

1. 1
   Build

   Dependencies are installed and artefacts produced on separate build compute. Output is captured into an immutable image.
2. 2
   Start

   A fresh instance boots the image. Once the health check passes, traffic swings from the previous instance in a single step.

Read the full pipeline reference in How deploys work.

Verifying the service is live#

Once the Deploys tab shows Live, the service is reachable at https://<name>.muerte.app. Quick checks:

# HTTP 200 with response headers
curl -I https://my-service.muerte.app

Live and historical build/runtime logs are also available on the service's Logs tab in the dashboard.

If the first deploy fails#

Next steps#