Data stays where it lives.
We deploy your hub. We do not host your data. Read-only by default; write access only where you explicitly enable it.
Customer data leaves the perimeter
Decisions logged with policy and sources
InfoSec questionnaire turnaround
Per deployment. No cross-customer data
Four pillars. No exceptions.
Data stays where it lives.
World models, agent definitions, and runbooks live in your cloud or VPC. Hubzoid does not maintain a customer-data lake. Customer data does not leave the perimeter.
Read-only by default.
Every connector ships read-only. Write access is enabled only with explicit, documented consent and a recorded audit trail of every write.
Single-tenant. Customer-controlled.
Each customer's hub is a separate deployment. Engineer access is time-bound, audited, and revoked at handover. Identity is yours.
Every decision logged.
Every agent decision is logged with the prompt, the policy applied, and the sources read. Available for SOC 2, internal audit, and incident review.
The full perimeter.
Data residency
World models, agent definitions, and runbooks live in your cloud or VPC. Hubzoid does not maintain a customer-data lake.
Model providers
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.
Tenant isolation
Each customer's hub is a separate deployment. World models, prompts, and outputs are not shared across customers.
Access control
Single-tenant, customer-controlled identity. Engineer access is time-bound and audited; revoked at handover.
Audit trail
Every agent decision is logged with the prompt, the policy applied, and the sources read. Available for SOC 2, internal audit, and incident review.
InfoSec questionnaire
Enterprise security questionnaires returned within five business days. contact@hubzoid.com.
One quarter. One hub. One company that runs on agents.
One engagement at a time, by design. Deployed inside your perimeter. Yours after handover.