Quickstart

Deploy your first service on Muerte Cloud in under five minutes: connect a repository, pick a service type, and get a live HTTPS URL.

Before you start#

An account on Muerte Cloud (registration includes a starting bonus).
A Git repository with your app, or a Docker image / archive if you prefer to bring your own build.
A process that listens on the port from the PORT environment variable — required for web services only.

Deploy in five steps#

1
Open the control panel
Go to console.muerte.cloud and sign in.
2
Create a service
Press Create service and choose the type: web service, static site, background worker, cron job or database. See service types if you are unsure.
3
Connect the source
Link a Git repository and branch, or point the service at a Docker image or an uploaded archive. The builder detects most stacks automatically.
4
Set build, start and resources
Check the build and start commands, add environment variables, and pick vCPU and RAM. Defaults are fine for a first deploy.
5
Deploy and open the URL
The first build starts immediately. When the status turns Running, open the generated *.muerte.cloud URL — HTTPS is already in place.

Bind to the right port#

A web service must listen on 0.0.0.0 and the port provided in PORT. Hardcoding a port is the most common reason a first deploy builds successfully but never becomes healthy.

server.js

const port = process.env.PORT || 3000;
app.listen(port, "0.0.0.0", () => {
  console.log("listening on " + port);
});

Static sites need no port

Static sites are built once and served from the edge — no process, no port, no start command.

What to do next#

Attach a custom domain

Point your own domain at the service with managed TLS.

Move secrets to variables

Keep tokens and connection strings out of the repository.

Add a database

Managed Postgres or a key–value store wired into the service.

Schedule backups

Protect volumes and databases before you have real users.

Turn on notifications

Get told when a deploy fails instead of finding out later.

Connect an AI agent

Manage services from an assistant over MCP.

If the first deploy fails#

Open the deploy and read the build log — the failing command is at the bottom.
Check that the build command matches your package manager and lockfile.
Confirm the start command actually starts a long-running process.
For "no open ports detected", revisit the port section.