BailingHub sits beside your business system. It receives business triggers, assembles context, calls models or executors, exposes selected business tools, records trace and audit data, and sends results back.
Configure one business scenario with target, model credentials, memory, knowledge, tools, budgets, and delivery.
Route allowlists, scopes, risk levels, parameter-level confirmation, rate limits, approvals, and audit trails.
Jobs, messages, approvals, audit records, trace events, delivery attempts, and troubleshooting bundles are hub-owned.
The hub controls what the agent can reach. Your backend still decides what the on-behalf-of user can actually do.
Authentication, routing, context assembly, tool governance, ledger persistence, and delivery share one runtime lifecycle and versioned contracts.
Models, inbound channels, tool providers, storage, and executors integrate through defined adapter surfaces so one extension does not have to rewrite the whole runtime.
Jobs, messages, memory summaries, approvals, audit records, and trace events persist in the database you operate. Cloud model inputs still follow the provider and endpoint you choose.
Routes, clients, tools, knowledge, approvals, audit, console, SDKs, and operations tooling are open source. Multi-tenant governance changes shared-platform administration, not the core runtime capability set.
Business event / web widget / inbound channel route: scenario routing context: assembly brain: model or executor tools: governed tools call: signed business API call authority: business permission check