Skip to content

Flow
Built for your workflow.

The planned automation and orchestration layer. Runtime executes. Flow sequences the work.

Why Flow

Orchestration on top of Runtime — not another agent.

Flow is reserved for real workflow orchestration: a plugin update can create a backup, apply the update, run Guard, smoke-test, run Optimise, roll back if unhealthy, and send the result. It is not the shared agent. That job belongs to Runtime. Flow is in development and is not sold as a standalone product yet.

A better starting point

Describe the sequence once. Runtime and the Rust planes do the steps. Nought.io records the run.

  • Safe updates still mean a human clicking through five plugins in the right order.
  • A failed update has no automatic backup-and-rollback path.

In practice

From task
to done.

How the product fits into the work you already do.

Safe plugin update (planned)

  1. Plugin update available
  2. Create backup
  3. Update plugin
  4. Run Guard
  5. Health / smoke test
  6. Run Optimise
  7. Rollback if unhealthy
  8. Send the result

On the roadmap

Up next.

Planned work, separate from what is available today.

01

Update pipeline

Backup → update → Guard → health check → Optimise → rollback → report.

02

Event triggers

Plugin update available, deploy, failed health, schedule.

Fits your workflow.

01

Runtime

Execution.

02

Backup, Guard, Optimise

Steps in a run.

03

Nought.io

Trigger, approval, history.

Technical details

Flow vs Runtime

Runtime is the SDK and agent. Flow is orchestration. Confusing them is how you get a seventh plugin dashboard.

Your toolkit, your choice

One product.
Or the connected Suite.

Choose an individual product licence or ask about Nought Suite. Contact us for pricing and availability.

Compare product licences ↗

Questions

Can I buy Flow today?

No. It is in development. If you need this pipeline now, that is engineering work — send a brief.

Make Flow
part of your workflow.

What are we
building next?

Tell us about it