Hubzoid is open source under the Apache 2.0 license, including the Console, access controls and workflows. You can inspect the product code and run a Hub on infrastructure you control.
That matters when the software reads business records, answers colleagues and performs scheduled work.
At a glance
- Hubzoid's product code and team controls are in the open-source repository.
- Your Hub's written context and tools can be maintained by your own team.
- Hosting, model providers, dependencies and ongoing operation still need review.
The team controls are part of the product
The Hubzoid repository (opens in a new tab) includes the runtime, bridge, gateway, scheduling, access checks, activity records and Console.
There is no separate paid Hubzoid feature edition needed to turn those controls on. Implementation services are work around the same product: understanding the task, connecting systems, building the agent and helping the team operate it.
Check the repository's licensing note (opens in a new tab) and license for the authoritative terms, especially if you distribute a modified version.
Your business context stays readable
A Hub holds instructions, reference knowledge and reusable procedures as plain files, alongside the tools and workflows for the job.
That lets a person review the current rule, compare an edit with the previous version and identify who owns it. The knowledge does not have to remain trapped in the chat where someone first wrote it.
A readable format helps with ownership. It does not maintain the content for you. Policies still change and someone still needs to retire an old definition.
Self-hosting is one part of data control
Running the Hub yourself gives you control over its files, databases and deployment. It does not mean every request stays inside that infrastructure.
Your model provider receives the requests you send to it. Connected services receive the data their tools use. Tracing and other optional integrations can create additional destinations.
Review the actual configuration and the terms of each service. Open source makes the product inspectable, not automatically offline or compliant with every organization's requirements.
Dependencies keep their own terms
Hubzoid builds on other projects. Their licenses remain relevant to your deployment and distribution choices.
Treat this as part of adoption, alongside provider agreements and the way credentials are stored.
Review the boundaries that matter to your task
A useful product review asks:
- Which channels may reach sensitive tools?
- How is the caller verified and their grant checked?
- What happens when the access store or decision log is unavailable?
- How do runs recover after a restart?
- What can be backed up, restored and upgraded?
The answers need to hold in your deployed configuration. A screenshot or a successful example does not establish them for every integration.
Decide who will operate what you own
The code does not need a Hubzoid product license fee. Your deployment still needs a model setup, infrastructure, backups and people responsible for changes and failures.
You can build and run it yourself, or get implementation help. Either route should end with a team that knows where the context lives, how access works and who responds when a report fails.
Next step: read the security model, then installation if you want to run your own Hub.
