Solo (3 Sites) - yearly payment
$129/yr
Buy nowPricing
Licensing for controlled sync.
Choose a licence for the way your team syncs WordPress: single-site manual workflows, agency remotes, or multisite rollout paths.
Plans
Choose the workflow size that fits your team
Every plan starts with Git-friendly JSON storage. Higher plans unlock more active sites and operational controls.
Pro (9 Sites) - yearly payment
$149/yr
Buy nowAgency (Unlimited) - yearly payment
$179/yr
Buy nowDeveloper Lifetime (Unlimited) - One time payment
$249one-time
Buy nowDeveloper Lifetime (Unlimited) - Split payments (4x $70/mo)
$70/mo
4 payments
Buy nowCheckout, login and account management are handled on my.alterview.net, our secure billing hub.
Checkout links can be connected before public launch. For now, contact us for licensing, purchase, or existing-customer update questions.
Buyer guide
Which plan makes sense?
Pick the plan by operational complexity, not by feature curiosity.
Start with the risk and number of sites you need to control.
Solo is for a single serious site. Studio is for repeated staging/production work across a small client portfolio. Agency is for remote groups, multisite, batch jobs, approval-heavy releases, and teams that need a productized WordPress change workflow.
Solo
One production site
Choose Solo when you mostly need manual JSON exports/imports, safer review, and occasional staging-to-production work.
Studio
Agency delivery rhythm
Choose Studio when remotes, workflows, conflict handling, backups, and recurring client releases save weekly time.
Agency
Many sites or higher governance
Choose Agency when multisite, remote groups, batch processing, audit exports, approvals, and reusable rollout patterns become core delivery infrastructure.
Compare
Manual sync vs controlled workflow
| WPChangeSync | Manual exports | Database copies | |
|---|---|---|---|
| Reviewable changes | Structured JSON | Limited | No |
| Selected item sync | Partial | ||
| Dry runs and conflicts | |||
| Media and ID remapping | Manual | Risky | |
| Repeatable workflows |
Trust
What you are really buying
WPChangeSync is a safer release layer for WordPress-managed data, not just a pile of import/export buttons.
Production control
Dry-runs, approvals, backups
Reduce avoidable production mistakes with workflow gates and restore paths.
Agency leverage
Repeatable workflows
Use the same release model across clients instead of reinventing every migration.
Technical visibility
JSON, logs, WP-CLI, REST
Give developers and site owners inspectable files, scripts, endpoints, and activity records.
FAQ
Pricing questions
How should I choose a plan?
Solo fits one production site and manual sync workflows. Studio is better for teams that need remotes, scheduled workflows, and richer audit visibility. Agency is for multisite, client fleets, and custom rollout needs.
What about existing BricksSync customers?
Existing BricksSync customers are WPChangeSync customers. Current licence holders get the same licence for WPChangeSync, and existing workflows should keep working after the update. See the BricksSync customer update.
Which plan is best for agencies?
Studio fits smaller agencies. Agency is intended for multisite, remote groups, batch processing, and heavier client workflows.
Can I change plans later?
Yes. The pricing structure is designed so teams can start with a smaller workflow and expand when they add more sites or automation.
Is there a trial?
The public checkout can define final trial or refund rules. Until then, use Contact to discuss the right licence and migration path for your site or agency.
Is WPChangeSync only for Bricks?
No. WPChangeSync 2.0 is builder-agnostic. Bricks remains deeply supported, but WordPress content, Gutenberg, fields, media, menus, widgets, remotes, workflows, audit, and storage workflows can matter on non-Bricks sites too.
Do I still need backups?
Yes. WPChangeSync includes sync-level backup and restore paths, but host/server backups remain essential for disaster recovery.
Can you help choose a workflow?
Yes. Send your stack, number of sites, current deployment process, and risk level through the contact page and we can suggest a starting workflow.
Pricing
Start with a safer sync path
Use WPChangeSync to move WordPress changes with files, remotes, dry runs, and rollback.