Deploy your apps.
Without the bloat.

Self-hosted PaaS deploying from Git, targeting under 50MB RAM idle.

From git push to a padlock

No Kubernetes required.

One-command deploy

Push to Git, Ployer builds and deploys automatically. Dockerfile, Nixpacks, and Docker Compose all work.

  • Dockerfile Works
  • Nixpacks Works
  • Docker Compose Works

HTTPS with nothing to configure

Caddy and Let’s Encrypt handle certificates. Point your DNS at the server and the padlock is there.

Point DNS at the server
You, once
Certificates
Caddy and Let’s Encrypt
The padlock
There
Webhooks
GitHub and GitLab push events trigger a deploy. Set it up once.
Health checks
HTTP polling with auto-restart when a container stops answering.
Live logs
Build and runtime logs stream over WebSocket while they happen.
Multi-server
Run apps across several servers from one dashboard.
Encrypted secrets
Environment variables encrypted at rest with AES-256-GCM.
Container stats
CPU, memory, and network I/O per container.
Internet
Caddy Ports 80/443. TLS termination, automatic SSL
Ployer Rust/Axum API + SvelteKit frontend (single binary)
SQLite WAL mode
Docker Container mgmt
Caddy API Dynamic routing

Caddy, Ployer, Docker, one server

Everything runs on a single server. No orchestrator, no external database.

  1. Caddy takes the traffic

    Ports 80 and 443, TLS termination and automatic SSL, with routes set live through the Caddy API.

  2. Ployer holds the state

    A Rust/Axum API and the SvelteKit frontend in a single binary, keeping its state in SQLite in WAL mode.

  3. Docker runs the workloads

    Your apps run as containers, which Ployer starts, watches and restarts.

A 1 GB VPS is enough

Runs on virtually any VPS. No beefy hardware needed.

OS
Ubuntu 22.04+ / Debian 12
RAM
1 GB minimum
CPU
1 vCPU
Disk
20 GB
Arch
x86_64 / arm64
Prerequisite
Docker installed

Install in one command

Point your domain’s DNS A record to your server, then run as root:

curl -fsSL https://ployer.nusendra.com/install.sh | sudo bash

While it runs, the installer:

  1. Detect your OS and architecture
  2. Download the pre-built binary
  3. Configure Caddy as reverse proxy
  4. Set up systemd services
  5. Provision HTTPS automatically