Get PorterWP

Licence the toolkit behind your custom WordPress build.

PorterWP is licensed per production domain. Choose the route that matches your role, confirm who will manage the licence, then continue to checkout.

Choose your path

The same licence, with different decisions before checkout.

DEVELOPER

Starting a custom theme project?

Confirm the production domain and whether your practice or the client will own the licence account. Review the current technical requirements before you build.

  • WordPress 6.4 or newer
  • PHP 8.2 or newer
  • ACF Pro 6.6 or newer when using the starter’s ACF Blocks v3 scaffold

Review the developer workflow

SITE OWNER

Following a developer recommendation?

Ask who will own the account, manage activation and handle updates. Confirm that PorterWP is intended for your live domain before purchasing.

  • Record the account owner
  • Confirm the production domain
  • List any other separately licensed project software

Read the site owner guide

Before checkout

Make the ownership decision explicit.

A licence is easier to manage when the project records who controls the account, which production domain it covers, and who is responsible for activation and updates.

PorterWP does not include an off-the-shelf theme or bespoke development. ACF Pro and other third-party project software are separate products with their own terms.

What happens next

From purchase to production.

01

Complete checkout. Use the account details agreed for the project.

02

Install and activate PorterWP. The person managing the build connects the licensed plugin to the production site.

03

Connect the theme. PorterWP reads the project’s theme configuration and loads the features the developer has enabled.

04

Document responsibility. Keep account ownership and the site’s update process in the project handover notes.

Ready to licence PorterWP?

Continue when the production domain and account owner are agreed.

The existing Licence terms remain available separately.