Skip to content
WP Deploy
Join early access
Early access

A theme release workflow that starts where you build.

wp-deploy is foundation-stage software for freelancers and WordPress theme developers: signing, manifests, admin key management, allowlists, and doctor checks exist today while direct deployment remains planned.

Join early access See the architecture
Foundation livenorthstar-theme.zip
Theme identitynorthstar / 1.4.0
Package manifestValid
Theme accessAllowlisted
Package uploadPlanned
Built around theme work

One package model for the themes you maintain.

The MVP stays deliberately focused on complete WordPress themes. Current foundations help prove identity, authorization, readiness, and scope before deployment operations arrive.

Standalone

Custom theme projects

Build a complete production package, validate its identity and requirements, then target the allowlisted theme slug.

Parent theme

Shared theme foundations

Treat a parent theme as its own deployment target with separate packages, history, and recovery boundaries.

Child theme

Client-specific customization

Validate the declared parent and preserve the stylesheet/template activation relationship during planned recovery.

Clear responsibilities

Your project defines the build. wp-deploy defines the handoff.

The tool does not replace source control or decide how your assets are built. It packages the production result and gives WordPress a validated, authenticated release request.

On the developer machine

  • Run project-specific production builds
  • Apply package inclusion/exclusion rules
  • Generate the manifest and checksum
  • Sign requests with the local private key

Inside WordPress today

  • Register, scope, expire, and revoke public keys
  • Allowlist installed theme targets
  • Expose capability and setup-readiness checks for doctor

Planned inside WordPress

  • Revalidate every uploaded package as untrusted input
  • Persist deployment operations and status history
  • Select a capability-appropriate deployment driver
Current status

Use what exists. Follow what comes next.

Key generation and request signing

Ed25519 CLI primitives and cross-language canonical signing fixtures.

Implemented
Manifest validation

Schema and semantic checks for package identity, paths, files, and requirements.

Implemented
Admin key and theme control plane

Register public keys, revoke access, allowlist installed themes, and check setup readiness.

Implemented
CLI doctor and standalone build proof

Doctor checks HTTPS connectivity, API compatibility, capabilities, and readiness; Linux x64 standalone packaging has been validated.

Implemented
Deploy, history, and rollback commands

Authenticated upload, background operation, status, health checks, and theme recovery.

Planned MVP
Developer boundaries

Focused scope means clearer guarantees.

MVP theme work

  • Standalone themes
  • Parent and child themes
  • Complete production ZIP packages
  • Local Git as optional source control metadata

Not the MVP

  • Plugin, core, or content deployment
  • Database or options migration
  • Individual changed-file syncing
  • GitHub-triggered deployment
Early access

Bring a real theme workflow into Early access.

Tell us whether you build standalone, parent, or child themes and what hosting environments matter most.

Join developer early access