FAQ · BEFORE THE DEMO
Short answers to the questions you should be asking.
Differentiation, data residency, model providers, security review, and what changes after handover.
QUESTIONS
Common questions before the demo.
How is this different from ChatGPT or a copilot.
ChatGPT is a model. A copilot is a chat box. Hubzoid is a hub plus agents. The hub holds your structured knowledge. Your policies, calendars, vendors, decision trees. The agents act on that knowledge across three modes: on-demand Tools, conversational Q&A, scheduled Background. The output is grounded in your numbers, not the open internet.
How long does an engagement take.
Engagements are scoped to your company during discovery. The depth scales with your environment, integrations, and security review. We share an exact timeline as part of scoping, not as a marketing claim.
Where does our data live.
In your cloud or VPC. Hubzoid does not maintain a customer-data lake. World models, agent definitions, and runbooks are deployed into your environment. Engineer access is time-bound and revoked at handover.
Which model providers do you support.
Anthropic Claude on the customer's contract by default. OpenAI and Google supported on request. No training on customer data, enforced via provider enterprise terms.
Is the runtime open source.
Yes. The runtime is the hubzoid package: MIT-licensed, pip install hubzoid, source at github.com/hubzoid/hubzoid. It runs inside your perimeter, so your team can read exactly what executes against your data. The same package powers our engagements; what you audit is what ships.
What happens after handover.
The hub is yours. Your team operates it against the runbook. Most customers take a quarterly retainer for the first quarter to surface drift early. Cancellable on thirty days notice.
Can we start with one team and expand.
Yes. Most engagements start with two or three teams (commonly marketing plus finance, or ops plus accounts). Adding teams later is a follow-on engagement.
Which languages do the agents speak.
Whatever your team uses. English, Hindi, French, German, and other major languages are supported on Telegram, Slack, and digests. Background reports follow the language leadership reads. Tool outputs follow your brand-kit language defaults.
Do you sign InfoSec questionnaires.
Yes. Five business day turnaround target. We share our control documentation under NDA on request.
Are you SOC 2 certified.
No, not yet. We are pre-audit. Our control environment maps to the SOC 2 Common Criteria today (access control, change management, audit logging, incident response). We target SOC 2 Type I in the [QX 2026] window, Type II twelve months after.