Run

Hub

exuvia hub <dir> serves every project under one directory, each with the full API under its own prefix. It is the shape a multi-tenant host needs: one process (or one container) per tenant, one project per workflow.

exuvia hub ./projects --templates ./templates --scheduler external
Route
GET /api/projectslist projects
POST /api/projectscreate one ({id, name, template}; templates come from --templates / EXUVIA_TEMPLATES_DIR)
PUT /api/projects/{project}/templatereplace its code with a template's ({template}): node files and views not in the template are removed (each view folder is replaced whole), the name, run history and stored outputs are kept, and removed files stay restorable from their revisions
DELETE /api/projects/{project}remove one
ANY /p/{project}/api/...that project's API (everything in the table below)
POST /api/schedule/tickevaluate every project's schedules; returns what started and the next due time. A project that fails to load or tick is skipped and named under errors (id → reason); the others still tick
GET /api/hub/statewhether anything is running, and a counter that changes when state does
GET /api/hub/export, POST /api/hub/importthe whole directory as one archive, for hosts with no persistent disk (without outputs already in EXUVIA_ARTIFACT_STORE, or records already in a shared EXUVIA_DB)

With --scheduler external nothing fires on its own: the host calls /api/schedule/tick when it wants schedules evaluated and can sleep until the next time it returns.