Choose the right evaluation path
The fastest way to understand BailingHub is the online console: no install, no model key, and your own isolated tenant for inspecting routes, tool providers, runs, audit trails, and platform capabilities. Use Docker Demo when you want the full technical loop on your own machine.
1. Online Console
Best for product evaluation, console mental model, and multi-tenant preview. After registration, you enter your own tenant console; the public online environment is not recommended for production secrets.
2. Docker Demo
Best for technical validation. It starts the hub, MySQL, a demo business app, route, client, tool provider, approvals, trace data, and smoke checks.
Start with the User Guide when the business scenario is still unclear
It explains why the control plane exists, how console objects map to business decisions, which first scenario to choose, and what requirements to hand to developers.
$ docker compose up --build Console: http://localhost:18900/console/ Login: admin / bailing-demo-admin Route: demo_support
Fresh Ubuntu/Debian servers can use the one-line installer for Docker Demo: curl -fsSL https://www.bailinghub.com/install.sh | sh. Use BAILING_INSTALL_MODE=image for official prebuilt images.
Five objects to understand
Route
A business scenario. It selects the target model/executor, memory, knowledge, tools, budget, and delivery policy.
Client
A business system credential. It controls authentication, route allowlists, rate limits, and budget constraints.
Target
The execution backend selected by a route, such as the built-in OpenAI-compatible LLM target or a remote executor.
Tool Provider
A business system endpoint that publishes selected APIs as agent-callable tools through ACC, OpenAPI, or SDK-generated specs.
Runtime Ledger
The hub-owned state database for jobs, messages, trace events, audit records, approvals, and delivery attempts.
Business Authority
BailingHub controls tool reach. Your backend remains the final authority for user permissions and business data access.
Recommended reading order
1. User Guide
Translate a business requirement into routes, tools, knowledge, identity, and delivery decisions.
2. Online Console
Inspect the complete console and product model immediately, without installing anything.
3. Docker Demo
Run the full loop: business system exposes tools, an Agent calls them, trace and audit records are created.
4. Business Tools
Expose selected business actions with scopes, risk levels, approval intent, and HMAC-signed tool calls.
5. SDK
Use PHP, Node, Python, Java, Go, .NET, or the plain HTTP/OpenAPI contract from any language.
6. MCP Safe Execution Map
See where protocol authorization, approval, idempotency, retries, audit evidence, and final business authority belong.