Ployz

dev.ployzPublished by ployz.devOfficial publisherv1.0.0Updated Oct 24, 2026

Deploy apps, databases and previews to your own servers. Run Ployz Cloud from your agent.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Ployz Cloud MCP server that lets an assistant deploy apps, databases and per-pull-request preview environments to Linux servers you rent.

What you can do
  • Deploy apps and services to your own servers, building the app and giving it an https address
  • Create and manage environments, including a preview per pull request with its own seeded database
  • Copy or sync services and settings between environments, such as production to a branch and back
  • Stage changes as drafts so a person can review the diff before deploying
  • Manage servers joined into one private network, with services running across them
When to use it
Useful when you rent your own Linux servers and want hosted-platform-style deploys, preview environments per pull request and database services driven from a coding agent, while keeping review before anything goes live.
Requirements
Remote streamable HTTP endpoint at ployz.dev with OAuth sign-in required. Your own Linux server reachable as root over SSH with systemd, plus Docker on it. The README's agent setup also installs the Ployz CLI and skill and signs you in.
Before you install
The agent acts on real production infrastructure: it can deploy, copy and sync environments, and a shared database can expose production data to a preview. Destructive changes to services, volumes or domains wait for human approval and an agent cannot approve them. No offsite backups or automatic failover yet, and your hosting provider bills you for the servers.

Installation

In SourceWeft

  1. Open Ployz in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.ployz%2Fployz/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ployz": {
      "type": "http",
      "url": "https://ployz.dev/mcp"
    }
  }
}

README

[Ployz]

Ployz

Rent a server. Get a cloud.
Preview environments on servers you own. One command from a fresh server to https.

Website · Quick start · Agents · Status · Self-host

Ployz turns Linux servers you rent into a deployment platform. It builds your app, gives it an https address and runs its databases and workers next to it. Every pull request can get its own environment. Start with one server and add more when you need them.

The workflow of the hosted platforms you like, on servers you rent.

[Logos of Vercel, Railway, Fly.io, Render, Netlify and Heroku]
Six hosted platforms. Ployz isn't affiliated with any of them.

What's different

  • An environment for every pull request. Each preview runs the pull request's code at its own https address. Copy the database service and the preview gets its own empty database, seeded by your setup command. A database you leave shared gives the preview production data. On merge, production gets the code and the preview's setting changes. The Ployz · ready to merge check lists those changes on the pull request first.
  • Review before you deploy. Edits from the dashboard, the CLI or an agent wait as a draft. You read the diff, then deploy it.
  • The CLI does what the dashboard does. Commands print JSON with --json. A change that would delete a service, a volume or a domain stops until a person approves it. An agent can't approve it.
  • One private network across your servers. Add a server with ployz server add. Your servers share a WireGuard network, and a service runs up to 50 replicas across them. A service with a volume runs on the server that holds its data, one replica by default.
  • Apps that outlive Ployz Cloud. Your apps keep running on your servers if Ployz Cloud is down or goes away. The engine and the dashboard are open source.

Use it with your agent

Paste this into your coding agent.

text
Set me up for Ployz: https://ployz.dev/agents.md

It installs the CLI and the Ployz skill, signs you in and registers the Ployz MCP tools. From then on it runs the same commands you would.

text
> Copy production with its own worker, deploy it there, then stage it back.$ ployz env branch try-worker --copy worker   # Made Branch shop/try-worker of production.$ ployz deploy --env try-worker               # 2 deployed · across 1 server$ ployz env sync --env try-worker --to        # Synced try-worker → shop/production.

The change waits in production for you to review and deploy.

Quick start

You need a Linux server with systemd that you can reach as root over SSH. See the server requirements.

  1. Install the CLI.

    sh
    curl -fsSL https://ployz.sh | sh

  2. Sign in to Ployz Cloud.

    sh
    ployz login

  3. From your app's directory, point Ployz at your server.

    sh
    ployz up --server root@your-server

    Ployz installs itself on the server, builds your app and prints its https address.

  4. Deploy on every push, and give each pull request a preview with its own seeded database.

    sh
    ployz github connect                # install the Ployz GitHub Appployz set shop.repository=you/shop  # build from GitHub instead of uploadsployz deployployz env pr you/shop --on --from production --copy postgres --setup 'shop=pnpm db:seed'

    ployz up names the service after your app's directory, here shop. The preview copies a postgres service you've added.

How it works

Each server runs a small Ployz daemon next to Docker. Your servers share a WireGuard network and keep each other up to date. Every server serves https itself through Caddy, so there's no load balancer to rent. The dashboard and the CLI tell your servers what to run. Once deployed, your apps depend on neither. Generated ployz.app addresses use Ployz's DNS. A custom domain with an A record pointing at your servers doesn't.

Status

Can I move a production app? Yes, if the gaps below are fine for you. If you need managed backups and automatic failover today, wait. Ployz is young and changes quickly. Work through the production checklist first.

  • You look after the OS. Ployz doesn't install OS updates.
  • No offsite backups yet. Volume mirrors keep a copy on another server. Dump your databases on a schedule and keep the dumps off your servers, or keep your hosted database.
  • No automatic failover. If a server dies, what ran only there stops. Replicas on other servers keep running.
  • No Docker Compose files. Add each container as its own service.
  • Alerts are email only. Ployz Cloud emails you when a service goes down or crashes.

Soon: offsite backups, automatic rollbacks, and moving a database to a bigger server without downtime.

Pricing

Ployz is free on your own servers, custom domains included. Paid Ployz Cloud plans are coming soon. Your hosting provider bills you for the servers.

Self-hosting the dashboard

Run the dashboard yourself instead of Ployz Cloud. See dashboard/README.md.

How Ployz is built

Agents write most of Ployz. I design the loop they run in, and I answer for what comes out of it.

Every change ships as a small PR. The agent has to prove it by running Ployz the way you would, on real servers. If it can't show me that, it doesn't merge. Low-risk PRs merge once the checks pass. The orchestrator, networking and anything touching your data get a human review first.

When an agent gets something wrong, we turn the mistake into a lint rule or a test. Every mistake makes the system stricter, and that's the part I trust.

Contributing

Bug reports and feature requests go in GitHub Issues.

The repository holds two projects. core/ is the engine, CLI and daemon, in Rust. dashboard/ is Ployz Cloud, in TypeScript. Each README explains how to build it.

License

The engine in core/ is Apache-2.0. The dashboard in dashboard/ is AGPL-3.0.

Source: README.md at commit 33e1860

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.