App Developer Studio

Enterprise AI guides

Grok Business and Enterprise: plans, pricing and rollout for South African companies

Grok Business is SpaceXSI's self-serve team plan with a published per-user price. Grok Enterprise adds organisation-wide governance, Custom SSO, SCIM directory sync and optional Enterprise Vault isolation, and is quoted by sales. This guide sets out what each plan includes, what it costs, and how we recommend a South African company runs its first rollout.

Every price and policy below comes from public SpaceXSI and 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

Plans and prices

Grok Business and Enterprise prices

Business has a published monthly price per user through a self-serve portal, so smaller teams can budget before speaking to sales. Enterprise is custom-quoted for organisations that need central identity, multi-team oversight or dedicated isolation.

Grok Business
ItemPlanDetailSource
Seat price, billed monthlyBusiness$30 per user a monthx.ai
Seats and onboardingBusinessSelf-serve portal for small-to-medium teams, with team and seat management and consolidated billingx.ai
Included models and toolsBusiness and EnterpriseGrok 4.7, Imagine, Voice and Grok Build, with increased rate limitsx.ai
Authorised purchase channelBusinessSelf-serve subscriptions are sold directly only; xAI authorises no third-party resellersx.ai

Prices in USD as of , excluding VAT. Check the vendor page before you buy.

Grok Enterprise
ItemPlanDetailSource
PricingEnterpriseNo public price; contact SpaceXSI sales for custom rate limits, volume pricing and dedicated onboardingx.ai
API teams and organisation consoleBusiness and EnterpriseGrok Business and xAI API teams are managed in the xAI console; Enterprise links multiple teams under one organisationdocs.x.ai

Prices in USD as of , excluding VAT. Check the vendor page before you buy.

South African billing and Grok Bot access

Public SpaceXSI pages quote US dollars excluding tax. Self-serve Grok Business seats can also sign in to Grok Bot (often searched as Grokbot), while engineering teams adopting Cursor alongside Grok Bot should review our Cursor and Grok Bot for Teams guide.

Billing in South Africa and Grok Bot access
ItemPlanDetailSource
Billing currency in South AfricaBusiness and EnterpriseVaries by region; check at checkoutx.ai
Grok Bot accessBusiness and EnterpriseAssigned seats on self-serve Grok Business can sign in to Grok Bot with that Grok account; Grok Enterprise customers arrange Grok Bot access with their account managercursor.com

As of . Check the vendor page before you rely on it.

What each plan includes

Identity, Enterprise Vault and data controls

Unlike some rivals that include SSO on their entry business plan, Grok places both Custom SSO and SCIM on Enterprise. Business includes domain verification, role-based access control, custom data retention and no training on business data.

For regulated or highly sensitive workloads, Enterprise Vault isolates customer data on a dedicated data plane away from the shared consumer stack, with customer-managed encryption keys and application-level encryption.

Identity, isolation and compliance controls
ItemPlanDetailSource
Domain verificationBusiness and EnterpriseDomain verification and claims on Business and Enterprise; Enterprise adds organisation-wide domain associationx.ai
Single sign-onEnterpriseCustom SSO on Enterprise onlyx.ai
SCIM directory syncEnterpriseEnterprise onlyx.ai
Role-based access controlBusiness and EnterpriseRole-based access control on Business; custom role-based access control and advanced user management on Enterprisex.ai
Enterprise Vault isolation and keysEnterprise VaultDedicated data plane isolated from the shared consumer stack, customer-managed encryption keys (CMEK) and application-level encryptionx.ai
Audits and complianceBusiness and EnterpriseSOC 2 Type I and Type II, HIPAA, GDPR and CCPA listed on the Grok Business pagex.ai

As of . Check the vendor page before you rely on it.

Training and data retention
ItemPlanDetailSource
Training on business dataBusiness and EnterpriseNot used for model training on Business or Enterprisex.ai
Data retentionBusiness and EnterpriseCustom data retention and advanced audit and security controls on Business and Enterprisex.ai

As of . Check the vendor page before you rely on it.

Data residency

South African data residency is not confirmed

SpaceXSI lists data residency as an option on custom Enterprise plans, without publishing a public list of regions or confirming hosting in South Africa. We recommend treating both Grok Business and Grok Enterprise as cross-border data transfers from the start unless your written Enterprise contract commits to a specific region that satisfies your policy.

Data residency by plan
ItemPlanDetailSource
Data residencyEnterpriseAvailable on custom Enterprise plans; SpaceXSI does not publish a public list of regionsx.ai
Data residency in South AfricaBusiness and EnterpriseVaries by region; check at checkoutx.ai

As of . Check the vendor page before you rely on it.

POPIA

What to check for POPIA

These are the questions we would settle with your legal and security teams before a pilot handles personal or confidential company information. This is a starting point, not legal advice.

  • SpaceXSI's commercial data processing terms, and whether they cover every Grok and API workspace your team opens.
  • Your legal basis for cross-border transfer outside South Africa, since public documentation does not confirm a South African residency region.
  • Custom data retention settings in the xAI console that match your records policy.
  • Whether sensitive business workloads require Enterprise Vault's dedicated data plane and customer-managed keys.
  • Connector permissions in tools such as Google Drive, Slack and CRM systems before users link accounts.
  • The SOC 2 reports and security documentation your risk team needs for supplier onboarding.
  • Written guidance on what staff may enter into Grok, signed off by your information officer before launch.

Choosing a plan

When Business is enough, and when you need Enterprise

Business is enough when

  • A small or mid-sized team can run a bounded pilot through self-serve billing.
  • Your security policy permits console invitations without SAML SSO or SCIM during the pilot.
  • Domain verification, role-based access control and custom data retention cover your baseline controls.
  • You want a published monthly per-user price bought directly from the vendor.

You need Enterprise when

  • Your security team requires SAML or OIDC single sign-on before staff use the tool.
  • Joiners, movers and leavers must sync automatically from your identity provider via SCIM.
  • Multiple business units or xAI API teams need unified oversight under one organisation.
  • Workloads require custom residency commitments or Enterprise Vault's dedicated data plane and CMEK.

The trade-off: Enterprise has no public price, so agree your pilot scope before requesting a quote.

How to roll out Grok in a South African company

Each setting below links to the public SpaceXSI page it comes from. The sequence, pilot sizing and outcome measures are our recommendations, not vendor requirements. Vendor setup steps are on the Grok Business overview and the Enterprise organisation guide.

Need hands-on rollout or integration support? Start with our two-week AI workflow diagnostic, or see how our Forward-Deployed Engineers take Grok and xAI API workflows into production.

  1. Step 1. Pilot scope

    We recommend starting with one operational workflow and one team rather than issuing licences across the business. Pick a process with a measurable baseline, such as engineering specification search or proposal preparation, and purchase self-serve seats directly from the official site.

    Seats and onboarding
    Self-serve portal for small-to-medium teams, with team and seat management and consolidated billing (x.ai)
    Authorised purchase channel
    Self-serve subscriptions are sold directly only; xAI authorises no third-party resellers (x.ai)
  2. Step 2. Identity and provisioning

    We recommend deciding early whether your pilot can run without SSO. On Grok Business, admins invite users in the console; Custom SSO and SCIM require Enterprise. On Enterprise, associate your domain, configure and test SSO, then map IdP groups to priority-ordered roles before turning SCIM on.

    SpaceXSI warns that activating SCIM is disruptive and can grant or remove access to resources immediately. Review the organisation preview and notify staff before clicking Activate.

    Domain verification
    Domain verification and claims on Business and Enterprise; on Enterprise, domain association links every sign-in from your company email domain to the organisation (docs.x.ai)
    Single sign-on setup
    Enterprise only, configured at console.x.ai/organization for providers such as Okta, Azure AD and Google Workspace, with a test step before organisation-wide enforcement (docs.x.ai)
    Vendor-recommended order
    Configure and test SSO, notify staff in advance, and check the SCIM preview carefully before activating because SCIM is disruptive and can grant or remove resource access (docs.x.ai)
    Provisioning without SCIM
    Self-serve user invitations, access controls and seat management in the xAI console (x.ai)
    SCIM directory sync
    Enterprise only: connect your IdP, create priority-ordered roles, map IdP groups at sso.x.ai, assign teams, permissions and licences, then preview before activating (docs.x.ai)
  3. Step 3. Admin and data policies

    Before inviting the pilot group, set custom data retention to match your records policy, define admin and member roles, and enable only the connectors the workflow needs. When connecting document stores such as Google Drive, confirm folder sharing hygiene first because Grok inherits each user's Drive permissions.

    Admin roles
    Role-based access control on Business; Enterprise adds unlimited custom SCIM roles ordered by priority, with Member as the default fallback role (docs.x.ai)
    Connectors and apps
    Connectors for Google Drive (respecting existing Drive file permissions), Slack, Notion, Salesforce, HubSpot and custom MCP servers (x.ai)
    Retention settings
    Custom data retention on Business and Enterprise (x.ai)
    Spend controls
    Consolidated billing, seat management and usage analytics on Business; custom rate limits and volume pricing on Enterprise (x.ai)
  4. Step 4. User enablement

    We recommend running one practical workshop built around the team's real documents, backed by a short page of approved use cases and forbidden data types. Name an internal owner for questions during the first month.

  5. Step 5. Measuring outcomes

    Measure workflow results rather than message counts. Record time per deliverable, cycle time and rework before launch, then measure the same tasks after four to six weeks. Label any projected time savings as estimated.

  6. Step 6. Scaling decision

    At the pilot review, decide whether to stay on Business, upgrade to Enterprise, or stop. Move to Enterprise when you need Custom SSO, SCIM, multi-team governance or Enterprise Vault. Stop or redesign the workflow if measured gains do not clear the cost of the seats.

    Single sign-on
    Custom SSO on Enterprise only (x.ai)
    SCIM directory sync
    Enterprise only (x.ai)
    Enterprise Vault isolation and keys
    Dedicated data plane isolated from the shared consumer stack, customer-managed encryption keys (CMEK) and application-level encryption (x.ai)

Questions we get asked

Grok Business and Enterprise FAQs

Next step

Test one workflow before you buy seats for everyone

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.