- Compare
- Ray vs OpenClaw
OpenClaw runs on your machine. Ray runs for your team.
OpenClaw is free, MIT licensed and one of the most starred projects on GitHub. Here is what running it actually costs, and when that trade is the right one.
Compared against OpenClaw's own pages. Last checked August 2026.
What OpenClaw is
An open-source agent, MIT licensed, that runs on your own hardware rather than a vendor's. It connects to the messaging apps a team already uses, Signal, Telegram, Discord, WhatsApp and Slack among them, ships a large library of skills, keeps its configuration and history locally, and drives an external model you supply the key for: Claude, a GPT model, DeepSeek or another. It is maintained by the OpenClaw Foundation. OpenClaw's own page
One message, two outcomes.
What happens to the same sentence in your channel, depending on which of the two is in the room.
Jonasin #eng
The webhook retry logic is dropping events again, someone should track that properly.
Ray
- Files it in Linear from the thread itself
- Shows you the approval card before it writes anything
- Works the same whoever is online, on one shared install
OpenClaw
- Can do the same work, and reach tools Ray does not
- Runs on one person's machine, under their own model keys
- What it does before asking is what they configured
The difference, in one table.
What each one is for, side by side. OpenClaw's column comes from their own pages, checked August 2026.
| Dimension | Ray | OpenClaw |
|---|---|---|
| What it costs | Flat by team size, from the free tier upward | Nothing for the software, plus your own model keys and hosting |
| Who runs it | We do. There is nothing to host and nothing to update | You do, on your own hardware, with your own keys |
| Chat platforms | Slack today | Signal, Telegram, Discord, WhatsApp and Slack among others |
| Before a write happens | An approval card, structurally, with no off switch | Whatever the person who set it up configured |
| Whose install it is | The team's, shared, with per-member tool identity | Whoever's machine it runs on |
| Memory of your team | Org memory you can inspect, correct and purge | Configuration and history kept locally on that machine |
| Where your data goes | Our infrastructure, never shared with ad platforms | Your machine and the model provider you chose |
What Ray costs
Free covers 25 tasks a month plus a one-time 50-task starter grant that never expires. Pro is one flat price for your team’s size: $49 a month for 1 to 3 people, $99 a month for 4 to 10 people, $199 a month for 11 to 25 people. No seats, and using Ray more never costs more.
What OpenClaw costs
The software is free, under the MIT licence, and that is not a trial or a tier. What you pay instead is everything around it: the model API keys it drives, the machine it runs on, and the time of whoever keeps both working. Those costs are real but they are yours to size, and for a technical team who would rather own them, free is genuinely free. their pricing page
Which one you should pick
The honest version, their side first.
Choose OpenClaw if
- Cost is the deciding factor. OpenClaw is free and Ray is not, at any size we sell. If your team has the skills to run it and would rather spend them than money, that is a sound trade and we will not pretend otherwise.
- You want your data on your own hardware. OpenClaw runs locally and keeps its history there, which is a guarantee a hosted product cannot make.
- Your team is not on Slack. OpenClaw reaches Signal, Telegram, Discord and WhatsApp today, where Ray is Slack-only.
- You want to change how the agent works. It is MIT licensed with a large skills library and a very large community, so you can read it, fork it and extend it. Ray is none of those things.
Choose Ray if
- Nobody on your team wants to be the person who owns the machine, the keys and the updates. That job is real, it lands on one person, and it does not go away.
- You want approval to be structural rather than configuration. On Ray no setting turns it off, so what waits for a yes does not depend on who set it up.
- You want one install the whole team shares, where each person's writes go out under their own connected account rather than under one operator's keys.
- You want the bill to be a line item you can predict rather than model usage you have to watch.
What OpenClaw does not do
Each one checked against their own documentation, August 2026. If any of this changes, tell us and we will fix it.
- There is no managed OpenClaw to buy. Nobody keeps it running for you, nobody is on the other end when it stops, and the upgrade is yours to do. That is the deliberate shape of the project rather than a gap in it, and it is the whole of what Ray is selling against. their docs
The rest of the field
If you are still drawing up the shortlist, these are the other tools people weigh against OpenClaw and against Ray. Each one says where it is the better pick.
Ray vs ViktorViktor charges by credits. Ray charges by team size.Ray vs Claude TagClaude Tag needs Claude seats. Ray needs a Slack channel.
Ray vs Grok BotGrok Bot drives a computer. Ray works your tools.Ray vs ChatGPTChatGPT is an assistant you ask. Ray is a teammate that acts.
Ray vs GeekbotGeekbot collects the updates. Ray does the work.Ray vs StanduplyStanduply runs the ceremonies. Ray finishes the work.
Ray vs DailyBotDailyBot makes the work visible. Ray moves it.
Ray vs Slack AISlack AI understands your Slack. Ray works outside it.
Ray vs Zapier AgentsZapier reaches everything. Ray lives where you talk.
Questions people ask.
The short answers are here. If we have not covered something, just ask.
Try Ray with your own team.
Free to start, no card. Ray sees only the channels you invite it to, and nothing sensitive happens without your approval. Or read OpenClaw for their side of it.