Deploying a WordPress change still means dumping the whole database and hoping production orders survive.
Move the intended change. Leave the live data alone.
WordPress-aware selective sync: push pages, fields, menus and configuration without overwriting orders, form submissions or other live data.
Roadmap
Stop overwriting production data just to deploy a WordPress change.
Semantic, WordPress-aware selective sync is a major Nought differentiator. It is not a raw SQL dump. Treat it as roadmap until a status badge on this page says otherwise.
A developer changes
- 2 ACF field groups
- 3 pages
- Theme files
Meanwhile production gains
- 47 WooCommerce orders
- 26 Gravity Forms submissions
Sync should deploy the intended development changes and leave the live transactional data alone. The system is intended to understand ACF configuration, pages, menus, plugin settings, Gravity Forms definitions versus submissions, WooCommerce configuration versus orders, users, and environment-specific settings.
Sync is the Suite product for moving a real WordPress change between environments without treating the database as one blob. It is meant to understand that an ACF field group is not a WooCommerce order, that a Gravity Forms definition is not a submission, and that a page edit should not wipe last night's customers. The layer is in development. Until the status badge here changes, treat every workflow on this page as the intended model rather than a download.
Why the usual way hurts
- Local tools whose deploy button copies the entire database.
- Staging that is weeks out of date because nobody dares to pull production.
- Plugin settings, ACF and pages travelling in the same dump as transactional data.
- No honest comparison of what actually differs between local, staging and production.
How Nought does it
Compare environments, choose the WordPress objects that should move, and leave production-only data where it is.
The actual workflow
Not a feature grid. The sequence you would actually run.
Intended deploy
- 1 Compare local against production
- 2 See the field groups, pages and theme files that changed
- 3 Leave orders and form submissions out of the plan
- 4 Push only what should move
Intended pull
- 1 Take a current production snapshot as the source of truth
- 2 Pull content and configuration you actually need
- 3 Keep local transactional fixtures from overwriting live data later
- 4 Work on the change, then push it back through the same rules
Product, not a mock
Screenshots and video will land here. Placeholders mark the real UI rather than decorating empty space with fake dashboards.
Environment comparison
Selective push plan
Coming
Coming soonRoadmap. Not live.
Environment comparison
See what differs between local, staging and production before anything is written.
Selective pull and push
Move only the objects the change needs, not the whole site.
Semantic WordPress objects
ACF, pages, menus, plugin settings, Gravity Forms definitions versus submissions, WooCommerce configuration versus orders, users, and environment-specific settings.
Production-only data stays put
Orders, submissions and other live records are not collateral damage of a theme or field change.
Runtime capability
Register Sync in the shared Nought shell so Local and WordPress are not two unrelated tools.
Integrations
Support for a platform is not a partnership or endorsement.
Nought Local
The desktop app is the intended place to compare environments and run a selective push.
FieldCraft
FieldCraft restructures ACF on one site. Sync is how those schema and content changes move between environments.
Backup
A Nought backup can be a pull source. Restoring a backup is still a restore, not a selective sync.
Runtime
Universal fallback when a host adapter is not enough, and the agent that registers the capability.
Nought.io
Site inventory and remote context for which environments exist.
Technical details
Not a SQL dump
A mysqldump is a backup. Sync is meant to understand WordPress objects, not copy tables blindly.
Suite capability
Runtime should register Sync so it can sit in the shared Nought shell. Nought Local is the desktop client that will drive pull and push.
Roadmap until the badge changes
Do not treat this page as a shipping promise. The status is in development.
How this is licensed
Buy this product on its own, take Nought Suite, or receive it with a qualifying Nought.io plan. Final amounts are not published until the commercial model is approved.
Individual
Sync
Developer / agency licence
Annual product licence. Site limits will be published with pricing.
Nought Suite
Included in Nought Suite
Nought Suite
One annual licence for the connected toolkit. Agency Suite entitlement is provisioned separately — site limits are not invented here.
Nought.io
Included with qualifying Nought.io plans
Qualifying plans
Entry Nought.io plans may include nothing from Suite, or selected products only. Higher individual/business and agency plans can include Suite entitlement.
Nought.io
Included with qualifying Nought.io plans
Nought.io is WordPress operations infrastructure. Higher individual, business and agency plans can include Suite entitlement. Entry plans may include selected products only, or none. Not every Nought.io subscription includes the entire Suite.
Questions
Is this just a database dump with a nicer interface?
No. The point is semantic, WordPress-aware selection. A dump is Backup's job. Sync is for moving the change and leaving live data alone.
Can it sync ACF without copying orders?
That is the intended model: field groups and stored values can move while WooCommerce orders stay on production. It is roadmap until this page says otherwise.
Do I need Nought Local?
Local is the intended desktop client for pull, push and comparison. Sync is the Suite capability behind that. You will not need two unrelated products that do not talk.
Next in the ecosystem
These are the natural next products — not a popup.