Deploy

Three ways to deploy. One interface.

Git, image, or manifest — configure your source once and deploy as often as you need.

Start deploying

Deploy from Git

Connect a GitHub repository. Ployz builds and deploys on every push to your configured branch. Set the root directory, build command, and start command.

Branch selection
Root directory
Build command
Start command
Preview per branch
Config
# Auto-detected from repo
Branch:       main
Root dir:     ./
Build cmd:    npm run build
Start cmd:    node dist/server.js

Deploy from an image

Pull any public or private container image. Configure registry credentials once, reference your image by tag or digest. No build step required.

Public and private registries
Registry credentials
Tag or digest pinning
Pull-on-deploy
Config
Image:  ghcr.io/acme/api:v1.4.2
Auth:   registry-credentials/prod

Deploy from a manifest

Paste or upload a service manifest to define ports, commands, environment references, and resource hints in a single file.

Portable config format
Env variable references
Port definitions
Command overrides
Config
name: api
image: ghcr.io/acme/api:latest
port: 3000
env:
  - DATABASE_URL
  - REDIS_URL

Everything that goes into a service

Ports
Expose HTTP or TCP ports. Mark as public or internal-only.
Variables
Set plain environment variables per service, per environment.
Secrets
Store sensitive values encrypted. Reference them like any other variable.
Health check
Configure an HTTP path and timeout for deploy readiness.
Commands
Override build, start, and pre-deploy commands.
Registry credentials
Attach stored credentials to pull from private registries.
Deploy preview

Know what changes before it runs.

Before each deploy, Ployz shows a diff of what is changing: image tag, environment variables, commands, and port config. Review it, then confirm.

Deploy diff
api-service → production
−image: api:v1.3.1
+image: api:v1.4.0
−PORT=3000
+PORT=8080

Ready to deploy?

Open CloudRead the docs