QuoxCORE components · orchestration

Don’t build your own orchestration.

Registries, routing, schedules and the machinery that starts work and keeps it inside the lines. It is a platform, and you were trying to ship a feature.

See what ships Try the live demo

Included in QuoxCOREFree, self-hosted, nothing to buy.

Build it yourself and you are signing up for

An agent registry with capability scopeswhich model, which provider, which tools, decided per agent
Model routing you can change without a deployproviders and models swapped per agent, not baked into code
Server-side triggerscron, webhooks and events that fire with nobody’s laptop open
A workflow engine with a human gateretries, expressions, and an approval step exactly where it matters

Or install QuoxCORE. All of it is already there.

In plain words

What it is, where it lives, when to reach for it

What is it: The execution layer of QuoxCORE: registered agents and assistants, workflow runs, and server-side triggers and schedules.
Where do I use it: On the dashboard agents and workflow pages, and in your terminal through quox agent and quox trigger.
When would I use it: When work should start on a schedule or an event, and run under rules rather than supervision.
How do I use it: quox assistant list shows who can act; quox trigger views and activates webhook, schedule and event subscriptions.

QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE

agents & assistants

Registered, routed, scoped.

Agents are registry entries, not scripts on a laptop: each carries its provider, its model routing and the capability scopes it may touch. Assistants are the chat-facing kind, and every organisation starts with one already active.

How do I use itquox agentDashboard: Agentsquox assistant list shows who can act in your organisation right now.

$ quox assistant list
 Name                    Status   Created
 Meridian Ops Assistant  active   2026-09-09 22:37

Real output · demo organisation, minutes after creation · captured 2026-09-09

The agent studio in the QuoxCORE dashboard: provider, model routing and capability scopes per agent

triggers & schedules

Work that starts itself.

Cron schedules, webhooks and platform events start workflows server side. Subscriptions are visible, and can be activated or deactivated, from the dashboard or the terminal: no browser tab left open, no laptop doing cron’s job.

How do I use itquox triggerDashboard: Workflowsviews webhook, schedule and event subscriptions, and flips them on or off.

The triggers calendar in the QuoxCORE dashboard: scheduled work laid out over the month

Where it sits

The engine room, governed.

Bundled with QuoxCORE; orchestration is not an add-on. Workflows, loops and fleet execution are the same family with their own pages, and everything they run passes the governance layer beside them.

if that’s not enough ...your code goes hereyour plugin can use everything underneath

you build this

QuoxFlow workflows/QLoop/Fleet exec/Agents docs/Schedulers docs

Ready when you are

Point it at the work.

Agents, triggers and schedules ship in the box with QuoxCORE: no extra licence, no extra install.

See workflows Try the live demo