Name: Deploy Forge
Brand: Deploy Forge
Price: 5 USD
Availability: InStock

Question 1

How does Deploy Forge actually deploy my theme?

Accepted Answer

When you push to GitHub, Deploy Forge triggers a GitHub Actions workflow that builds your theme (running npm install, compiling assets, etc.). The built artifact is then securely downloaded by our lightweight WordPress plugin and deployed to your theme directory—no FTP, no SSH, no manual file uploads.

Question 2

Does it work with my WordPress host?

Accepted Answer

Yes. Deploy Forge works with any host that runs WordPress and PHP—shared hosting, managed WordPress hosts like WP Engine or Flywheel, VPS, or dedicated servers. Our plugin uses standard PHP filesystem operations, so no SSH access or special server configuration is required.

Question 3

What happens if a deployment breaks my site?

Accepted Answer

Every deployment automatically backs up your current theme before replacing it. If something goes wrong, you can instantly roll back to a previous version with one click from your dashboard. Deploy Forge keeps your most recent backups available for rollback. Your site is never left in a broken state.

Question 4

Is there a free trial?

Accepted Answer

Yes—all plans include a 30-day free trial with full access to every feature. A credit card is required to start the trial, but you won't be charged until the trial ends. Cancel anytime before that to avoid being billed.

Question 5

Can I deploy to staging and production separately?

Accepted Answer

Yes. Every site in Deploy Forge lets you choose which branch to deploy from. You can connect the same repository to two sites—one deploying from your develop branch to staging, and another deploying from main to production. This works on all plans.

Question 6

What access does the WordPress plugin have?

Accepted Answer

The plugin only writes to your WordPress theme directory. It communicates with Deploy Forge's API using an encrypted API key, and all webhook payloads are verified with HMAC SHA-256 signatures. The plugin doesn't modify your database, other plugins, or core WordPress files.

Question 7

Can I use this for client sites as an agency?

Accepted Answer

Absolutely. The Pro plan supports up to 5 team members and 50 sites, while the Agency plan offers unlimited team members and 100 sites. Only your team can connect repositories and manage deployments—clients never need access to the Deploy Forge dashboard.

Question 8

Why not just use FTP to deploy my theme?

Accepted Answer

You can—but FTP means manually uploading files every time you make a change, with no version history, no rollbacks, and no way to know what's actually live on the server. Deploy Forge gives you push-to-deploy automation, automatic backups before every deployment, instant rollbacks, and a full deployment history. Once you ship a broken change over FTP at 11pm and have no backup, you'll wish you had this.

Question 9

Do I need to use GitHub Actions?

Accepted Answer

No. Deploy Forge supports two deployment methods: GitHub Actions (recommended) and Direct Clone. With GitHub Actions, your theme is built in CI before deploying—great for themes that need an npm build step. With Direct Clone, the WordPress plugin pulls your repository directly from GitHub, which works well for simpler themes that don't require a build step. You choose your method during site setup.

Question 10

How long does it take to set up?

Accepted Answer

Most users are deploying within 10 minutes. Sign up, install our WordPress plugin on your site, connect your GitHub repository through our setup wizard, and push your first deployment. The wizard generates the GitHub Actions workflow file for you automatically.

Question 11

Does the plugin slow down my WordPress site?

Accepted Answer

No. The plugin is lightweight and only activates when receiving a deployment webhook from Deploy Forge. It adds no overhead to your site's front-end performance—it doesn't load scripts, stylesheets, or run on page loads.

Question 12

What happens to my sites if I cancel?

Accepted Answer

Your WordPress sites continue to work normally—we never touch your live site content, database, or hosting. You simply lose the ability to deploy via GitHub. Your theme stays exactly as it was on your last deployment.

Question 13

Do I need to build my theme locally before pushing?

Accepted Answer

No. Deploy Forge runs your build step (npm install, npm run build, etc.) in GitHub Actions before deploying. Your repository stays clean—no compiled CSS, bundled JS, or node_modules in your repo. Just push your source files and we handle the rest.

Question 14

Can I upgrade or downgrade my plan?

Accepted Answer

Yes. You can change your plan at any time from the dashboard. Upgrades take effect immediately, and downgrades take effect at the start of your next billing cycle. All plans are month-to-month with no long-term commitment.

Question 15

Does Deploy Forge work with WordPress plugins or just themes?

Accepted Answer

Deploy Forge is currently focused on theme deployments. We're exploring plugin deployment support for the future. If you're building a custom theme that includes plugin-like functionality, it works great for that.

Question 16

Do you offer discounts for open source projects, students, or nonprofits?

Accepted Answer

Yes—we're happy to support open source developers, students, and nonprofit organizations. Reach out to us at support@getdeployforge.com with details about your project and we'll work something out.

Features	Hobby	Pro	Agency
Connected WordPress Sites	5	50	100
Team Members	1	5	Unlimited
Multi-Branch Deployments
GitHub Actions Deployments
Instant Rollbacks
Early Access to New Features
Asset Compilation (npm build)
HMAC-Signed Webhooks
Zero-Config Setup Wizard
Works on Any WordPress Host
Support	Community	Email	Priority

Simple pricing for
every team

Hobby

Pro

Agency

Feature Comparison

Frequently Asked Questions

Start your 30-day free trial

Simple pricing for every team