Rakazo is an open-source, self-hosted AI agent for persistent teammates that people manage from chat. Each bot signs into the tools a person already uses, works through a sandboxed browser and shell, and pauses for approval when work crosses a boundary the owner sets. It serves individuals and small teams who want Grok Bot style delegation while keeping credentials, data, and infrastructure on a machine they control.[1][2]
Quick verdict
Our assessment is that Rakazo fits solo operators and tiny teams who want chat-managed bots operating their existing tools, because persistent memory, routines, and sandboxed computers carry recurring work forward. Its documented strengths are tool sign-in with approval boundaries, per-bot model choice, and local custody of credentials and data. Its material constraints are mandatory self-hosting with Docker and user-supplied model keys, beta status with no documented SSO or enterprise support, and a waitlist-only hosted Cloud. A person matching that profile should evaluate it against OpenClaw; anyone needing zero-setup delegation should choose a hosted product instead.[1][2][3]
Capabilities
Persistent bots with memory and routines Each bot keeps its own conversations, memory, routines, and history, so recurring work such as inbox sweeps carries context forward instead of starting cold.[1]
Tool sign-in with approval boundaries Bots sign into your tools the way you would and complete tasks while you are away, pausing to ask for approval when work crosses a boundary you set.[1]
Sandboxed browser, shell, and desktop Every bot works through a sandboxed browser and shell, with terminal, file, and graphical desktop access, isolated from the rest of your machine.[1][2]
Bring your own model per bot Each bot can use a different model across Claude, GPT, Grok, OpenRouter, and local servers such as Ollama, so triage can run cheap while writing runs smart.[1][2]
Voice mode with your own voice keys Bots speak replies, take dictation, and hold calls using a caller-supplied ElevenLabs, OpenAI, Cartesia, or Fish Audio key.[1]
Delegation to peers and subagents Bots hand work to peer bots or spin up short-lived subagents, which suits parallel jobs such as researching accounts while drafting outreach.[1]
Shared and private computers Teams share Team Computers while keeping Private computers isolated, with local Docker computers on by default and E2B, Daytona, CreateOS, or Box as optional remote providers.[1][2]
Broad integration sources App connectivity runs through Composio or Pipedream Connect plus user-installed Treg, remote MCP, and OpenAPI tool sources, rather than a fixed integration catalog.[1]
Who it fits
Solo operators delegating tool chores from chat: persistent bots that report back in conversation remove the context-switching tax on triage, follow-ups, and drafting.[1][2]
Technically comfortable Mac owners with model subscriptions: existing Claude or ChatGPT spend converts into staffed bots with no new seat fees.[1][2]
Privacy-minded users wanting local custody: sessions, credentials, Postgres, and the audit log stay behind their own firewall.[1][2]
Boundaries to check
People who will not run infrastructure: Docker, an always-on machine, and upgrades are required, and hosted Cloud is waitlist-only.[1][2]
Teams needing documented SSO or enterprise support: neither is documented and the project states beta status.[1][2]
Anyone needing guaranteed offline operation: cloud models need connectivity and fully offline behavior is undocumented.[1][2]
Questions worth asking
What is the best Rakazo alternative for non-technical users?
A hosted assistant that needs no Docker, server, or model keys fits better, because Rakazo currently requires self-hosting and user-supplied credentials. Among self-hosted options, OpenClaw is not simpler: its documented path adds a CLI, an onboarding wizard, a gateway service, and a config file.[1][2][3]
Is Rakazo really no-code?
Operating Rakazo is chat-based and needs no code: bots are set up by interview and managed from conversation with Markdown routines. Running it still calls for Docker Engine, the Compose plugin, an installer script, and a connected model, and source installs additionally need Node.js and pnpm.[1][2][3]
How much does Rakazo cost per month?
Can you self-host Rakazo?
Sources and editorial review
Source research. Reviewed on October 12, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Rakazo - Open source Grok Bot alternative
official · Observed October 12, 2026
Official homepage: open-source Grok Bot alternative positioning; persistent bots sign into tools with sandboxed browser and shell and approval boundaries; per-bot model choice; setup interview; web, desktop, and mobile chat; self-host offer plus Cloud waitlist; GitHub and iPhone app links.
- Self-Hosted AI Agent (Open Source) - Rakazo
official · Observed October 12, 2026
Official self-hosting guide: Apache-2.0 license; hosted Cloud not generally available; no seat fee with user-paid model and computer providers; Docker Engine 26 plus Compose or Node 22 with pnpm 9 source checkout; Postgres, bot files, and audit log on user machine; supported model providers.
- elie222/rakazo repository
official · Observed October 12, 2026
Official repository: open-source Grok Bot alternative with user-chosen model and sandbox; Apache-2.0 license; Docker, E2B, Daytona, CreateOS, and Box computers; published Docker images and source install paths.
- Open Source OpenClaw Alternative - Rakazo
official · Observed October 12, 2026
Official vendor comparison updated October 7, 2026: Rakazo as chat-managed open-source OpenClaw alternative via Docker installer under Apache-2.0; OpenClaw as CLI plus wizard plus gateway plus config file under MIT; Markdown routines; web, desktop, and mobile management.
- Rakazo README
official · Observed October 12, 2026
Official README: persistent teammates on web, Electron desktop, iPhone, and Android APK; alternative to Grok Bot, Meta Muse, OpenAI Dots, Instinct, OpenClaw, Hermes Agent, Hark Pro; beta status; voice mode, delegation, shared and private computers, integration sources; stack TypeScript, React, Electron, Expo, Hono, oRPC, PostgreSQL, Prisma, Better Auth, Graphile Worker, Pi, Docker, E2B, Daytona, CreateOS, Box.
Compared with these products
No explicit proprietary baseline is recorded.