Nucleo Orchestrator
Orchestrator is the custom integration layer of Nucleo — an iPaaS built around your systems. It moves data between the software that doesn't speak Nucleo natively and the modules that do, and gives you one place to see every flow: what was exchanged, when, with which system, and whether it worked.
What Orchestrator is
Most stacks include at least one system that no standard connector covers — an ERP, a 3PL, a PLM, something legacy. Orchestrator is how those systems join Nucleo: during onboarding, the Nucleo team builds the connectors and flows your setup needs, tailored to your data and your rules.
Orchestrator is not an operational module. It moves and monitors data; it doesn't manage it. Orders and stock live in OMS, products in PIM, assets in DAM — you work on the data in the module that owns it, and Orchestrator keeps the systems around it in sync.
Flows & monitoring
Inside the Nucleo shell, Orchestrator is a monitoring surface over your integration flows. The Dashboard shows the state of the flows at a glance; Projects groups them by the project they belong to; Users lists who has access.
- Flow visibility — what was exchanged, when and with which system, with payloads, timings and history
- Run logs — the trail of each execution, including retries
- Alerts — know the moment a flow fails, and why
The interface is for observing, not operating: when something in the data itself needs fixing, you fix it in the connected module or system, and the flow picks it up.
Connections: custom vs plug & play
Nucleo modules ship with plug & play connections for common platforms — those don't need Orchestrator at all. Orchestrator switches on when a connection has to be built rather than activated: anything bespoke, on-premise or legacy runs through a connector tailored to it.
You can also run Orchestrator standalone — watching custom flows between your own systems even where no other Nucleo module is involved.
Records & volumes
Orchestrator is sized on records — the units of data that flow through it: an order, a product, a stock row. When Orchestrator activates alongside a module connection, the volume follows that connection; when it runs standalone, you choose the records volume for your flows.
How to get started
Because every implementation is custom, Orchestrator starts with a conversation rather than a setup wizard.
- Talk to the Nucleo team about the systems you need connected.
- Together, map the flows: which data moves, in which direction, how often, and what counts as an error.
- The team builds and tests the connectors during onboarding.
- Once live, follow your flows from the Orchestrator dashboard — logs and alerts included.