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, answered straight.
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. This is applied AI built into how your company decides, not a tool bolted on beside it.
How do we get started.
Request an Agent Map. Answer a few questions about your team and the tools you run, and we send back a one-page shortlist: the agents that would do the most for your company, what each one watches, and the hours it gives back. No demo, no sales sequence, a real document. It is the fastest way to see what a hub would do for you before any commitment.
How does pricing work.
Each engagement is fixed-price and scoped to your company. Your first agent plus the hub is one fixed price, and each agent after that is its own. No per-seat pricing, no open-ended scope. We share exact numbers in the proposal, after a short fit call.
Where do you work, and which systems do you support.
We deploy inside your own cloud, so we can work with companies anywhere. We connect to the systems you already run, from major ERPs and accounting platforms to the industry-specific tools your sector runs on, and meet your team on the surfaces they already use: WhatsApp, Telegram, Slack, email, web.
Do you replace our existing systems.
No. Hubzoid reads from the systems you already run, ERP, accounting, CRM, drives, and chat, and makes them legible to your agents. We do not rip and replace, and we do not copy your data out. Your core systems stay exactly where they are.
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. Your data trains no model: not the provider's general models, and nothing at Hubzoid, enforced via provider enterprise terms and zero-retention access.
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 own cloud, 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. A quarterly retainer is available for the first quarter, to surface drift early. Cancellable on thirty days notice.
Can we start with one team and expand.
Yes. Start with one team or a pair, commonly marketing plus finance or ops plus accounts, and add more once the first agents have earned it. 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.
Pre-audit. No SOC 2 report yet. Our controls are built against the SOC 2 Common Criteria: access control, change management, audit logging, incident response. We're targeting a Type I report by the end of 2026, with Type II to follow twelve months later. In the meantime, the hub runs in your cloud, under your keys, and every action lands in your logs.