Intended deploy
- Compare local against production
- See the field groups, pages and theme files that changed
- Leave orders and form submissions out of the plan
- Push only what should move
Move the change.
Keep the live data.
WordPress-aware selective sync: push pages, fields, menus and configuration without overwriting orders, form submissions or other live data.
Why Sync
Move the intended change. Leave the live data alone.
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.
A better starting point
Compare environments, choose the WordPress objects that should move, and leave production-only data where it is.
- 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.
The intended workflow · In development
A deployment should
move your work.
Selective, WordPress-aware sync is on the roadmap. The aim is to understand the change, rather than replace the whole database.
What you changed locally
- 2 ACF field groups
- 3 pages
- Theme files
What stays in production
- 47 new WooCommerce orders
- 26 new form submissions
- Live transactional data
In practice
From task
to done.
The workflow we are building towards.
Intended pull
- Take a current production snapshot as the source of truth
- Pull content and configuration you actually need
- Keep local transactional fixtures from overwriting live data later
- Work on the change, then push it back through the same rules
On the roadmap
Up next.
Planned work, separate from what is available today.
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.
Fits your workflow.
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.
Your toolkit, your choice
One product.
Or the connected Suite.
This product is in development. Get in touch to follow progress and discuss your workflow.
Individual
Sync
Discuss this product and the right licence for your sites.
Ask about Sync ↗The toolkit
Nought Suite
Connected WordPress tools, with individual and agency options.
Explore the Suite ↗Remote operations
Nought.io
Some Nought.io plans include Suite products. What’s included depends on your plan.
Explore Nought.io ↗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.
Also in the toolkit
Local A WordPress-only desktop app, macOS-first, built with Tauri 2, React, TypeScript and Rust. Designed so local development is not married to a single host. ↗ FieldCraft Field management for Advanced Custom Fields Pro: link and sync shared fields across selected pages, restructure groups, migrate stored values and keep templates working. ↗ Backup Two layers: a conventional WordPress backup product for people who want a plugin, and a remote Nought backup plane that moves the heavy work off the site. ↗ Nought Suite The collection of WordPress products built by Nought. Buy one, or licence the lot. ↗