# Nearzero

> Nearzero is open-source software you install on a Linux server you operate. You use it to deploy apps and databases to that server, or to other servers you add over SSH. Traefik routes custom domains. Let's Encrypt issues HTTPS when ports 80 and 443 are open.

Nearzero is a self-hosted deployment platform, not a global CDN. You still patch, back up, and size the VPS. The Community edition is Apache-2.0 and free to self-host. You pay for your own servers, storage, and domain.

## Product facts

- Runtimes: Node.js, Python, Go, PHP, Ruby, and other container apps
- Databases: Postgres, MySQL, MariaDB, MongoDB, Redis, libSQL
- Stacks: Docker Compose and Docker Swarm
- Networking: Traefik routing, managed zones via CoreDNS, Let's Encrypt TLS
- Remote servers: control plane on one host, workloads placed over SSH
- Agent: can read project state and logs; production changes stay off until an administrator turns that gate on

## Indexable pages

- [Nearzero](https://nearzero.dev/): Install Nearzero on a Linux VPS to deploy apps, Postgres, Redis, and Compose from Git. Add remote servers over SSH. Traefik and Let's Encrypt handle HTTPS.
- [Nearzero docs — Install the control plane on your VPS](https://nearzero.dev/docs): Install Nearzero on a Linux VPS, add remote servers, route domains with Traefik and Let's Encrypt, and use an Agent that cannot change production until you turn that on.
- [Install Nearzero on a Linux VPS](https://nearzero.dev/docs/self-hosting): Download the installer, check the SHA-256 checksum, finish setup on your HTTPS admin URL, then back up the control plane. You still patch and size the VPS.
- [Nearzero architecture — Your servers run the apps](https://nearzero.dev/docs/architecture): Nearzero is the control plane. Docker, Traefik, and databases run on Linux servers you operate — the same host or remote boxes you add over SSH.
- [Add remote Linux servers to Nearzero](https://nearzero.dev/docs/remote-servers): Keep the control plane on one host, add another VPS over SSH, and send public traffic to Traefik on that box. Keep Docker and management ports private.
- [Point Nearzero domains at the server that runs the app](https://nearzero.dev/docs/domains-and-https): Delegate a managed zone to CoreDNS or bring your own hostname. Traefik and Let's Encrypt terminate HTTPS on the selected server when ports 80 and 443 are open.
- [Nearzero Agent — it can see your infra. Production writes start off.](https://nearzero.dev/docs/agent-safety): The Agent can read deploys, logs, domains, and servers. It can only change what your role and workspace policy allow. Production writes stay off until an administrator turns that gate on.
- [Nearzero vs Vercel, Netlify, Coolify, and Dokploy](https://nearzero.dev/compare): Vercel and Netlify own the runtime. Coolify and Dokploy ship Git to a VPS. Nearzero is the control plane for apps, databases, Compose, remote servers, DNS, and HTTPS on machines you own.
- [Nearzero vs Vercel — keep the server](https://nearzero.dev/compare/vercel): Vercel owns the runtime. Nearzero deploys apps, databases, and Compose from Git onto Linux servers you operate.
- [Nearzero vs Coolify — placement, DNS, and a locked-down Agent](https://nearzero.dev/compare/coolify): Both run on your VPS. Nearzero connects placement, optional authoritative DNS, HTTPS, and a policy-bounded Agent in one control plane.
- [Nearzero vs Dokploy — records and metrics on the selected server](https://nearzero.dev/compare/dokploy): Both deploy Docker on your VPS. Nearzero keeps managed records, Community host metrics, and a policy-bounded Agent on the server you selected.
- [Nearzero vs Netlify — a control plane, not an edge for sites](https://nearzero.dev/compare/netlify): Netlify hosts sites on their edge. It is not a Docker, database, or Compose control plane. Nearzero is, on the VPS you already pay for.

## Optional

- [GitHub](https://github.com/Nearzero-systems/nearzero)
- [Issues](https://github.com/Nearzero-systems/nearzero/issues)
- [Full assistant context](https://nearzero.dev/llms-full.txt)