On The X Subscription, Cursor Teams combines per-seat weekly usage pools for Cursor and Grok models with a shared prepaid balance for third-party models, and includes Grok Bot (often searched as Grokbot) on every paid seat. Cursor Enterprise adds pooled usage, SCIM, audit logs and an admin switch to govern who can use Grok Bot. This guide sets out the prices, usage rules and governance checks we recommend for South African teams.
Every price and admin setting below comes from public Cursor documentation, with a link and the date we checked it.
App Developer Studio is a Registered Partner in the SpaceX Super Intelligence Partner Network. View our partner profile
We build production OpenAI agents, multi-agent workflows, ChatGPT and Codex integrations, Grok Bot and Cursor delivery, and deploy on the platform your organisation approves, including Claude.
By Rob MacleanReviewed by Amanda KaburiseLast reviewed
Teams bills per active paid seat across three paid tiers plus a Free seat, and one team can mix tiers so heavy agent users get a larger weekly pool without upgrading everyone. Enterprise is quoted by sales and pools usage across the whole team.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Premium seat, billed monthly | Premium seat | $30 per user a month, with the Premium weekly usage pool | cursor.com |
| Super seat, billed monthly | Super seat | $100 per user a month, with the Super weekly usage pool (3.75x Premium) | cursor.com |
| Ultra seat, billed monthly | Ultra seat | $200 per user a month, with the Ultra weekly usage pool (12.5x Premium) | cursor.com |
| Free seat | Free seat | $0 per user a month for Members or Admins, with no team usage allowance; assigned via email invite or the Seat menu | cursor.com |
| Annual seat billing | Teams | $300 a year for Premium, $1,000 a year for Super and $2,000 a year for Ultra on The X Subscription | cursor.com |
| Mixing seat tiers | Teams | One team can mix Premium, Super, Ultra and Free seats; seat tier is separate from Member or Admin role, and Plus is not available for teams | cursor.com |
Prices in USD as of , excluding VAT. Check the vendor page before you buy.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Enterprise pricing and inclusions | Enterprise | Custom quote via Cursor sales; adds pooled usage shared across the team, invoice billing, SCIM 2.0, audit logs and priority support | cursor.com |
Prices in USD as of , excluding VAT. Check the vendor page before you buy.
Two billing rules catch engineering managers off guard. First, included weekly pools cover Cursor models (including Grok and Composer) and refresh every week, rather than once a month. Second, third-party models are paid from a shared prepaid balance from the very first request, so a team that uses external frontier models needs a funded prepaid balance and clear per-member spend caps.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Included weekly usage pool | Teams | Each paid seat gets its own weekly pool for Cursor models (Grok 4.7, Grok 4.6, Grok 4.5 and Composer 2.5), shared across Cursor, Grok and Grok Bot for that person; seats on Teams do not share weekly pools | cursor.com |
| Third-party models | Teams and Enterprise | Not included in the seat price; billed from a shared prepaid team balance at public API list prices plus the $0.25 per million token Cursor Token Rate unless exempt (Cost mode or cache-read strictly below $0.10 per million tokens across every tier) | cursor.com |
| Legacy Teams seats | Teams | Teams created before The X Subscription use Standard ($40) and Premium ($120) monthly seats and keep working unless an admin switches permanently | cursor.com |
| Billing currency in South Africa | Teams and Enterprise | Varies by region; check at checkout | cursor.com |
As of . Check the vendor page before you rely on it.
On a self-serve Cursor Teams plan, Grok Bot is on by default for every paid seat and there is no admin toggle to turn it off. For regulated organisations or staged pilots that want editor seats for everyone while holding Grok Bot to one approved group, that rule favours Cursor Enterprise or a separate pilot team with a written access policy.
Before staff build or share Bots, Pages or agent-built apps, we recommend checking the workspace sharing defaults. On self-serve Teams, public Bot template sharing starts allowed, Bot sharing defaults to Everyone, Page sharing defaults to Anyone on the team, and Slack Workspace Access is on by default. Tightening those settings before invitations go out prevents internal workflows, connected app credentials or shared artefacts from spreading wider than intended.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Grok Bot on Teams | Teams | Included on every paid Teams seat and enabled by default, with no admin switch to turn it off (stays off only on Legacy Privacy Mode or legacy request-based plans) | cursor.com |
| Grok Bot on Enterprise | Enterprise | Controlled by an organisation-wide Enable Grok Bot switch in the Cursor dashboard, with group-level access via Manage Group Access | cursor.com |
| Grok Bot isolation model | Teams and Enterprise | Each user gets a dedicated cloud computer in a Firecracker microVM; all Bots that user runs share that computer, and Team Bots carry their owner's apps, secrets and files into teammates' chats | cursor.com |
| Sharing defaults to review before rollout | Teams and Enterprise | Public template sharing starts allowed on self-serve Teams and off on Enterprise; Bot sharing defaults to Everyone; Page sharing defaults to Anyone on the team; Slack Workspace Access is on by default; Allow Shared Logins and Agent Email are off by default | cursor.com |
| Execution on member machines | Teams and Enterprise | Team ceiling defaults to Always allow while each member defaults to asking per task; Cursor recommends setting Never allow unless Bots need local file access | cursor.com |
| Enterprise-only Grok Bot controls | Enterprise | Network destination allowlists, Enforce Auto-review and team Auto-review rules, Inference Hooks, Action Recording, OpenTelemetry Export, Audit Logs and the MCP server allowlist | cursor.com |
As of . Check the vendor page before you rely on it.
Cursor includes SAML 2.0 and OIDC single sign-on on both Teams and Enterprise, and Grok Bot reuses that Cursor login. SCIM directory sync, audit logs, network destination allowlists and enforced Auto-review rules require Enterprise.
Grok Bot cloud computers run in the United States, and public Cursor documentation does not confirm a South African residency option. Note too that Grok Bot manages its own model selection and is not restricted by the Cursor editor's team model allowlist, so review Cursor's subprocessor list if your contract limits model providers.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Single sign-on | Teams and Enterprise | SAML 2.0 and OIDC SSO included at no extra cost on Teams and Enterprise | cursor.com |
| SCIM directory sync | Enterprise | Enterprise only (SCIM 2.0 user and directory-group provisioning) | cursor.com |
| Training on team data | Teams and Enterprise | Not used for model training when Privacy Mode is enabled; admins can enforce Privacy Mode across the team | cursor.com |
| Data deletion and DPA | Teams and Enterprise | Under Cursor's Data Processing Agreement, data is deleted or returned within 30 days of written direction after service ends | cursor.com |
| Audits and certifications | Teams and Enterprise | SOC 2 Type II, ISO/IEC 27001:2022, ISO/IEC 42001:2023 (covering Grok Bot) and AIUC-1 | cursor.com |
As of . Check the vendor page before you rely on it.
| Item | Plan | Detail | Source |
|---|---|---|---|
| Where Grok Bot computers run | Teams and Enterprise | Hosted in the US; Cursor offers a US-only data residency programme for inference, processing and storage through account teams | cursor.com |
| Data residency in South Africa | Teams and Enterprise | Varies by region; check at checkout | cursor.com |
As of . Check the vendor page before you rely on it.
Settle these points with your engineering lead, security team and information officer before enabling Cursor or Grok Bot on production repositories or customer data. This is a starting point, not legal advice.
The trade-off: Enterprise requires a sales quote, while Teams can launch a bounded pilot immediately.
Each setting below links to the Cursor documentation page it comes from. The rollout sequence and governance baselines are our recommendations, not vendor requirements. Cursor's own setup guides are on Team pricing, SSO setup and Grok Bot for Teams and Enterprise.
Want help hardening agent-built software or standing up governed Grok Bot workflows? Start with our AI workflow diagnostic or work with our Forward-Deployed Engineers.
We recommend piloting with one engineering pod or one operations workflow for four to six weeks. Assign Premium seats as the default and step up to Super or Ultra only for engineers who exhaust the weekly pool on real delivery work. Decide up front whether self-serve Teams' always-on Grok Bot access is acceptable for the pilot cohort.
We recommend moving off Legacy Privacy Mode (which blocks Grok Bot), verifying your company domain, configuring SAML or OIDC SSO, and testing sign-in before inviting the wider team. On Enterprise, configure SSO first because SCIM 2.0 depends on an active SSO connection.
Assign users directly to the Cursor app in your identity provider or to a top-level assigned group. Nested IdP groups often fail sign-in (such as Entra ID error AADSTS50105), and existing pre-SCIM users remain on the team until removed or synced.
Before members sign in, enforce Privacy Mode team-wide, audit Team Marketplace connectors, turn off public Bot template sharing, restrict Bot sharing to Admins only if shared Bots require review, set Execution on Local Computer to Never allow unless local tasks are needed, and set both team and per-member monthly caps on the prepaid balance. Also check TLS proxy exemptions (`*.*.cursorvm.com`) if staff sit behind Zscaler or a similar gateway.
We recommend publishing a short Team Rules baseline, training members never to paste credentials into chat (using Vault or masked secret cards instead), and reminding staff that every Bot on one account shares the same cloud computer. Start Bots on read-only and draft workflows with human approval on writes.
Measure delivery cycle time, review turnaround, defect escape rate and rework on the pilot backlog, alongside weekly pool and prepaid spend per seat. Do not judge success by lines or percentages of code generated. Report time saved as estimated.
After the pilot, expand on Teams if self-serve controls and per-seat pools fit, move to Enterprise if you need group-gated Grok Bot access, SCIM, pooled usage, network allowlists or audit logs, or stop where a workflow shows no measured gain.
Grok Bot (often searched as one word, Grokbot) is Cursor and SpaceXSI's cloud computer-use agent for standing work across browsers, files, terminals and connected apps. Isolation model: Each user gets a dedicated cloud computer in a Firecracker microVM; all Bots that user runs share that computer, and Team Bots carry their owner's apps, secrets and files into teammates' chats. Availability on Teams: Included on every paid Teams seat and enabled by default, with no admin switch to turn it off (stays off only on Legacy Privacy Mode or legacy request-based plans). Availability on Enterprise: Controlled by an organisation-wide Enable Grok Bot switch in the Cursor dashboard, with group-level access via Manage Group Access.
Premium seat: $30 per user a month, with the Premium weekly usage pool. Super seat: $100 per user a month, with the Super weekly usage pool (3.75x Premium). Ultra seat: $200 per user a month, with the Ultra weekly usage pool (12.5x Premium). Annual billing: $300 a year for Premium, $1,000 a year for Super and $2,000 a year for Ultra on The X Subscription. Mixing tiers: One team can mix Premium, Super, Ultra and Free seats; seat tier is separate from Member or Admin role, and Plus is not available for teams. Prices are in US dollars, excluding VAT, as of 11 November 2026.
Not included in the seat price; billed from a shared prepaid team balance at public API list prices plus the $0.25 per million token Cursor Token Rate unless exempt (Cost mode or cache-read strictly below $0.10 per million tokens across every tier). Spend controls: Shared prepaid balance with a monthly team cap, default per-member cap and per-member or directory-group overrides; a separate Grok Bot-only spend cap is not available. We recommend setting a monthly team cap and per-member limits on the prepaid balance before enabling third-party models.
No. Included on every paid Teams seat and enabled by default, with no admin switch to turn it off (stays off only on Legacy Privacy Mode or legacy request-based plans). If your organisation needs an admin kill switch or wants to restrict Grok Bot to selected directory groups, use Enterprise: Controlled by an organisation-wide Enable Grok Bot switch in the Cursor dashboard, with group-level access via Manage Group Access.
Sharing defaults: Public template sharing starts allowed on self-serve Teams and off on Enterprise; Bot sharing defaults to Everyone; Page sharing defaults to Anyone on the team; Slack Workspace Access is on by default; Allow Shared Logins and Agent Email are off by default. Local execution: Team ceiling defaults to Always allow while each member defaults to asking per task; Cursor recommends setting Never allow unless Bots need local file access. We recommend reviewing these settings before sending team invitations.
Where Grok Bot computers run: Hosted in the US; Cursor offers a US-only data residency programme for inference, processing and storage through account teams. Data residency in South Africa: Varies by region; check at checkout. Treat both Cursor and Grok Bot as cross-border transfers under POPIA.
Billing currency in South Africa: Varies by region; check at checkout. Budget in US dollars until checkout or your Enterprise quote confirms your billing currency.
Check Cursor's Data Processing Agreement and 30-day deletion clause, your cross-border transfer basis to the United States, team-wide Privacy Mode enforcement, subprocessor rules (because Grok Bot manages its own model mix outside the editor model allowlist), sharing defaults on shared Bots and templates, and sign-off from your information officer. This is a starting point, not legal advice.
Our AI workflow diagnostic takes about two weeks. It baselines one process, checks data and security feasibility, and ends with a go/no-go decision. It can conclude that you need no AI build at all.
Planning a rollout now? Book a call with Rob and Amanda.
