Platform

Ploy turns a Git repository into running deployments. Pick a source, add a ploy.yaml, and every push builds and deploys. This section covers everything around that loop: where your code comes from, how a project is configured, how environments and secrets reach your build and runtime, and how branches, monorepos, and templates map to deployments.

How a deployment works

1. Push to a connected GitHub repository or to a Ploy Git repository.
2. Ploy reads ploy.yaml at the pushed commit to find the project kind, build command, output directory, and bindings.
3. The build runs with your dashboard environment variables available, and the result is uploaded.
4. The deployment goes live: pushes to the production branch replace production, and every other branch gets a preview deployment with its own URL.
5. Roll back by redeploying any earlier deployment from the dashboard.

Pushes can be skipped per branch pattern or commit-message marker with the deploy section of ploy.yaml, or from Project Settings → Preferences → Deploy Rules.

Project types

kind in ploy.yaml tells Ploy how to build and run a project:

kind: dynamic
build: pnpm build
out: dist
db:
  DB: default

Bindings such as db, queue, workflow, cron, ai, and auth are declared next to the build settings. The full reference is on the Configuration page.

In this section

Related

• CLI — ploy dev runs your project locally with emulated bindings; ploy push and ploy git work with Ploy Git repositories.
• Self-hosting — run the whole platform on your own infrastructure.