Choose the level of ownership and administration your AI work needs. The difference is how broadly you share, administer and operate—not whether basic protections apply.
Compare the plans Questions about pricing1 builder/operator seat
Your approved AI environment, across your projects and supported clients.
Discuss Solo5 builder/operator seats
Shared standards. Separate identities. Better ways of working together.
Discuss Team25 builder/operator seats
Organizational policy across people, deployed agents and business systems.
Discuss BusinessA scoped agreement
The identity, deployment and operating model your organization needs.
Discuss EnterpriseScoped authority, credential protection and safe recovery are foundational—not premium upgrades.
Compare how ownership and administration expand. Specific integration and service requirements belong in your agreement.
Scroll horizontally to compare all plans →
| What changes as you grow | Solo | Team | Business | Enterprise |
|---|---|---|---|---|
| Environment ownership | Personal & project profiles | Shared team baselines | Company rollout policy | Tailored operating model |
| Tools, skills & MCPs | Private reviewed library | Shared catalogs & releases | Organization-managed distribution | Assessed custom requirements |
| Connections & access | Owned, explicitly scoped | Team-owned administration | Organizational lifecycle | Identity, key & network requirements |
| Change management | Diff, pin, review & rollback | Shared review & staged activation | Administrative change workflows | Agreed lifecycle requirements |
| Approval workflow | Own exact-action review | Team reviewers & channels | Multi-step & separation of duties | Tailored review requirements |
| Evidence & investigation | Own governed actions | Shared team investigations | Organization reporting & export needs | Agreed retention & evidence |
| Knowledge & learning | Private reviewed lessons | Reviewed shared knowledge | Organization-scoped controls | Tenant-private requirements |
| Foundational protection | Scoped authority & credential protection | Same foundation | Same foundation | Same foundation |
Organize private tools, skills, plugins and instructions into versioned profiles. Select the right connections and knowledge for each project. Compare approved setup with observed state, review changes and keep the receipts from governed work.
Give the team a reviewed baseline without sharing credentials or flattening every project’s permissions. Organize shared catalogs and team-owned connections. Make release ownership, action review and member onboarding explicit.
Bring company-wide policy administration, richer review and workload lifecycle into the same operating model. Align data, evidence and organizational requirements across teams instead of granting every agent a separate exception.
Scope your identity mappings, network and deployment requirements, capacity, retention, onboarding and support. Establish the integration path and success criteria through an explicit agreement rather than assuming one universal enterprise bundle.
A seat represents a person who builds or administers agents, connections, policies or shared configuration. It is not a count of stored agent definitions, temporary child agents or separate device logins.
No. Provider-direct model, voice, tool and storage accounts retain their own charges. A DriftGate subscription is not an unlimited subscription to every provider.
An agent is a software identity or runtime binding, not an extra human employee. The selected plan cards include one, five or 25 builder/operator seats; technical usage and scope still need an appropriate agreement.
Team centers on shared environments, ownership, repeatable onboarding and reviewed releases. Business extends administration across company policies, richer review, identity lifecycle and cross-team evidence needs.
No. Keep source systems authoritative and choose the appropriate permission-aware access model. Ordinary source storage, hosted indexes and model usage are different cost categories.
Discuss your expected work and requirements with us. Additional usage, annual arrangements, dedicated infrastructure and professional services need explicit terms; they are not implied by these monthly cards.