Fleet

From one machine to a small fleet.

No Kubernetes. No separate control plane. Install a daemon, add machines over SSH, and your services span the fleet.

Get startedSelf-hosted pricing

Start with one machine

Install the Ployz daemon on any Linux server. Your services run there. The environment canvas gives you the same view you would get on the cloud.

Single serverCLI installNo cloud required
CLI
# On your server
npx ployz daemon install
ployz mesh init

Add a second machine

When one server is not enough, add another over SSH. Ployz provisions the daemon, joins it to the mesh, and makes it available for workloads.

SSH provisioningAuto mesh joinReadiness check
CLI
# From your local machine
ployz machine add \
  --host 10.0.0.2 \
  --user ubuntu

Mesh formation

New machines join the overlay network automatically. Services can be scheduled across the fleet and still reach each other by name.

Automatic mesh joinCross-machine DNSOverlay networking
CLI
# Machine is ready
node-2 joined mesh: acme-prod
Services: api, worker → node-1
Postgres → node-2

Fleet overview

acme-prod fleet
2 machines, 4 services
node-1Primary
Ready
apiworker
node-2Secondary
Ready
postgresredis
Roadmap

This is the platform, not a separate product.

Fleet is the natural continuation of the single-machine install. Add machines when you need them. The same environment canvas, same service config, same CLI — just more capacity. No migration, no replatforming.

Run your own fleet

Start with one server. Grow when you need to.

Read the docsView pricing