The OpenClaw alternative with no gateway to keep alive
Download it, sign in, type the job. A companion pulls every July invoice out of the billing dashboard and tells you which three you were charged twice for.
Switching costs one download and a sign-in. Type “pull every invoice from the billing dashboard for July and tell me which three we were charged twice for”, and a companion works it in tabs you are already signed into, on credits that are already there, with a card in front of every send, record change and payment.
Both keep the agent on your side of the network. The difference is who assembles it: no gateway to host, no provider key to paste, no channel to pair, no Saturday spent on tool policy.
| Strawberry | ||
|---|---|---|
| What you install | A gateway you configure | A browser you sign into |
| Model access | Your own key, 35+ providers | Credits included; plans from $20/month |
| Where it meets you | WhatsApp, Telegram, Slack and seven more | A chat panel beside your tabs |
| Reach | Shell, files, cron, a browser tool | The logged-in web, plus 93 native integrations and 1,975 connectable apps |
| Acts inside accounts you are already signed into | Depends how you wire the browser tool | Yes, by construction |
| Recurring work | A cron tool you wire up | Routines saved from the chat, with the run history beside them |
| Approvals | Tool policy and exec approvals you set | Approval cards, Ask Always mode |
Which half of OpenClaw are you actually using?
Four things sit on OpenClaw’s side of the line.
The shell. The phone, because it answers in WhatsApp and Telegram. The MIT licence and readable source. And the tinkering, which for some people is the appeal.
Everything else on your list is behind a login: the portals, the trackers, the dashboards. That half is what a companion takes, and the rest of this page is about it.
What arrives already built
The unglamorous parts you would otherwise assemble.
- Model access as credits: free to start, paid plans from $20/month, no provider account of your own.
- Native integrations for Gmail, Outlook, Slack, Notion, Linear, Zoom and Apollo, as first-class tool calls rather than page-driving.
- Scheduled routines for the weekly jobs, so recurring work is a setting rather than a cron entry.
- An approval card in front of consequential actions, and Ask Always mode in Settings → AI permissions when you want everything to wait.
- Meeting prep and transcription, which no gateway ships and nobody wants to build.
Is a local agent with your logins safe?
An agent holding your session can reach whatever you can reach, so the brakes are built in rather than configured afterwards. Sensitive actions pause on a card naming the exact action, you can watch the tab while a companion works, and Ask Always mode extends the pause to everything.
OpenClaw’s answer is a tool policy enforced before the model call, plus exec approvals and allow lists. That is a configuration file. Ours is a default. The full model is at /security.
Running both is allowed
Nobody makes you choose. The gateway keeps the machine-level and messaging work it was built for. A companion takes the browser-shaped chores: 30 profiles read for job changes, four pricing pages diffed against June’s screenshots, seven vendor onboarding forms filled from one sheet. Finished runs of that kind are at /real-runs, and the fuller list is at what can an agentic browser actually do.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents