AIREITERGrok Bot for Enterprise is officially available to eligible enterprise customers for two weeks free, but activation, post-promotion pricing, and several governance details remain account-specific.
Grok Bot for Enterprise: launch status versus buying status
Grok Bot for Enterprise is a real product launch, not a rumor or a renamed chatbot. xAI’s September 3, 2026 announcement says Grok and Cursor Enterprise customers can use it free for two weeks and invite their whole organization, including people without an existing seat. (Read the announcement)
The important distinction is that “available” does not mean “fully self-serve.” The launch page sends enterprise customers through an admin dashboard or sales contact, and the Cursor plans and billing documentation says enterprise access requires coordination with an account executive.
| Buyer question | Answer checked September 4, 2026 |
|---|---|
| Is Grok Bot for Enterprise officially launched? | Yes. xAI announced enterprise availability on September 3, 2026. |
| Is there a free enterprise offer? | Yes. Eligible Grok Enterprise and Cursor Enterprise customers get two weeks of free usage. |
| Can a company invite non-seat users? | The announcement says the entire organization can be invited, including people without an existing seat. |
| Is there a public post-promotion price? | No price, quota, overage rate, or contract minimum is stated in the launch announcement. |
| Can any company activate it instantly? | Not reliably. Enterprise enablement is account-team/admin-led, according to current Cursor documentation. |
| Is it the same as Grok Business or Grok Enterprise chat? | No. Grok Bot is the persistent, tool-using agent product; Grok Business/Enterprise is the broader organizational workspace. |
That makes this a controlled evaluation opportunity, not a budgeting decision you can complete from a public price card.
Access, eligibility, and the price you cannot yet budget
Grok Bot does not have a clearly published standalone enterprise SKU. The current commercial routes combine Bot access with eligible Grok or Cursor plans, while the enterprise launch adds a two-week promotion for existing enterprise customers.
The official Cursor plans and billing documentation lists access through paid individual Cursor Pro, Pro+, and Ultra plans, self-serve Cursor Teams, or linked individual SuperGrok and X Premium+ subscriptions. Enterprise customers are directed to their account executive. The same page says SuperGrok Team, SuperGrok Enterprise, and SuperGrok Lite are not supported for the account-linking route.
That last distinction matters. The xAI business page presents Grok Business and Grok Enterprise as the broader organization-focused offering, while the Bot documentation describes a persistent cloud-computer agent. Treat them as separate products until the contract identifies which Bot features, data terms, and controls are included.
| Commercial detail | What is public | What remains unknown |
|---|---|---|
| Enterprise promotion | Free for two weeks for Grok and Cursor Enterprise customers | Whether the clock starts at activation or on a fixed date |
| Standard Bot access | Included with several eligible Cursor and individual Grok plans | The exact weekly allowance by plan |
| Usage accounting | Cursor says paid included usage resets weekly and on-demand usage may continue after depletion | A reliable enterprise cost model for long-running Bot tasks |
| Enterprise price | Custom sales route | Per-user price, minimum seats, term, overage, and support SLA |
| xAI organization pricing | The official pricing page advertises custom rate limits, dedicated infrastructure, SSO, compliance support, data residency, and volume pricing | Which of those terms apply specifically to Grok Bot, and under which contract |
The budgeting risk is not merely that the price is missing. Agent work is metered by activity, computer-use steps, and model usage rather than by a simple message count. Cursor warns that a single long run can consume a trial credit, and that on-demand usage is enabled by default for Teams plans.
What the enterprise release actually adds
Grok Bot is designed to perform work inside the applications and websites employees already use. The official launch description says a Bot can operate around the clock, learn a workflow from a demonstration and corrections, return when it needs a decision, and communicate with other Bots.
That operating model differs from a conventional assistant that drafts an answer and stops: it is most useful when the work has a clear start and finish but the underlying system is awkward, old, or unavailable through an API.
The announcement gives these examples:
| Team | Officially described workflow | Safer first version |
|---|---|---|
| Sales | Monitor content, prepare LinkedIn/email drafts, and update a presentation during a call | Draft only; require a person to approve every outbound message |
| Recruiting | Prospect overnight, prepare a shortlist, queue outreach, and create scorecards | Use synthetic or consented data; keep candidate decisions human-reviewed |
| Marketing | Read webinar Q&A, identify relevant account executives, and prepare Slack follow-up | Send internal drafts, not customer-facing messages |
| Finance | Monitor vendor spend, usage, and renewals to find savings | Read-only reporting before negotiation or purchasing actions |
| Engineering | Monitor pull requests, failing builds, merge conflicts, and security findings | Create review queues and issues; do not grant merge or production credentials initially |
These are vendor-described use cases, not independent success-rate measurements. The launch page provides no methodology, task-success rate, latency number, uptime commitment, or independent ROI study.
Security controls: what is confirmed and what must be tested
xAI says the enterprise release adds access controls, network controls, and audit controls. The launch announcement also says each user’s work runs in a secure, isolated environment, Bots have no access by default, and a Bot can access only accounts the user signs it into.
Those are vendor claims, not a complete procurement specification. The Grok Bot FAQ and launch page do not spell out Bot-specific encryption, audit fields, retention, key management, data residency, incident response, or uptime commitments.
Treat “audit controls” as an unverified feature claim until the company can inspect the logs and contract language.
| Control area | Publicly stated position | Evidence to request during the pilot |
|---|---|---|
| User isolation | Each user’s environment is described as isolated | Tenant-boundary documentation and a test proving one user cannot inspect another’s files or sessions |
| Default access | A Bot starts with no access and needs selected account sign-ins | Account inventory, permission scope, credential revocation, and offboarding behavior |
| Network control | Enterprise network controls are announced | Allowed-destination policy, private-network behavior, egress details, and failure logs |
| Audit control | Audit controls are announced | Exportable action records showing user, Bot, tool, timestamp, approval, and result |
| Identity | The official pricing material advertises SSO and SCIM for custom plans | Whether those controls cover Bot creation, linking, provisioning, and deprovisioning—not just the parent workspace |
| Data handling | Cloud storage is required; Legacy Privacy Mode is unsupported | Retention, deletion, residency, training-use, and connector-processing terms for the exact service |
The operating limits that change the risk calculation
The most important limitations are in the operating model, not the marketing list. Grok Bot can work in a browser and remain active after a laptop is closed, but the same cloud persistence that makes it useful creates shared-state, cost, and recovery questions.
Multiple Bots share an account computer
The official FAQ says all Bots on one account share one persistent cloud computer, including files, browser sessions, and logins. Several Bots can work in parallel and have separate screens, but each Bot can run only one computer-use task at a time.
This means “multiple Bots” should not automatically be treated as “multiple security boundaries.” Do not use separate Bots on one account as the only separation between finance, customer support, and engineering credentials.
Browser automation can stop at the messy parts
The FAQ says websites without formal connectors may work through browser tools, but automation blocks, reauthentication, CAPTCHAs, and human confirmation can interrupt a run. Passwords, two-factor codes, and CAPTCHAs require the user to take over the computer.
For that reason, a workflow that succeeds in a clean demo may still need a clear exception path. A pilot should deliberately include expired sessions, ambiguous pages, blocked automation, and a failed login—not only the happy path.
Approval and deletion are not the same as isolation
Sensitive actions may pause under tool, risk, or auto-review rules. For a production rollout, require explicit human approval before sending messages, publishing content, deleting records, making purchases, or changing production systems, even if a Bot appears able to do those actions.
Deleting a Bot removes its profile, conversations, and routines, but the FAQ warns that shared-computer files and logins may remain. Treat deletion as a lifecycle event that needs manual cleanup and credential rotation.
Linking can be permanent
Cursor’s documentation says linking an individual SuperGrok or X Premium+ account to Cursor is a usage grant, not a subscription migration. It also says the link cannot be self-served unlinked or transferred to another Cursor account.
Decide which corporate identity and workspace will own the Bot before testing. A personal account linked to a corporate workspace—or a corporate entitlement linked to a personal Cursor account—creates an avoidable offboarding problem.
Real-user reports show why the access and metering details deserve testing rather than assumption:
“I started today with the Grok integration. I did basic stuff. I saw 11% of usage. That’s pretty insane.” — u/SubtleFuryTuesday in r/grok
That comment is one user’s early observation, not a universal consumption rate. It is still a useful pilot question: how much of a plan’s weekly allowance does a normal task consume, and can an administrator see the answer before on-demand charges accumulate?
A separate r/cursor discussion captures the entitlement problem from another angle:
“At least for me it doesn’t work. It always says i need to upgrade to pro (i am) … however, i am on the old pricing plan (500 Requests).” — u/MidnightRambo
This is anecdotal and plan-specific, but it supports a concrete acceptance test: verify access with the actual legacy, Teams, and Enterprise identities your company will use.
Where to pilot Grok Bot—and where not to start
Grok Bot is worth piloting when the benefit comes from persistent computer use and the downside of a wrong action is contained. It is not a sensible first choice for a workflow that can silently send, delete, purchase, approve, or alter production data without a reliable audit and rollback path.
| Start here | Add approval gates | Keep out of the first pilot |
|---|---|---|
| Internal research briefs | Customer or candidate communications | Irreversible financial transactions |
| Read-only vendor and renewal review | CRM updates and record changes | Production deployments and merges |
| Draft sales or marketing follow-up | Publishing and external posting | Unreviewed employment scoring |
| Non-sensitive inbox or ticket triage | Security-ticket creation and prioritization | Regulated data without written controls |
| Test-repository issue and build monitoring | Any action using privileged credentials | Shared personal/corporate accounts |
The strongest initial fit is draft-first work across browser-only tools: the Bot can do more than a text assistant, while a person still reviews the external effect. The weakest fit is a high-impact workflow where the organization cannot reconstruct exactly what the Bot saw, changed, and approved.
A two-week procurement pilot that can produce a yes or no
Use the free enterprise period as a controlled test, not as proof that the product is affordable or production-ready.
- Choose one reversible workflow. Use a test inbox, sandbox CRM, mock vendor portal, or non-production repository. Define the expected result and the actions the Bot must never take.
- Create a dedicated owner and test identity. Because account linking may be permanent, document the owning workspace before any employee connects a personal or corporate subscription.
- Grant the minimum useful access. Start read-only where possible. Avoid shared administrator credentials, production tokens, payment methods, and unrestricted browser sessions.
- Measure work, not messages. Record elapsed time, successful steps, retries, human takeovers, failed logins, approvals, and weekly allowance consumed. Cursor says usage resets weekly, while the exact enterprise allowance is not public.
- Force failure cases. Test CAPTCHA, expired authentication, prompt injection in a web page, contradictory instructions, missing data, and a request to send or delete something. The Bot should stop and escalate rather than improvise.
- Inspect the control plane. Confirm whether administrators can review and export action logs, revoke connected accounts, remove lingering files or sessions, manage users through the identity provider, and investigate an incident.
- Calculate the post-promo decision. Ask the account team for the price after two weeks, usage limits, overage mechanics, minimum commitment, data terms, support response, and SLA. If the answer is still informal, keep the deployment in pilot status.
A pilot passes only when the workflow is useful and the company can explain who authorized each consequential action. High task completion without recoverability is not enterprise readiness.
Grok Bot for Enterprise FAQ
The launch answers availability, but commercial and governance details still require account-team confirmation.
Is Grok Bot for Enterprise officially available?
Yes. xAI announced it on September 3, 2026, with two weeks of free usage for Grok and Cursor Enterprise customers; activation remains admin- and account-team led.
Does Grok Bot have a separate enterprise price?
No public post-promotion price, allowance, overage rate, or contract minimum is stated, so request all four before approving a rollout.
Is Grok Bot the same as Grok Enterprise?
No. xAI describes Grok Business and Enterprise as its broader organization offering, while the Bot FAQ describes a persistent agent that uses cloud computers, websites, files, and connected accounts.
Can every employee use it during the free period?
The launch announcement says the entire organization can be invited, including people without an existing seat, but permissions and usage entitlements still need confirmation.
Does each Bot get a separate computer?
No, not as a strict security boundary: Bots under one account share a persistent cloud computer, including files, browser sessions, and logins, even though they can run in parallel with separate screens.
Does Grok Bot support SSO, SCIM, and audit logs?
xAI advertises access, network, audit, SSO, and SCIM controls for enterprise/custom plans, but buyers should verify Bot-level coverage, log export, provisioning, deprovisioning, and retention.
Can Grok Bot use websites without an API?
Yes, but automation blocks, CAPTCHAs, reauthentication, and human confirmation can interrupt browser-based work.
Who should use Grok Bot for Enterprise now?
Teams with a reversible, draft-first workflow should run a limited pilot; teams needing fixed pricing, granular credentials, complete action-level auditability, or regulated-data guarantees should wait for written answers.
The decision is about control, not the demo
Grok Bot for Enterprise is worth testing because persistent browser-based work addresses a real gap, but post-promotion pricing, governance evidence, shared-computer behavior, and lifecycle controls still need account-specific verification. Use the two-week offer for one reversible workflow, then expand only if the company can control access, recover from failed actions, and forecast spend.