The public repository contains the hub service, console, SDKs, schemas, Docker demo, and developer docs. One instance can connect multiple business systems through multiple routes, clients, and tool providers. Multi-tenant governance changes how independently managed organizations share an operated platform; it does not replace or unlock a reduced open-source core. This official website is a separate project and is not part of the open-source package.
Use, modify, deploy, and redistribute the open-source code under Apache License 2.0.
Keep the license, copyright notices, and NOTICE file when redistributing modified or unmodified code.
Apache 2.0 does not grant trademark rights to BailingHub, 百灵中枢, or related marks.
Most organizations need only the complete open-source hub. Multi-tenant isolation, platform operations, SLA, training, and delivery support are optional when multiple independent customers must share one operated platform.
Build an independent distribution, industry adaptation, executor, connector, or an implementation of the independent ACC open contract. A community project may keep its own name, roadmap, maintainers, and governance, and it is not required to contribute every modification upstream.
Use your own identity and direction while describing origin, compatibility, and project ownership accurately.
General fixes, contracts, docs, and adapters are welcome upstream; specialized work can remain independently maintained.
Once qualifying projects exist, the official site will list strong independent work. A listing is not certification, warranty, endorsement, or transferred maintenance responsibility.
Community projects must not imply that they are an official BailingHub distribution or have received approval that was not explicitly granted.