Most local WordPress apps make pull and push easy only if you live inside one hosting ecosystem.
Local WordPress. Any host.
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.
Nought Local
- WordPress sites created
- 4,263
- Installs
- 1,847
- Sites imported
- 918
Nought Local is being built so you can create or import WordPress locally, then pull and push across unrelated hosts: native provider adapters, generic SSH/SFTP/WP-CLI, Runtime as a universal fallback, Nought Backup as a pull source, and Nought.io as site inventory. Selective, WordPress-aware movement of changes is Sync — a Suite product Local is meant to drive, currently on the roadmap.
Why the usual way hurts
- Local tools whose deploy button only works on the vendor's hosting.
- Dumping whole databases and overwriting production orders.
- No honest comparison of local, staging and production.
How Nought does it
One desktop app, many transports, with Sync as the WordPress-aware layer when that product ships.
The actual workflow
Not a feature grid. The sequence you would actually run.
Intended pull
- 1 See the site in Nought.io inventory, Backup, Runtime, or SSH
- 2 Pull into a local WordPress
- 3 Work on the change
- 4 Push only what should move, through Sync when that layer ships
Product, not a mock
Screenshots and video will land here. Placeholders mark the real UI rather than decorating empty space with fake dashboards.
Nought Local site list
Shipped in this product
Only what is actually in the current build or honestly in beta.
Desktop WordPress app foundation
Tauri 2 application with site and runtime commands. Treat public availability as in development.
Provider adapter architecture
The app is designed around native adapters plus SSH/SFTP/WP-CLI, Nought.io, Nought Backup and Runtime. Host names here describe intended adapters, not an official partnership.
Coming
Coming soonRoadmap. Not live.
macOS download
Primary platform. Windows and Linux are designed for; they are not a launch promise.
Pull and push through host-neutral transports
Native adapters, SSH/SFTP/WP-CLI, Runtime, Backup and Nought.io inventory.
Sync
Selective, semantic WordPress sync lives in the Sync product. Local is the desktop client that should run it.
Integrations
Support for a platform is not a partnership or endorsement.
Sync
The WordPress-aware selective layer Local is meant to drive.
Nought.io
OAuth and estate inventory.
Nought Backup
Pull from a backup.
Runtime
Universal fallback.
SSH / SFTP / WP-CLI
Generic transport.
Technical details
Host-neutral
Adapters for specific hosts are integrations, not endorsements.
Runtime fallback
If a host has no first-class adapter, Runtime is the intended universal path.
Companion to the Suite
Local is a desktop app, not a WordPress plugin licence. It sits in the toolkit because pull, push and Sync belong next to Files, Backup and FieldCraft.
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
Local
Developer / agency licence
Not sold as a standalone SKU.
Nought Suite
Buy separately
Nought Suite
One annual licence for the connected toolkit. Agency Suite entitlement is provisioned separately — site limits are not invented here.
Nought.io
Not included with Nought.io
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 a LocalWP alternative?
That is the job it is being built for: local WordPress without a host-shaped ceiling. It is in development, not a general download yet.
Can it sync ACF without copying orders?
That work belongs to Sync. Local is the desktop client. The semantic model is still roadmap until the Sync page says otherwise.
Next in the ecosystem
These are the natural next products — not a popup.