Agency Platform for Holding Groups and In-House Teams.
Holding groups, in-house digital teams and larger agencies run Zyan on the Agency plan, with custom terms as the team grows. Access is set per member, and every client’s data stays isolated.
48 Keys per Member. Managed at Scale.
Give account managers, designers and bookkeepers the access their work needs. Adjust permissions per member, keep Builder access explicit, and keep client seats on their own portal.
- Role presets for owners, account managers, designers, bookkeepers, and client seats
- Builder access is its own axis — IDE, git, and terminal grants per member
- Invite team members, update permissions and offboard access as responsibilities change
What an enterprise workspace includes.
Every enterprise workspace starts on the Agency plan. Contract terms, support and the migration are agreed with your team.
75 seats
The Agency plan includes 75 seats and 10 Builder seats. Larger teams move to custom terms.
10,000 AI credits
A month, pooled across the whole team, with top-up packs that roll over for 60 days and custom volume by contract.
Every table isolated
Row-level security separates each workspace. Realtime channels stay private, and integration secrets live in a managed vault.
Your own domain
Client portals answer on your domain, one per workspace, attached only after its DNS verification passes.
MSA + DPA
Contract documents ready for your redline. Your data never trains a model, and a deleted workspace is purged within 30 days.
Migration, mapped
Email team@zyan.ai with your current stack, and we map what moves and what connects before you sign anything.
Manage the team. Keep a record of the work.
Turn on managed devices per member and see device time against assigned hours, with one record of who did what across the workspace.
Managed devices, per member
Turn it on per member. The desktop app on macOS and Windows reports active, idle and locked time against their assigned hours.
Private by design
Never keystrokes, and never the owner. Only the owner and full-access admins see it, with an optional in-app disclosure notice.
Every action on record
Team activity lands in one workspace feed, and every lead touch names who made it — a teammate, an automation or Zyan AI.
Who looked, logged
Every view of this data goes to an audit trail you can export, and you set how long device samples and page visits are kept.
Prepare for the security review.
Bring your security and procurement requirements into the conversation early. Request the architecture, data-handling and contractual materials your reviewers need to assess the fit.
Request materials- MSA + DPA (Word, ready for redline)
- Security architecture overview + data-flow diagram
- Subprocessor list with purposes
- Incident-response runbook
- Security questionnaires answered on request
- Insurance certificate on request
Agree on support before rollout.
Response targets and any service credits are defined in your enterprise agreement. Confirm coverage, escalation and recovery requirements with your team.
- Critical incident response (P0)
- 1 hour
- 24/7 — paging on contract
- High-priority response (P1)
- 4 hours
- Business hours — extended on contract
- Standard response (P2 / P3)
- Next business day
- Email + priority channel
- Uptime & recovery targets
- In writing
- Documented per contract in the trust packet
Plan the workspace your teams need.
Tell us how your teams work, what you need to migrate or connect, and which requirements your reviewers need answered. We can scope the rollout and the right contractual materials from there.
- MSA + DPA ready for signature
- Trust packet within one business day
- Named success engineer assigned on contract
- More than 75 seats? Custom terms — contact us