Implementation

How does multi-tenancy work?

Each org is a separate tenant. Receipts, agents, projects, billing all scoped to the org. Per-project ACLs add a second layer for sensitive work within an org.

Join the launch waitlist Install MCP server

Tenant boundary

Receipt feeds don't cross orgs. Agent transfers between orgs require explicit countersign from both. Standard SaaS multi-tenancy — your org's data is yours.

Per-project ACLs within an org

org-public / members-only / private — see /use-cases/access-control.

Per-engineer attribution within an org

human_id captures the engineer. Cross-engineer queries respect ACL boundaries.

Receipts can be shared via signed JWT links to external auditors / customers. Sharing doesn't move tenancy; it's a read-only view.

Org admin model

Single admin or multi-admin. Admins manage billing, ACLs, install tokens. Members can issue receipts. Granular roles in v0.8.

White-label tenancy

Enterprise tier white-label lets your org's receipts be signed by your domain. External viewers see your branding, not GenZAgents.

FAQ: Enterprise pricing

SSO, ACL, audit logs, evidence packs, anomaly webhooks, self-hosted Helm, on-prem option, dedicated dispute lane, SLA.

FAQ: Where is data stored

SaaS: Azure UK South or EU West. Enterprise self-hosted: any region you choose. Granular per-receipt residency on Enterprise tier.

FAQ: Self-hosted

Yes — Enterprise tier ships a Helm chart for Kubernetes. Your cluster, your Postgres, your control. Air-gap-compatible mode on roadmap.

FAQ: How many agents do I need

One agent per role / project / domain usually. Most orgs settle on 5-20 agents per 100 engineers.

Get the trust layer for your AI work

GenZAgents is the verified work-history layer above every AI provider your team uses. Sign cryptographic receipts, hand off conversations across Claude / ChatGPT / Cursor / Gemini, keep institutional AI knowledge when employees leave.