newPloyz Cloud · the managed dashboard is in open beta.

Your apps. Your servers. No compromises.

Git-push deploys, real PR environments with isolated data, database-aware rollback, and multi-server production defaults, without handing your infrastructure to a vendor.

No KubernetesBring your own VPS, NUC, or rackCloud platform, your hardware
ployz · cluster · production

Servers

eu-paris-013
eu-paris-022
us-iad-011
home-rack-013
Cluster topology placeholder
api
web
worker
redis
postgres

Live events

14:02successDeploy api@v412 — healthy
14:01changedPR #284 preview ready
13:58warneu-paris-02 draining
13:55successSnapshot db @v411

Trusted by teams running production on metal they own

veridian.io
northpine
blackpearl labs
quanta cloud
olive & co.
frostsignal
pinecone radio

What stops being your problem

The platform layer, handled.

Five buyer-level promises. Ployz Cloud takes the platform decisions; you take the product decisions.

01deploy

Git-push to productionlike it's somebody else's problem.

Connect a repo. Pick a server. Ship. TLS, health checks, routing, and zero-downtime rollouts come standard — not as something you wire up later.

  • Git-push deploys with build caching
  • Automatic TLS, routing, and zero-downtime rollouts
  • Secrets, env vars, and domains managed in the dashboard
  • Full deploy history with one-click rollback
deploy · api@v412
buildsha 9f2a · 38s
releaseapi@v412
health2/2 ready
routeeu-paris-01 → 100%
02preview

Real PR previewswith real data.

Every pull request gets a full environment: its own URL, its own database forked from production, its own secrets. Reviewers see the change against real data — not an empty staging shell.

  • Per-PR URL, secrets, and isolated database
  • Database branches forked from production in seconds
  • Auto-cleanup on merge — no orphan envs, no surprise bills
  • Promote a preview to production with one click
branches · 4 active
mainprod · 14d
feat/cart-redirectPR #284 · db forked
feat/auth-rewritePR #281 · db forked
fix/timeout-edgePR #277 · db forked
03rollback

Database-aware rollbackapp and state, together.

A bad deploy snapshots both your app and your data. One click restores both — to the exact moment before the change. Recovery stops feeling like an incident.

  • Instant database snapshots before every deploy
  • App and database restored in lockstep — not separately
  • Reliable platform actions — retried for you
  • Time-travel for production: pick a moment, restore
incident · api@v412
release api@v412 · 14:025xx ↑ 17%
rollback
restore api@v411 + db snapshothealthy
04grow

Multi-server by defaultwithout Kubernetes.

Start with one VPS. Add a second when traffic doubles. Add ten when you stop counting. Ployz handles placement, draining, and capacity, without making you hire a platform team.

  • Multi-server, day one, not after a rewrite
  • Mixed arch and locations: x86, ARM, on-prem, cloud
  • Add a server, drain a server, from the dashboard
  • 1 to 200 servers, same dashboard, same workflow
fleet · 5 servers
eu-paris-01
arm · 4c
eu-paris-02
arm · 4c
us-iad-01
x86 · 8c
us-iad-02
x86 · 8c
home-rack-01
x86 · 16c
+ add server
05understand

One dashboardfor the things that broke.

Deploys, health, logs, and incidents in the same place you ship from. No Grafana sidecar, no Loki stack, no extra monthly bill — and no tabs to keep open.

  • Live deploy timeline with logs attached
  • Built-in metrics and structured logs
  • Alerts wired to deploys — not a separate config file
  • Roll back from the same row that flagged the issue
observability · api
14:02api@v412 · 200 OK · 38ms
14:02web · 200 OK · 12ms
14:01worker · job=mailer.send · 220ms

Production defaults, already picked

You make product decisions. Ployz handles the platform.

Nine things every production app needs. None of them should be a sprint.

TLS & routing

Certificates issued, renewed, and routed across servers automatically.

Health checks

New versions only take traffic once they are actually ready.

Database snapshots

A point-in-time copy of your data lives next to every deploy.

PR previews

Each pull request gets its own URL, secrets, and database fork.

Secrets & env vars

Encrypted, scoped per environment, edited from the dashboard.

Multi-server placement

Workloads land on the right server. Drains move them away calmly.

Logs & metrics

Structured logs and per-service metrics, attached to deploys.

Deploy history

Every release is recorded. One click rolls back app and state.

Cleanup & retries

Failed steps retry. Merged previews tear themselves down.

Built to stay up

Written in Rust. Lean on the box. Stable when things break.

A single fast binary with very few moving pieces. Ployz keeps running with its last-known-good state when something upstream goes down, your apps don't notice the control plane having a bad day.

Static stability

If the control plane wobbles, traffic keeps flowing. Nodes hold the last-known-good state until things recover, no thundering reconvergence, no surprise downtime.

Written in Rust

One small statically-linked binary. Predictable memory, predictable CPU. No JVM, no Python venv, no garbage-collection pauses on the path that serves your app.

Minimal moving pieces

No etcd to lose, no operators to babysit, no sidecar agents on every node. Fewer parts means fewer 3 a.m. pages.

Lean on the box

Runs comfortably on a $5 VPS or a Raspberry Pi. Most of your server is for your app, not the platform that runs it.

How Ployz is different

What managed-cloud teaches, on infrastructure you own.

A small honest comparison. We're not the right tool for everyone, but if you've outgrown a single-box panel and don't want to operate Kubernetes, this is your lane.

CapabilityPloyzCoolifyKubernetesVercel / Render
Deploy from a git pushWithout webhooks-and-prayers
YesYesHelm chartYes
Multi-server, day one1 → 200 nodes, same workflow
YesSingle-host firstWith operator hiresVendor-managed
Per-PR preview environmentsWith isolated data + secrets
YesManualWith ArgoCD + scriptsYes
Database-aware rollbackApp and state restored together
YesNoVelero pluginApp only
Database branches per PRFork data along with code
YesNoOperator-dependentBranchable add-on
Runs on your hardwareNUC, rack, mixed arch, on-prem
YesYesYesVendor cloud only
No platform team requiredCloud-like UX out of the box
YesDIY opsOperator hiresYes
Built-in observabilityLogs, metrics, deploys — one place
YesExternalBring your own stackYes
No vendor lock-inOpen-source core, self-hostable
YesYesYesVendor cloud only

Bring your servers.
Bring some peace.

Start with Ployz Cloud and a single server. Grow into a fleet on your terms.

Ployz Cloud is built on the open-source core. Self-host the whole thing whenever you want, no lock-in.