Back to EcosystemSuite Orchestration
NabuOS
One switchboard for the whole pantheon.
Orchestration
n8n Fleet
Live Monitor
Operating LayerLIVE
The fleet
Thirteen agents, one switchboard, zero chaos.
- 01Open the /os consoleThe panel is delivered as a conversation.
- 02Ask in plain languageNatural questions route to the right tools.
- 03Tools fire across modulesLocal, HTTP and MCP tools answer one call.
- 04Watch results stream inSSE events show each tool, timed in ms.
3
Tool types
7
SSE event types
2
Gates per call
Module Switchboard
Turn each Nabu product on or off per team, region or brand — one tenant view across the whole fleet.
Workflow Composer
Chain agents visually: Form → CRM → Voice → Desk. Routes, retries and fallbacks without writing glue code.
Live Health Monitor
Latency, errors, token spend and queue depth per agent — with alerts before your customers notice.
Roles & Guardrails
Who can deploy what, spend limits per module, and an audit log on every action the suite takes.
One API Surface
A single API key, webhook mesh and SDK for all thirteen products instead of thirteen integrations.
Suite Orchestration
The Operating Layer
- 13 products, 1 login
- Sub-second routing between agents
- Every action audit-logged
NabuOS
FAQ
NabuOS FAQ
No — each product runs standalone. NabuOS is for teams that want them orchestrated: shared contacts, chained workflows and one bill of health.
Yes. Workflows compile to n8n executions, so your team can inspect and extend every automation with the tooling it already knows.
NabuOS detects the failure, retries with backoff, and can reroute the task to a sibling agent — then tells you what happened.