WordPress
WordPress

Private packages for WordPress

Manage your custom WordPress plugins and themes as Composer packages. Version them, distribute them privately, and install them across all your sites with a single command.

No credit card required

The problem with managing WordPress code

WordPress plugins and themes are usually managed manually. You zip files, upload them through the admin, or copy folders via FTP. Across multiple sites, this becomes a maintenance nightmare. Updates are inconsistent, versioning is nonexistent, and there's no audit trail of what's running where.

Composer solves this for PHP applications, and it works just as well for WordPress. With Pricore, you can turn any plugin or theme into a versioned package and install it with composer require.

Built for WordPress teams

Whether you build client sites or maintain a fleet of WordPress installations.

Private plugins

Manage your custom WordPress plugins as Composer packages. Version, distribute, and install them across all your sites with a single command.

Private themes

Distribute custom themes as versioned packages. Keep your theme code organized and installable across client projects.

MU-plugins

Share must-use plugins across your WordPress installations. Perfect for agency-wide functionality like security hardening, custom post types, or branding.

Agency distribution

Ship proprietary plugins and themes to client sites without giving away source code access. Token-based auth keeps your packages private.

Bedrock & Roots

Already using Bedrock? Add your private registry alongside wpackagist.org. Pricore works natively with any Composer-based WordPress workflow.

Multi-site management

Manage dependencies for dozens of WordPress sites from one registry. Update a package once, deploy everywhere.

Works with any Composer setup

Add Pricore as a repository and require your packages. That's it.

composer.json
{
  "repositories": [
    {
      "type": "composer",
      "url": "https://app.pricore.dev/your-team"
    },
    {
      "type": "composer",
      "url": "https://wpackagist.org"
    }
  ],
  "require": {
    "your-agency/custom-plugin": "^1.0",
    "your-agency/starter-theme": "^2.4",
    "wpackagist-plugin/advanced-custom-fields": "^6.0"
  }
}

Up and running in minutes

1

Add your repository

Connect your GitHub or GitLab repository to Pricore. Your WordPress plugin or theme becomes a Composer package automatically.

2

Configure your project

Add your Pricore registry to your WordPress project's composer.json. Works with standard WordPress, Bedrock, or any Composer-based setup.

3

Install with Composer

Run composer require to install your private plugins and themes. Pricore handles versioning, authentication, and distribution.

Making a plugin a Composer package

Add a composer.json to your plugin. Composer handles the rest.

wp-content/plugins/your-plugin/composer.json
{
  "name": "your-agency/custom-plugin",
  "type": "wordpress-plugin",
  "require": {
    "composer/installers": "^2.0"
  }
}

The wordpress-plugin type tells Composer to install the package into wp-content/plugins/. Use wordpress-theme for themes.

Frequently asked questions

Can I use Composer with WordPress?

Yes. WordPress plugins and themes can be distributed as Composer packages by including a composer.json file with the correct type (wordpress-plugin or wordpress-theme). Tools like Bedrock and composer/installers make it easy to manage your entire WordPress stack with Composer.


Does Pricore work with wpackagist.org?

Yes. You can use Pricore alongside wpackagist.org in the same composer.json. Use wpackagist for public plugins from the WordPress.org directory, and Pricore for your private plugins and themes.


How do I make a WordPress plugin a Composer package?

Add a composer.json to your plugin's root directory with the type set to wordpress-plugin. Specify a name (e.g., your-vendor/plugin-name) and require composer/installers so Composer knows to install it into wp-content/plugins/.


Can I use Pricore with Bedrock?

Yes. Bedrock already uses Composer for WordPress dependency management. Add your Pricore registry URL as a repository in your Bedrock project's composer.json, authenticate with your token, and require your private packages alongside public ones from wpackagist.


What about WordPress core updates?

Pricore is for managing your private plugins and themes. For WordPress core, use the roots/wordpress package or johnpbloch/wordpress from Packagist. Pricore handles the private packages that aren't available anywhere else.

Start managing your WordPress packages

Self-host for free or try Pricore Cloud with a 14-day free trial. No credit card required.