Team
Team overview
What Team adds to zn-gate, who can do what in an organization, and how seats, the shared quota and billing work.
Team gives an engineering team one set of rules for every coding agent its developers run, and a record of what those agents did. zn-gate keeps running on each machine and stays free; Team adds the shared parts:
- One signed policy that every zn-gate in the organization downloads, verifies and applies. See Organization policy.
- An audit trail of the decisions zn-gate takes on each machine, uploaded in the background. See Join a machine.
- Exports of that trail and of your cloud checks, as CSV, JSON or OpenTelemetry logs, for reviews and auditors. See Export the audit trail.
- A shared quota for API and MCP calls, so nobody's personal plan runs out mid-sprint.
In v0 the policy is tested and supported for Claude Code and Codex. Cursor and OpenCode follow in a later release.
What leaves each machine
The same rule as the rest of zn: values never leave the machine. The audit trail carries metadata only: the secret's name, the agent, the tool, the host it tried to reach and the decision. Never secret values, prompts, file contents or tool output. More in What leaves your machine.
Roles
| Role | Members and invitations | Policy | Audit log and exports | Billing and seats | Uses a seat |
|---|---|---|---|---|---|
| Owner | invite and remove anyone, change roles | publish | read and export | manage | yes |
| Admin | invite and remove members | publish | read and export | no | yes |
| Member | no | read | no | no | yes |
| Auditor | no | read | read and export | no | no |
Members see a read-only overview: their membership, where their usage is billed and the policy in effect. Sensitive actions (inviting, promoting to admin, publishing a policy, organization settings, API keys and agent tokens, seats and billing) ask owners and admins for two-factor authentication.
Seats, quota and billing
- $19 per seat per month, or $15 per seat per month billed annually. From 2 to 50 seats.
- 14-day trial. Polar asks for a card; nothing is charged before the trial ends, and you can cancel at any time from the billing portal.
- 50,000 calls per seat each month, shared across the organization. While the organization's plan is active or in trial, every call a member makes (API keys, MCP, installs) counts against that pool, and their personal plan is paused, not cancelled. Calls count by input size, as on every plan: one call up to 2,000 characters, one more for each extra 1,000 characters or part of them (how calls are counted). An input that needs more calls than are left in the pool is refused with a 429 (
INSUFFICIENT_QUOTA, withrequiredandremaining); a shorter input may still fit. Members' personal credits are never used for organization calls. - After the pool, monthly plan: the owner can allow pay-as-you-go calls at $0.10 per 1,000, up to a monthly cap they set, billed on the subscription's next invoice. The default cap is $0, which stops at the pool.
- After the pool, annual plan: calls use prepaid organization credits at the same price ($1 = 10,000 calls, from $10), which the owner buys in the dashboard. Credits never expire; without credits, calls stop at the pool.
- During the trial the pool is always a hard limit.
- Seats in use count members and pending invitations, and the number of seats can never go below that.
Sign-up starts on the pricing page: you create the organization, start the trial and then invite your team from Members.
Support and billing
- Support: support@usezn.com. We aim to reply within one business day (Monday to Friday, Central European Time).
- Cancelling: cancel from the billing portal (Billing & seats, Manage in Polar). The plan stays active until the end of the period you paid for.
- Refunds: if you cancel, ask support@usezn.com within the paid period and we refund the unused part, prorated by days and seats.
- More than 50 seats or SSO: contact sales@usezn.com.
What Team is not
zn-gate is a local guardrail, not an MDM. Someone with administrator rights on their own machine can leave the organization. The dashboard makes that visible: the last policy version each install has seen, its last upload, and installs that are out of date or silent.