Rakazo is an open-source Grok Bot alternative for running persistent AI teammates. Each bot combines a long-lived thread, memory, routines, and history with access to a working computer.
A Rakazo bot uses a live desktop for websites and graphical applications, shell commands, and file operations. It can return to the same work later with its history and workspace intact.
For example, an inbox bot can return to yesterday’s browser session and continue its scheduled cleanup. A development bot can pick up an unresolved issue with its earlier notes and files. You can bring these bots into a shared chat when a task needs both of them.
Persistent Bots and Their Computers
Rakazo bots return to their existing threads, memory, and working files when a new conversation or routine begins. You can give a bot Markdown instructions for recurring work, and it can use the files and history from earlier runs as it proceeds.
The bot works on a graphical desktop with a browser, terminal, applications, and files. It can navigate websites, interact with web apps, and run commands. For a technical investigation, it can inspect a page in the browser, review project files, run a diagnostic command, and save its findings for the next session.
Bots in a team normally work on a Team Computer. Each starts in a bots/<bot-id>/ folder, and files for collaboration can go into shared/. These folders organize the work; every Team bot can access the computer’s workspace. You can assign a Private Computer to a bot that handles confidential files or browser sessions.
The live computer viewer shows what a bot is doing. If a task needs a manual login or other human action, use Take Control to interact with its desktop. Settings -> Approvals controls which bot actions need consent, and the audit log records earlier actions. Purchases require a person’s approval, with the order items and spending amount shown in the request.
Bots Working Together: Group Chats and Spaces
A group chat lets several bots work on one question. Mention a bot to assign part of the investigation, and the bots can exchange messages as they make progress. A persistent peer can take on an ongoing responsibility; temporary subagents handle short tasks. For research that can run in the background, a bot can dispatch read-only helpers and continue the conversation until their findings return.
A Space keeps a team’s bots, group chats, memory, routines, and computer in one place. Invite colleagues to work with those bots and review the same history. Each member connects their own model and app accounts and retains their own notifications and approval settings.
Everyone in a shared Space can access the browser sessions on its Team Computer, including saved website logins. Keep credentials and sensitive files on a Private Computer when that work needs restricted access.
Recurring Tasks, Bot Email, and Shareable Pages
Schedule a bot to collect updates each morning, or have it respond to a webhook, Git event, incoming email, or watched change. Rakazo records each routine run, and you can adjust or pause the instructions from chat. A research bot, for example, can add the latest findings to its existing project files each day.
Bots can receive email at their own addresses, search their inboxes, and send replies. Receiving mail requires an inbound domain and mail relay; sending mail requires an outbound email provider. Messages from verified, permitted senders can trigger a routine, turning an incoming request into work the bot tracks in its conversation and files.
A bot can present the result as a Page, such as a dashboard, report, or document. Open it from chat, request changes in the conversation, or let a routine refresh it. Pages support view-only links and PDF export, giving teammates a usable result even when they are not following the bot’s chat.
Voice Conversations and Connected Apps
You can dictate messages, hear spoken replies, and talk to a bot in a voice call. Rakazo supports speech services including ElevenLabs, OpenAI, Fish Audio, and local speech servers. Calls and spoken responses use the voice provider configured in Settings → Voice.
For work that spans other services, connect apps such as Gmail, Slack, GitHub, Notion, and Linear. Rakazo supports Composio and Pipedream Connect catalogs, as well as remote MCP servers, OpenAPI and GraphQL tools, and GitHub-hosted plugins. Bots can read or update connected data through the actions and permissions you authorize.
Models and Costs
Rakazo runs its agents through Pi. Connect a supported subscription, supply an API key, or point Rakazo at an OpenAI-compatible model server in Settings -> Models. Assign models to individual bots and routines, and configure a fallback if a model connection becomes unavailable.
| Model or service | How to connect |
|---|---|
| Claude Pro or Max | Sign in with a supported Claude subscription. |
| ChatGPT Plus or Pro | Sign in through the supported ChatGPT account connection. |
| GitHub Copilot | Use GitHub Copilot device-code sign-in. |
| SuperGrok / X Premium | Use supported xAI sign-in or an xAI API key. |
| OpenAI, Anthropic, Google, xAI, OpenRouter and other API providers | Add a provider API key; self-hosted deployments can use an operator-managed key such as OPENROUTER_API_KEY. |
| Ollama, LM Studio, and compatible local servers | Connect the model server’s OpenAI-compatible endpoint. |
Bots that operate the desktop need a model that can interpret screenshots. The model picker identifies models that cannot read images.
Rakazo is Apache-2.0 licensed and free to self-host. You pay for your server, model API usage, and any rented computers you choose.
Managed hosting costs $15/month for Standard with 25 bot-computer hours, $49/month for Pro with 100 hours, or $99/month for Max with 200 hours. These hosted plans let you connect your own supported model access.
Rakazo also sells model credits, starting at $10/month, for models billed through its catalog.
Where Bot Computers Run
The web, desktop, and mobile apps connect to a Rakazo server. The bot’s browser and shell execute on the computer provider configured for that server. A local installation usually runs bot computers in Docker, and a hosted setup can use remote sandboxes or your own infrastructure.
To let a bot work on the machine running the desktop app, enable Settings -> General -> Let bots use this computer. Host commands then run with that computer account’s permissions.
| Computer provider | Execution location and use |
|---|---|
docker | Docker on your machine or server; default for self-hosted installations. |
e2b, novita, daytona, createos, boat, boxd, railway | Remote sandboxes. Set the provider name and its API credentials in the server configuration. |
kubernetes, incus | Computers managed by your own cluster or Incus host. |
| Desktop computer access | Use your macOS, Windows, or Linux host when you grant the desktop app permission to run commands under your account. |
Run Rakazo Locally
Install With Docker
Run the installer below to download Rakazo’s Compose configuration, generate its application secrets, and start the server.
mkdir -p rakazo && cd rakazo &&
curl -fsSLO https://raw.githubusercontent.com/elie222/rakazo/main/infra/compose/install-images.sh &&
bash install-images.shOpen http://127.0.0.1:5173, create an account, connect a model, and create a bot. The default computer provider is Docker, so the bot can open its browser and terminal once the local computer starts.
Develop From Source
Clone the repository and create its environment file:
git clone https://github.com/elie222/rakazo.git
cd rakazo
cp .env.example .envIn .env, set POSTGRES_PASSWORD and POSTGRES_APP_PASSWORD and use those credentials in DATABASE_MIGRATION_URL and DATABASE_URL. Generate values for BETTER_AUTH_SECRET, ENCRYPTION_KEY, SCREEN_PROXY_SECRET, and SANDBOX_SUPERVISOR_TOKEN. Model credentials can also be added after the server starts.
pnpm install
pnpm sandbox:build
pnpm devThe development command starts the app and its workers, applies database migrations, and launches a local Postgres container if the configured database is unavailable. Open the URL printed by Vite to sign in and create your first bot.
Desktop and Mobile Apps
Rakazo has web and desktop clients for macOS, Windows, and Linux, plus apps for iPhone and Android. The desktop app can run Rakazo locally through Docker or connect to an existing server. Mobile apps connect to the server to chat with bots, view their status, manage routines and memory, and respond when a bot needs input.
To connect to a server on a VPS, enter its HTTPS address in the desktop or mobile app. If you are developing the Electron client from a source checkout, launch it with pnpm --filter @rakazo/desktop dev and choose Existing instance to connect to the local web server. You can build a desktop package with pnpm --filter @rakazo/desktop pack.
Rakazo Use Cases
Recurring Browser and Account Work
An operations bot can return to a signed-in dashboard each morning, collect updates, and save the results in its workspace. An inbox routine can handle recurring triage, with a person stepping into the computer viewer when a message or action needs their decision.
Bug Triage and Technical Investigation
Give a development bot an issue to investigate and it can use the browser, terminal, and project files as part of the same investigation. When you return with more information, its earlier commands, notes, and files are available in the bot’s history.
Research and Content Operations
A research bot can check sources on a schedule and add findings to the working project. It can turn the latest results into a Page that colleagues can open by link and review after each routine run.
Multi-Bot Collaboration
Put a research bot, a technical bot, and a reporting bot in one group chat. You can ask one to investigate a question, have another follow up on the findings, and share the resulting Page with a team in the same Space. Long-running responsibilities can stay with peer bots, and short investigations can go to temporary subagents.
Alternatives & Related Resources
- AionUi: Free Open-source Cowork App
- Cumora: Team Chat for Humans and Persistent AI Agents
- Hermes Agent: Free, Open-source, Self-Improving AI Agent
- 7 Best OpenClaw Alternatives for Safe & Local AI Agents
- 10 Best Open-Source Grok Bot Alternatives
FAQs
Do Team bots have isolated files?
No. Team bots start in their own bots/<bot-id>/ directories. Those folders organize files; every Team bot can access the full Team Computer workspace. Use a Private Computer when the bot needs its own workspace.
What happens to an E2B computer when Rakazo replaces it?
Rakazo restores the latest checkpointed portable workspace and browser-profile data from its own DATA_DIR. System packages installed outside that portable workspace do not move with it. Reproducible images or setup scripts are the safer way to preserve machine-level customization.
Does Take Control pause the AI agent?
No. Take Control makes the embedded computer viewer accept your input. It does not automatically pause the active agent run. Rakazo has a takeover request mechanism for work that needs protected human input or judgment.










