Skip to content
Your servers. One deployment workflow.

Ship software without giving up your infrastructure.

Nearzero turns your servers into a deployment platform. Connect Git, deploy applications and databases, publish HTTPS domains, and troubleshoot from one control plane.

Book a technical walkthrough See the self-hosting guide
A deployment in Nearzero Repository to live service
Live
01
SourceConnect a repository
02
BuildBuild on your server
03
RunStart the application
04
PublishRoute the domain with HTTPS
Running on your server api.production.example.com HTTPS
Open source A self-hosted control plane you can inspect and operate
Apps + data Applications, databases, Compose, and Docker Swarm
Git to HTTPS Builds, routing, managed DNS, and Traefik TLS when ingress is ready
Remote ready Place workloads on local or connected servers
A repeatable path to production

Connect. Configure. Deploy.

Choose the server, repository, runtime, and domain. Nearzero keeps those decisions together so the next deploy follows the same path.

  1. 01

    Run the control plane

    Self-host Nearzero on a dedicated host, then keep the console behind a trusted management boundary.

    Projects, policy, DNS, and deployment state have one home.
  2. 02

    Connect your servers

    Use the local host or add remote servers over SSH. Nearzero prepares Docker, Traefik, builds, and monitoring for the workload host.

    You choose where each application and database runs.
  3. 03

    Bring a repository

    Connect GitHub, GitLab, Bitbucket, or Gitea, select a branch, and review the detected or explicit install, build, and start commands.

    Source and deployment settings stay attached to the service.
  4. 04

    Configure the runtime

    Add environment values, choose an application port, attach storage, or deploy a database or Docker Compose stack beside the application.

    The runtime is described before a build is started.
  5. 05

    Deploy and publish

    Build on the selected server, create the Traefik route, and connect a custom or managed hostname after DNS resolves to that server.

    The application moves from Git to HTTPS when DNS and ingress prerequisites are ready.
  6. 06

    Operate with context

    Inspect logs, deployment state, domains, servers, and metrics directly—or ask the Agent to investigate using only actions your role allows and administrator-controlled policy permits.

    Operations keep the same context as the original deployment.
The practical difference

Nearzero owns the workflow. You keep the infrastructure.

That trade gives you control over workload placement and the storage infrastructure you choose, but it also leaves your team responsible for host security, capacity, backups, and control-plane availability.

Read the self-hosting guide
The problem

Shipping on your own servers becomes tool switching.

Git SSH Builds DNS TLS Logs

Every deployment and incident starts by piecing the system together again.

The Nearzero solution

One control plane keeps the application and infrastructure connected.

N One operational workspace
  • Deploy from Git to the selected server
  • See builds, runtime state, and logs together
  • Keep domains and HTTPS attached to the service

Your team spends less time reconstructing context and more time shipping.

Infrastructure help with a permission model

Ask for the outcome. Keep control of every action.

The Agent can investigate deployments, logs, domains, and servers without making you gather the context first. It asks before guessing and can act only when user permissions and workspace policy allow it.

N AgentInfrastructure workspace
production writes: disabled
You

Deploy the API to the production server and put it on our managed domain.

Nearzero Agent

Inspected project and recent deployments

Checked available servers and domain zones

Missing the target production environment

Which environment should receive this deployment?
production staging
Ask Nearzero about your infrastructure…
01

See the current state

The Agent reads the projects, deployments, logs, domains, and servers already recorded in Nearzero.

Current context
02

Ask before guessing

If a request is missing an environment, server, domain, or repository, the Agent asks for it.

Explicit inputs
03

Build a safe plan

It selects bounded platform actions and explains the concrete operation before changing infrastructure.

Plan and verify
04

Stay inside policy

Every action must pass the user's role, administrator policy, and the separate production gate.

Controlled authority
Built-in boundary

Production mutations start disabled.

The requesting user still needs the underlying role access, and administrators choose which Agent capabilities are available for the organization. Enabling production actions is a separate, deliberate workspace setting—not an assumption hidden in a prompt.

Read the Agent safety model →
One operational loop

From first deploy to everyday operations.

Start with a single server. Add remote capacity and services when you need them. The application-centered workflow stays familiar.

Ship

Git to a running application

Connect a repository, detect the build path, choose a server, configure environment values, and deploy.

Git Build Deploy
Operate

Understand a failed deployment

Inspect deployment context, follow the relevant logs, and narrow the next step without rebuilding the system picture.

Context Logs Next step
Extend

Add infrastructure without changing workflows

Connect remote servers, place workloads deliberately, and keep applications, databases, and Compose services in one control plane.

Server Workload Route
Domains that follow the workload

From delegated DNS to HTTPS, connected to the right server.

Nearzero can serve an authoritative managed zone from the control plane. Bind that zone to an environment and service records target the selected local or remote server.

  • CoreDNS answers managed authoritative zones
  • Each service record points to its selected server
  • Traefik routes the hostname and manages HTTPS
Read the remote-server DNS guide
01 · Resolve Public resolver api.example.com?
02 · Answer Nearzero CoreDNS A 203.0.113.20
03 · Connect Remote server 203.0.113.20:443
04 · Route Traefik → API TLS · service:3000
DNS authoritative HTTPS active
A complete deployment control plane

Applications, data, routing, and operations. Connected in one place.

Run common application infrastructure without giving up control of the servers underneath it.

01

Application runtimes

Deploy Node.js, PHP, Python, Go, Ruby, and other container-ready applications.

02

Six database engines

Run PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and libSQL services.

03

Compose and Swarm

Deploy multi-service Docker Compose stacks and expand across Docker Swarm nodes.

04

Backups and monitoring

Back up Nearzero-managed application database services to external storage and view CPU, memory, storage, and network metrics.

05

Routing and certificates

Use built-in Traefik routing with managed service domains and HTTPS certificate assignment.

06

API and notifications

Manage deployments programmatically and connect Slack, Discord, Telegram, email, and other notification channels.

Choose the right operating model

Know what you manage and what the platform manages.

Compare infrastructure ownership, deployment workflows, and day-to-day operations before choosing a platform.

View all comparisons
Managed infrastructure

Nearzero vs Vercel

Compare a globally managed application platform with a self-hosted Docker control plane for infrastructure you operate.

Compare operating models Managed web platform

Nearzero vs Netlify

Compare managed edge delivery, functions, and deploy previews with long-running workloads on your own servers.

Compare operating models Self-hosted PaaS

Nearzero vs Coolify

Compare Git, Compose, previews, remote servers, DNS ownership, and day-two operations across two self-hosted platforms.

Compare operating models Self-hosted PaaS

Nearzero vs Dokploy

Compare Docker and Swarm, remote and build servers, domains, monitoring, and governance across two self-hosted platforms.

Compare operating models
Straight answers

Understand the operating model before you install.

What runs on your servers, what Nearzero controls, and what remains your responsibility.

Explore the documentation
01 Where does Nearzero run?

Nearzero is self-hosted. The control plane runs on infrastructure you choose and can manage workloads on its local host and connected remote servers.

02 How is Agent access controlled?

The Agent can work with Nearzero context such as projects, deployments, logs, domains, and servers. Every mutation still requires the requesting user's authorization and administrator-controlled permission for that action. Production mutations also require a separate gate and are disabled by default.

03 How do domains work across remote servers?

Bind an environment to a Nearzero-managed DNS zone and each service record can target its selected server. Public traffic reaches Traefik on that server, which routes the hostname to the service.

04 Does Nearzero provide HTTPS?

Managed service domains use Let's Encrypt through Traefik after the public A record resolves to the selected server, TCP 80 is reachable for HTTP-01 validation, TCP 443 is reachable for HTTPS, and any CAA records permit letsencrypt.org.

05 What can I deploy?

Applications, PostgreSQL, MySQL, MariaDB, MongoDB, Redis, libSQL, and Docker Compose stacks are supported. Docker Swarm is available for multi-node operation.

06 Is Nearzero an alternative to Vercel, Netlify, Coolify, or Dokploy?

It can be, when your priority is running applications, databases, and Compose workloads on servers you control. Vercel and Netlify remove more infrastructure work through managed platforms, while Coolify and Dokploy already provide capable self-hosted PaaS workflows. Nearzero connects workload placement, domains, HTTPS, monitoring, and optional policy-bounded Agent assistance in one self-hosted control plane.

07 How should I install Nearzero?

Choose a published Nearzero release, download its installer and SHA-256 file, verify the checksum, review the script, and only then run it. The self-hosting guide keeps the release version explicit and covers the security boundary.

See it on your infrastructure

Ask for the outcome. Nearzero helps execute the work.

See how the Agent uses live project context to inspect, plan, and perform permitted actions across deployments, servers, domains, and logs.

Book a technical walkthrough Self-host Nearzero
What we cover in the walkthrough

1 Your current deployment bottleneck

2 Server, network, and DNS requirements

3 A repository-to-HTTPS deployment path

4 Whether Nearzero fits your operating model

No generic sales deck Book the call →