Documentation

Deplyr is an open-source, self-hostable platform. You point it at a VPS you own — an EC2 instance, a Hetzner box, anything running Linux — and it installs what it needs over SSH once. From then on you deploy apps from GitHub, spin up Postgres or Redis, watch health and logs, and get told in Discord or Slack when something breaks.

Two roles are involved, not two VPS — worth keeping straight, but you only need one box to start:

Get a small Linux VPS from any provider — Hetzner, DigitalOcean, an EC2 instance, anything. Then run this on it:

curl -fsSL https://raw.githubusercontent.com/deplyr/deplyr/main/infra/install.sh | bash

That's the entire install. It figures out the rest on its own, and prints a URL when it's done.

1. 1

   Open the URL it printed

   It's just your server's IP address, like http://13.126.137.183. First time, this is a setup page — pick an email and password. That's your one account for this instance; there's no invite flow or public sign-up here, on purpose.

2. 2

   You're in — and this server is already registered

   Open Servers and you'll find This server already there and connecting — it's the box you just installed on. Deplyr works over plain HTTP on its IP address; no domain is needed to start deploying.

3. 3

   Add a domain whenever you want (optional)

   Point the domain's DNS A record at your server, then go to Settings → Instance address and type it in. HTTPS is issued automatically within a minute — no reinstall, no editing files on the server.

4. 4

   Updating later

   SSH back into the box and run the exact same command again. It updates in place — your account, servers, projects and secrets are untouched.

There are two ways to connect it — pick whichever fits your setup:

From Servers → Connect server, give it a name, an IP address, and either a root password or an SSH private key. Deplyr connects once over SSH and installs Docker, nginx and a small agent — after that it never needs SSH again. The agent dials out to the control plane and stays connected, so the server needs no open inbound management port.

Once connected you get live CPU, memory, disk and load, with history charts from 1 hour to 7 days, and a warning if the agent's heartbeat goes stale.

You don't need this screen to get started: the box running Deplyr is registered for you automatically as This server. Use it when you want more — connect as many additional servers as you like, and run every deploy, database and project across all of them from this one Deplyr instance.

Projects → New project picks a server and a repo, then Deplyr detects the framework — Next.js, NestJS, plain Node, or anything with a Dockerfile — along with the package manager (npm, pnpm, yarn, bun), the Node version, and monorepo subfolders. Everything it detects is editable afterwards on the project's Settings tab: install, build and start commands, the root folder, and the health-check path.

From a server's Databases tab, create a Postgres or Redis instance: choose the version, port, memory limit, and — for Redis — an eviction policy and persistence mode.

Databases bind to the server's loopback address, reachable only by apps running on that same server. Credentials are never shown by default — reveal them on demand from the database's page, or connect an app to one directly when creating it.

Each database gets its own health status, live stats (connections and cache ratio for Postgres; hit rate and memory for Redis), history charts, and container logs.

Every project gets a free <name>.<your-domain> address the moment it deploys. Add your own domain from the project's Domains tab and Deplyr shows you the DNS record to create, verifies it automatically once it propagates, and issues a real Let's Encrypt certificate — no wildcard certificate needed for custom domains, and it renews itself from then on.

Add a channel from Notifications in the sidebar. You'll need a webhook URL:

Deplyr sends a test message before it saves the channel, so a broken webhook is caught immediately — editing a channel's webhook later works the same way. Every attempted delivery, including failures and why, shows up in the channel's history.

Separately, the Activity page logs every action across every server and project — deploys, database changes, installs, agent connects, secret changes, alerts — filterable and searchable in one place.

infra/install.sh generates all of these on first install. The only one you'd normally change afterward is the domain, and that's done from Settings → Instance address now, not by editing this file — see Self-hosting above.