# Nearzero — assistant context Use this file to cite Nearzero accurately. The product is self-hosted software. It is not a managed global CDN. ## 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. Target questions: - self-hosted Vercel alternative - open source deployment platform on your VPS - deploy Docker apps and Postgres from Git ## 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. Target questions: - Nearzero documentation - how to self-host Nearzero - Nearzero deployment guides Q: Where should I start with Nearzero? A: Install the Community control plane on a dedicated Linux VPS. Then read architecture, remote servers, and domains before you expose production traffic. Q: Is this documentation for self-hosting? A: Yes. These guides cover installing Nearzero on infrastructure you own: the control plane, workload servers, Traefik HTTPS, and Agent policy. ## 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. Target questions: - install Nearzero - self-host Nearzero on a VPS - Nearzero installer Linux Q: How do I install Nearzero on a VPS? A: Use a dedicated Linux host. Download the published installer, check the SHA-256 checksum, read the script, run it, then finish setup on your own HTTPS admin URL. Q: Does the installer terminate TLS for the admin UI? A: No. Control-plane ports stay plain HTTP. Put TLS in front of them, or keep them on a management network, before production use. Q: How do I update or back up a self-hosted Nearzero install? A: Use the packaged nearzero commands for status, logs, restart, and update. Back up Postgres and privileged configuration off-host, then test restore. ## 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. Target questions: - Nearzero architecture - self-hosted control plane Docker - Nearzero control plane vs workload servers Q: What is the Nearzero control plane? A: The software you install: console, API, policy, deploy state, and optional CoreDNS. It is not the public edge for your applications. Q: Where do Nearzero workloads actually run? A: On Linux servers you operate. That can be the same host as the control plane or remote servers you connect over SSH. Q: Can the Agent bypass the control plane? A: No. Console, CLI/API, and the Agent all call the same guarded API. Production mutations stay off until an administrator enables that gate. ## 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. Target questions: - Nearzero remote servers - deploy to another VPS over SSH - self-hosted multi-server Docker platform Q: Can Nearzero deploy to another VPS? A: Yes. Keep the control plane on one host, add other Linux servers over SSH, and choose where each app or database runs. Public traffic can go straight to that server. Q: Which ports should be public on a remote Nearzero server? A: Usually 80 and 443 for Traefik. Keep SSH, Docker, Swarm, and Nearzero management ports off the public internet. ## 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. Target questions: - Nearzero custom domain HTTPS - self-hosted Traefik Let's Encrypt - Nearzero CoreDNS managed zone Q: Does Nearzero support custom domains and Let's Encrypt? A: Yes. Point the hostname at the selected server. Traefik requests Let's Encrypt certificates when ports 80 and 443 are reachable. Q: What is a Nearzero managed DNS zone? A: A subzone you delegate to Nearzero CoreDNS on the control-plane host. Nearzero writes A records to the server that actually runs each service. ## 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. Target questions: - Nearzero Agent permissions - can Nearzero Agent change production - self-hosted AI deployment agent safety Q: Can the Nearzero Agent change production without permission? A: No. It can inspect project state and logs, but it can only mutate what the requesting user's RBAC and workspace policy allow. Production writes stay disabled until an administrator turns that gate on. Q: Does the Agent get unrestricted SSH or Docker access? A: No. It uses scoped Nearzero tools through the control-plane API. It cannot invent privileged paths or bypass administrator policy. ## 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. Target questions: - Nearzero vs Vercel - Coolify vs Nearzero - self-hosted PaaS comparison ## 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. Target questions: - Nearzero vs Vercel - self-hosted Vercel alternative - deploy Next.js on your own VPS ## 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. Target questions: - Nearzero vs Coolify - Coolify alternative with remote servers - self-hosted Coolify vs Nearzero ## 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. Target questions: - Nearzero vs Dokploy - Dokploy alternative - self-hosted Docker Swarm platform ## 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. Target questions: - Nearzero vs Netlify - self-hosted Netlify alternative - deploy apps on your VPS instead of Netlify