Open source
Inspect it. Run it on your own VPS.
Ship software without giving up your infrastructure.
Nearzero is the control plane for apps, databases, and Compose on your Linux VPS. Place the work, point the hostname, get HTTPS.
Nearzero is the control plane for apps, databases, and Compose on your Linux VPS. Place the work, point the hostname, get HTTPS.
Inspect it. Run it on your own VPS.
Containers, databases, Compose, and Swarm.
Build, route, and get a certificate.
Run here, or on another server you add.
Pick the server, repo, runtime, and domain. Nearzero keeps those choices together.
Use a dedicated Linux VPS. Finish setup on your own HTTPS admin URL.
Keep work on that host, or add more Linux servers over SSH.
GitHub, GitLab, Bitbucket, or Gitea. Branch and build commands stay with the app.
Env values, port, storage, or a database before you build.
Build on the selected server. Point the domain. Traefik handles HTTPS.
Logs, deploys, domains, and servers stay together. The Agent can look with you.
You still patch, back up, and size the VPS. Nearzero builds, deploys, and routes.
Git, SSH, builds, DNS, TLS, and logs usually live apart. Nearzero keeps them attached to the app.
The repo is in Git. Runtime is on a server. DNS and certificates live somewhere else.
Your team spends less time reconstructing context and more time shipping.
The Agent can read deploys, logs, domains, and servers. It can only change what your account is allowed to change.
Deploy the API to the production server and put it on our managed domain.
Which environment should receive this deployment?
The Agent reads projects, deploys, logs, domains, and servers already in Nearzero.
Current contextIf a request is missing an environment, server, domain, or repo, it asks.
Explicit inputsIt picks bounded platform actions and explains them before changing anything.
Plan and verifyEvery action still needs your role and workspace policy. Production stays off until you turn it on.
Controlled authorityYour role still has to allow the action. Turning on production writes is a separate workspace setting, not something hidden in a prompt.
Start on one server. Add remote capacity when you need it. The workflow stays the same.
Connect a repo, pick a server, set env values, and deploy.
Open the deploy, follow the logs, and take the next step without rebuilding the picture.
Connect remote hosts and place apps, databases, and Compose where they should run.
Point DNS at the host that actually runs the app. Traefik routes it and Let’s Encrypt covers TLS.
Nearzero can serve a managed zone. Bind it to an environment and each service record targets the selected server.
api.example.com? A 203.0.113.20 203.0.113.20:443 TLS · :3000 Apps, databases, and stacks on servers you already have. Add another host when one is not enough.
Node, Python, Go, PHP, Ruby, and other container apps. Pick the server, then ship the repo.
Run them next to the app, or on another server you add.
Ship a multi-service stack on one host. Add Swarm nodes when that host is not enough.
Back up managed databases so a bad deploy is not a lost dataset.
CPU, memory, disk, and network on the hosts you added.
Trigger deploys from the API. Send alerts to a channel you already use.
Install, architecture, remote servers, DNS, HTTPS, and Agent safety. Then compare Nearzero with the tools you already know.
Install the control plane, then take Git to HTTPS
Open GuideYour servers run the apps. Nearzero is the control plane.
Open GuideVerify the installer, set DNS, claim the first owner
Open GuideAdd a Linux VPS and send traffic straight to it
Open GuidePoint the hostname at the server that runs the app
Open GuideIt can see your infra. Production writes start off.
Open CompareVercel, Coolify, Dokploy, and Netlify — what you keep, and what you give up.
All comparisonsInstall it yourself. Book a call only if you want help choosing the path first.
Use a Linux VPS you already have. The guide covers setup, DNS, HTTPS, and the first deploy.
If you would rather map servers and DNS with a human before you install, we can do that in 30 minutes.
Short answers about installing Nearzero and running it on servers you own.
General
Nearzero is open-source software you install on your own Linux server. You use it to deploy apps and databases to that server, or to other servers you add.
Yes, if you want to deploy from Git on machines you own. You still run those machines. Nearzero does not give you Vercel’s global CDN.
Yes. You can self-host the Community edition for free. You still pay for your VPS, storage, and domain.
All three run on your VPS. Nearzero keeps apps, databases, extra servers, optional DNS, HTTPS, and a locked-down Agent in one control plane.
Platform
Use a dedicated Linux VPS. Download the installer, check the SHA-256 checksum, read the script, then run it. Finish setup on your own HTTPS admin URL.
Most container apps, including Node, Python, Go, PHP, and Ruby. Databases include Postgres, MySQL, MariaDB, MongoDB, Redis, and libSQL. Docker Compose works too.
Yes. Point your domain at the server. Nearzero uses Traefik and Let’s Encrypt. Ports 80 and 443 need to be open.
Yes. Keep Nearzero on one server, add other Linux servers over SSH, and pick where each app runs. Public traffic can go straight to that server.
Operations
No. The Agent can read logs and project state, but it can only make a change if your account is allowed to. Production changes stay off until you turn that on.
Yes. You still patch, back up, and size the VPS. Nearzero builds, deploys, and routes. You keep the servers healthy.