Six Nought plugins should not mean six agents, six logins, and six unrelated wp-admin screens.
One Nought agent. One dashboard. Products register capabilities.
The lightweight shared Nought agent and SDK embedded across compatible WordPress products. Not a plugin you necessarily buy.
Runtime is the shared agent: Nought.io connectivity, authentication, secure communication, capability registration, jobs, events, health, and remote operations. If several Nought products are installed, Runtime must load once. Individual plugins detect an existing compatible Runtime instead of each creating an independent agent. The result is one connected Nought area in WordPress rather than a bundle of disconnected dashboards.
Why the usual way hurts
- Product bundles that still look like six plugins taped together.
- Duplicate control panels and duplicate background agents.
- No shared way to talk to Nought.io.
How Nought does it
Vend Runtime once. Products register capabilities such as files, backup, guard, optimise, FieldCraft and sync. The user sees one Nought shell.
The actual workflow
Not a feature grid. The sequence you would actually run.
Install the second product
- 1 Runtime is already present
- 2 The new product detects it
- 3 It registers capabilities
- 4 You still have one Nought area in wp-admin
Product, not a mock
Screenshots and video will land here. Placeholders mark the real UI rather than decorating empty space with fake dashboards.
Shared Nought dashboard in WordPress
Shipped in this product
Only what is actually in the current build or honestly in beta.
Shared WordPress runtime
Product plugins vendor this runtime rather than each shipping a standalone agent.
Capability registration
Products register what they can do so the shell can show Backup, Security, Performance and the rest without six menus.
Coming
Coming soonRoadmap. Not live.
Full shared dashboard navigation
Overview, Products, Backup, Security, Performance, Automation, Connection, Settings — with every product contributing its panel.
Job and event bus for Flow
Runtime is the agent. Flow will orchestrate sequences on top of it.
One Nought area in WordPress
Compatible products register capabilities into a shared shell. Runtime loads once. You do not get six unrelated plugin dashboards.
Overview
Connection status, product capabilities, recent jobs. Backup, Guard and Optimise contribute their own panels without replacing this shell.
The heavy jobs leave your website
Your website should not also have to back itself up, scan itself, and speed itself up. Those jobs happen somewhere else.
Integrations
Support for a platform is not a partnership or endorsement.
Nought.io
Enrolment, auth, remote jobs, telemetry.
Files, Backup, Guard, Optimise, FieldCraft, Sync
Register as capabilities.
Nought Local
Runtime is a universal fallback transport when a host adapter is not enough.
Technical details
Agent, not a SKU
You should not have to shop for Runtime separately. Compatible products bring it with them, once.
Runtime is not Flow
Runtime connects and executes. Flow, when it ships, orchestrates multi-step workflows.
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
Runtime
Utility licence
Not sold as a standalone SKU.
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
Do I buy Runtime?
No. It is infrastructure bundled with compatible Nought products. The Suite is the commercial collection; Runtime is how those products share a brain.
Is this Flow?
No. Flow is the future automation layer. Runtime is the agent those automations will call.
Next in the ecosystem
These are the natural next products — not a popup.