Michael
vsGrokBot

Their bot. Or your bot.

GrokBot drops xAI's assistant into your workspace and tells you little about how it works. Michael connects to your stack, runs on models from every lab, and shows you everything he does.

Get started for freeBook a demo
4 min readUpdated September 2026

A bot in your Slack is not a bot you own.

Both products show up as a name in your sidebar. The difference is whose bot that name is. GrokBot is xAI's assistant visiting your workspace: one lab's models, one vendor's terms, and not much visibility into either. Michael is hired by you, routes across every frontier model, and opens his workings to you. Same sidebar. Very different employment contract.

MichaelAI coworker

Your bot. He routes across every frontier model, holds only the credentials you grant him, logs every action where you can read it, and stops to confirm anything he cannot undo.

Every frontier modelYou own the memoryFull audit trail1,000+ tools
GrokBot
GrokBotSlack bot, from xAI

xAI's bot in your workspace. Capable and fast, but it runs xAI's models, on xAI's terms, and is opaque about how it decides, what it keeps, and why.

xAI models onlyOpaque workingsxAI's termsAnswers in place

Same sidebar. Different employer.

Tools it reaches
1,000+
Stripe, HubSpot, your repo, scoped to your workspace
GrokBot. Whatever xAI wires in, on xAI's say-so
Models it runs
Every lab
Grok included, picked per job
GrokBot. xAI's models, whichever one they point it at
Who it answers to
You
Your workspace, your memory, your audit log
GrokBot. xAI, with a black box in between

The unglamorous work is still the work.

Nothing about this exchange is interesting to the internet. It is four tabs of reconciliation that somebody on your team was going to lose a morning to.

# growth ⌄
Lisa
Lisa9:02 AM

Audit our Meta and Google spend for May, month over month.

MichaelAPP9:02 AM

Pulling the numbers now. ETA 4 min.

MichaelAPP9:06 AM

Done. Meta CPA is down 12% and ROAS is up to 3.4x. Google pMax is underperforming. I flagged 3 campaigns to pause in the doc.

PDF
ads-audit-may.pdfView PDF in Slack
42

Every step of this is logged where you can read it: what he opened, what he pulled, what he wrote. Ask a black-box bot for the same job and you get the answer without the receipts, which is fine until somebody asks where the numbers came from.

Line by line. No asterisks.

The core job
MichaelTake work off your plate and finish it.
GrokBotAnswer in the thread, on xAI's terms.
Models
MichaelRoutes across every frontier lab, Grok included, picked per job.
GrokBotxAI's models. One lab, good quarters and bad.
Control
MichaelYou set his channels, his tools, his standing jobs, and what needs a confirmation.
GrokBotYou take the defaults it ships with.
Ownership
MichaelYour workspace owns the memory. Your taste, your corrections, yours to keep.
GrokBotWhat it keeps, and where, is xAI's business to know.
Transparency
MichaelEvery action logged and readable in the web app.
GrokBotOpaque. You get the reply, not the workings.
Private data
MichaelConnected by OAuth, workspace scoped, never crossing tenants.
GrokBotGoverned by xAI's terms rather than by you.
Deliverables
MichaelFiles. Decks, spreadsheets, dashboards, shipped code.
GrokBotText in the thread.
Live public signal
MichaelNot his job. He is built for your stack, not the feed.
GrokBotGenuinely strong, straight from X. A real edge.
Risky actions
MichaelStops and shows the exact action before he takes it.
GrokBotYou do the acting, so the question does not come up.
Price
MichaelFrom $19 a month.
GrokBotAn xAI or X plan, per seat, by tier.

The row that frames the rest is models. A bot tied to one lab is only ever as good as that lab's current quarter, and you find out about the bad quarters from the quality of your work. Routing across labs is not a spec-sheet line. It is the difference between your bot and theirs.

Three steps, or an install.

GrokBot wins this section outright, and it should. Installing an app is not a project. It is also not a connection to your stack, or any say in what happens next.

Michael3 steps
  1. Add Michael to Slack.
  2. Connect Stripe, Gmail, and one ads account.
  3. Give him a job.
GrokBot3 steps
  1. Install the app.
  2. Take the defaults it ships with.
  3. Ask, and take the workings on trust.

What that looks like on a real team.

One customer, the two numbers they measured, and what they said about it.

Phelix.ai
Michael, in production
“The time and money savings of Michael have been incredible. My team is able to operate at a far greater velocity now, enabling us to hit aggressive targets in market expansion.”
Hassaan Ahmed
Hassaan Ahmed
CEO, Phelix.ai
10×
Ticket resolution
5×
Development velocity
Impact
Aggressive market-expansion targets, hit.

Where GrokBot is the better call.

We would rather you trust this page than convert off it.

The question is about right now.

What is the reaction to this launch, what is the argument about this morning, who is saying what. Real-time signal on the public conversation is a genuine edge and Michael does not compete for it.

You want xAI end to end.

One lab, one bill, and the deepest possible tie into X. If your world already runs there, a single vendor with no routing layer in between is a coherent choice.

You do not need to see the workings.

If fast answers matter more than knowing how they were produced, the opacity costs you nothing. It only gets expensive the day someone asks you to stand behind the output.

What each one actually costs.

The honest read is not which plan is cheaper. It is what each one buys: a bot you own and can audit, or a seat at somebody else's table.

Michael
From $19/ month
  • Starter $19, Pro $99, Max from $199.
  • Every frontier model, routed per job, in the price.
  • Your memory, your audit log, your bot.
GrokBotGrokBot
xAI plan
  • Priced by xAI, per seat, by tier.
  • Bundled with the X tiers that include it.
  • xAI's models, xAI's terms, xAI's black box.

Pick the one that fits.

Choose Michael if
  • You want the best model for each job, not one lab's current best.
  • You want to see and steer what your bot does.
  • The memory and the audit trail should belong to you.
  • The work crosses your private tools and ends in a file.
  • You want the same job to run every Monday without asking.
Choose GrokBot if
  • Your world already runs on X and xAI.
  • One vendor and one bill matters more than model choice.
  • Live public signal is most of what you ask for.
  • You are comfortable taking the workings on trust.

Short answers.

Is GrokBot the same as Grok?
Same lab and same models, different doorway. GrokBot is the bot form of xAI's assistant, and it inherits the same posture: xAI's models, xAI's terms, and not much said about what happens in between.
Which models does Michael use?
He routes across frontier models, Grok included, and picks the right one per task. You never choose a model, and no single lab's bad quarter becomes your bad quarter.
What does 'owning your bot' actually mean?
The memory is scoped to your workspace and stays yours. The credentials are ones you granted and can revoke. Every action is logged where you can read it. If you leave, you are not leaving a trained-up assistant behind for the platform to keep.
Can I use both?
Yes. GrokBot for the live public conversation, Michael for the inside of your company.
Will he post anything publicly?
No. Anything he cannot undo stops first. He shows you the exact action and waits. There is no timeout that decides for you.

Hire the bot that works for you.

Same sidebar, different employer. Give Michael the job with four tabs and no glamour in it, and read what comes back, with the receipts.

Get started for free →Book a demo
From $19 a monthCancel anytimeLive in 3 minutes