rakazo

Open source alternative to Grok Bot, Lindy AI, Zapier Central, Make, Simular Pro and Muse

4.9K stars
Apache-2.0
Active this week
Last commit 1 day ago

Last verified Oct 20, 2026

Run persistent AI agent teammates on your own hardware with sandboxed browsers, any LLM, and Markdown routines. Apache-2.0 licensed, no seats, no feature gates.

Visit website GitHub4.9K Deploy on Hostinger

Read the full breakdownWho it is for, how it works, trade-offs, the quick start and the FAQ

who it's for

Who rakazo is for#

Developers automating repetitive operational workflows

Rakazo gives developers a self-hosted platform to run bots against real tools, such as email, GitHub, or a CRM, with sandboxed browser sessions and persistent memory. Setting up a bot that triages issues, drafts replies, or files expense reports removes repetitive work from a dev's plate without requiring a paid automation subscription.

Skip if:

If you need zero-infrastructure setup or do not want to manage a Postgres database and Docker environment, a managed service like Lindy AI will have less friction to get started.

Small teams replacing per-task automation billing

Teams paying monthly fees to Zapier Central or Make for task-based automation can self-host Rakazo and run unlimited bots against their own workflows at the cost of server time only. Bot templates for inbox management, sales outreach, and expense filing cover common business processes without per-execution fees.

Skip if:

If your team has no one comfortable running a TypeScript monorepo and Docker stack, the self-hosting burden will likely outweigh the cost savings compared to a managed service.

Security-conscious teams that cannot route credentials offsite

Teams in regulated industries or with strict data handling policies can use Rakazo to run AI agents without sending tool credentials or workflow data to a third-party server. Every browser session runs inside the team's own Docker environment, behind their own firewall.

Skip if:

If regulatory requirements mandate formal security audits of software supply chains, the beta status and early-stage codebase will require additional review time before deployment is approved.

the problem

The problem it solves#

AI automation platforms like Lindy AI, Zapier Central, and Grok Bot charge per task, per agent, or per seat, and all of them store your workflows and tool credentials on their servers. Every automation you build adds to a monthly bill that scales with usage, and switching means migrating logic that is locked inside their proprietary workflow editors.

The harder problem is trust: your AI agents sign in to email, CRM, and banking tools on your behalf. On a managed platform, those sessions and credentials leave your machine. For teams handling sensitive data, customer records, or financial workflows, that is a real pain point with no opt-out.

how rakazo solves it

How it solves it#

Sandboxed browser and shell per bot

Each bot runs in an isolated Docker container with its own headless browser and terminal. Bots can navigate websites, fill forms, and run shell commands the same way a person would, without sharing session state with other bots or the host system.

Persistent memory and saved routines

Bots maintain conversation history, memory, and task routines across sessions. Routines are stored as plain Markdown files you can read, edit, and commit to version control, making agent behavior auditable and version-controlled like any other code.

Bring-your-own model support

Point any bot at Claude, GPT-4, Grok, or a local model via OpenRouter. Models are configured per bot, so you can use a cheaper model for routine triaging and a more capable one for complex drafts, all with your own API keys.

Approval gates and audit log

Set exactly what each bot may do without asking, and what requires your sign-off. Every action the bot takes is recorded in an audit log stored on your own infrastructure. No action happens silently, and every decision trace stays with you.

Bot templates for eight common roles

Rakazo ships with templates for Sales Outbound, Inbox Manager, Talent Scout, Expense Manager, Bug Triage, Account Manager, Paid Media, and Chief of Staff. Each template interviews you on setup to capture your workflows, voice, and tool access before getting to work.

strengths · trade-offs

Strengths and trade-offs#

Strengths

No seat pricing or feature gatesRakazo is Apache-2.0 licensed with no pricing page. Every feature in the codebase is available to self-hosters without paying for seats, agents, or tasks. Unlike Lindy AI or Zapier Central, usage does not generate a monthly bill.
Credentials stay on your infrastructureAgent browser sessions and tool logins never leave your Docker environment. For teams handling sensitive data or regulated workflows, this removes a real risk present in every managed AI automation platform where credentials transit a third-party server.
Routines stored as plain MarkdownAgent workflows are saved as readable Markdown files, not proprietary workflow graphs. You can inspect, modify, and version-control bot behavior with the same tools you use for code, and move routines between instances without a migration tool.

Trade-offs

-Multi-step install, not a single commandGetting Rakazo running requires Node.js 22+, pnpm 9, Docker Desktop, environment variable setup, a Postgres database, database migrations, and a sandbox image build. The process has six distinct steps and assumes familiarity with TypeScript monorepo tooling. Not suitable for non-technical users.
-Beta stage with active developmentRakazo was created in August 2026 and is labeled beta in its README. The project has 16 open issues and is under active development. Production deployments should account for the possibility of breaking changes between releases.
-No managed cloud option yetA hosted cloud tier (bring your own keys, managed sandboxes) is listed as coming soon but is not available at time of writing. Teams that want always-on bot availability without managing their own server must wait for the cloud option or run their own uptime infrastructure.

versus alternatives

rakazo vs alternatives#

Rakazo vs Grok Bot

Grok Bot is xAI's managed AI assistant product, available through the X platform with no self-hosting option. Rakazo is positioned as a direct open-source alternative, letting teams run persistent AI agents locally with any model.

Feature	Rakazo	Grok Bot
License	Apache-2.0	Proprietary
Self-hosting	Yes	No
Model choice	Any (Claude, GPT, Grok, local)	Grok only
Credential storage	Your infrastructure	xAI servers
Pricing	Free self-hosted	Subscription

Rakazo is the better choice when you need agent workflows that run outside the X platform, with your own model keys and data store. Grok Bot remains easier to start with if you are already on X Premium and have no need for infrastructure control or model flexibility.

Rakazo vs Lindy AI

Lindy AI is a commercial AI agent platform with a managed cloud and per-seat pricing, supporting dozens of third-party tool integrations. Rakazo is an open-source alternative without per-seat fees, with agents running on your own hardware.

Feature	Rakazo	Lindy AI
License	Apache-2.0	Proprietary
Self-hosting	Yes	No
Pricing	Free self-hosted	Paid plans
Data residency	Your servers	Lindy servers
Integration library	Composio-based	Extensive managed

Rakazo is the stronger choice for teams with sensitive credentials, cost constraints on high-volume automation, or a requirement to keep data on-premises. Lindy AI is the better pick when you want a polished, no-infrastructure product with a larger library of pre-built integrations and no tolerance for Docker setup.

Rakazo vs Zapier Central

Zapier Central is a task-based automation service with per-task billing and a managed cloud environment. Rakazo runs bots persistently with memory and saved routines, closer to an agent model than a trigger-action model.

Feature	Rakazo	Zapier Central
License	Apache-2.0	Proprietary
Self-hosting	Yes	No
Billing model	Free self-hosted	Per task
Agent memory	Persistent across sessions	Per-run only

Rakazo suits teams that want agents with persistent context across tasks rather than one-off trigger-action automations. Zapier Central is still the better fit for simple, high-volume integrations between SaaS tools where setup speed matters more than data ownership.

install · quick start

Quick start#

bash

Self-hosting Rakazo requires Node.js 22+, pnpm 9, and Docker Desktop before running the setup steps below.
```bash
git clone https://github.com/elie222/rakazo.git
cd rakazo
cp .env.example .env
docker compose --env-file .env -f infra/compose/docker-compose.yml up postgres -d
pnpm install
pnpm db:generate
pnpm db:migrate
pnpm sandbox:build
pnpm dev
```

tech stack · detected from GitHub

What it's built on#

Languages: PythonTypeScript
Frameworks: React
Infrastructure: Docker

frequently asked

FAQ#

Is Rakazo free to use?

Yes. Rakazo is Apache-2.0 licensed and free to self-host with no pricing page and no feature gates. You pay for your own server infrastructure and whatever API costs your chosen LLM provider charges. A managed cloud option (bring your own model keys, managed sandboxes) is listed as coming soon but is not yet available.

What AI models does Rakazo support?

Rakazo supports any model you connect through your own API keys, including Claude, GPT-4, Grok, and local models via OpenRouter. Models are configured per bot, so different bots can use different providers. You can point a cheaper model at routine triage tasks and a more capable one at writing or analysis.

How difficult is it to self-host Rakazo?

Moderate. You need Node.js 22+, pnpm 9, and Docker Desktop installed before starting. The setup involves six steps: clone the repo, configure environment variables, start a Postgres instance via Docker Compose, run database migrations, build the sandbox image, and start the dev server. Detailed self-hosting documentation is available in the repo's docs folder.

Is Rakazo production-ready?

Rakazo is labeled beta in its README. It was created in August 2026 and has 16 open issues as of that date. Active development means breaking changes between releases are possible. The project recommends evaluating it for non-critical or internal workflows before committing it to production-critical pipelines.

How does Rakazo compare to Zapier or Make for automation?

Zapier and Make are managed cloud services with per-task billing that store your workflow logic and credentials on their servers. Rakazo is self-hosted, Apache-2.0 licensed, and keeps everything on your own infrastructure. The key difference is model: Rakazo bots are persistent agents with memory that span multiple sessions, whereas Zapier and Make run discrete trigger-action automations per event. Zapier and Make require no server management; Rakazo requires running your own Docker environment.

Looking for more

Other ways to replace Grok Bot, Lindy AI, Zapier Central, Make, Simular Pro and Muse#

Buzz

Featuredfor Grok Bot

Self-hosted team chat where people and AI agents work together

36,174Visit

OpenMausBot

#2 in the Grok Bot guide

Local-first agent team on your existing CLI subscriptions

5,280

OpenBot

#3 in the Grok Bot guide

Per-agent isolation with a policy-gated audit trail

6,875

openhuman

#4 in the Grok Bot guide

Memory, reach, and workflow orchestration

42,188

All 11 Grok Bot alternatives 8 open source Grok Bot alternatives, ranked

by category

Open source tools in these categories#

404

Run rakazo on your own server

Self-host rakazo on a Hostinger VPS.

Deploy on Hostinger

Featured

Inbox Zero

Alternative toSuperhuman

AI email assistant that drafts replies and clears your inbox

12,712 GitHub stars
Licence AGPL-3.0
#Email

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

4,904 GitHub stars
Licence Apache-2.0
#AI Agents

Omnara

Alternative toClaude Managed Agents

Open-source agent deployment API. Self-host or use Omnara Cloud.

2,957 GitHub stars
Licence Apache-2.0
#AI Agents

Feature your project

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

Rakazo vs Grok Bot

Feature	Rakazo	Grok Bot
License	Apache-2.0	Proprietary
Self-hosting	Yes	No
Model choice	Any (Claude, GPT, Grok, local)	Grok only
Credential storage	Your infrastructure	xAI servers
Pricing	Free self-hosted	Subscription

Rakazo vs Lindy AI

Feature	Rakazo	Lindy AI
License	Apache-2.0	Proprietary
Self-hosting	Yes	No
Pricing	Free self-hosted	Paid plans
Data residency	Your servers	Lindy servers
Integration library	Composio-based	Extensive managed

Rakazo vs Zapier Central

Feature	Rakazo	Zapier Central
License	Apache-2.0	Proprietary
Self-hosting	Yes	No
Billing model	Free self-hosted	Per task
Agent memory	Persistent across sessions	Per-run only

Who rakazo is for#

Developers automating repetitive operational workflows

Skip if:

Small teams replacing per-task automation billing

Skip if:

Security-conscious teams that cannot route credentials offsite

Skip if:

The problem it solves#

How it solves it#

Sandboxed browser and shell per bot

Persistent memory and saved routines

Bring-your-own model support

Approval gates and audit log

Bot templates for eight common roles

Strengths and trade-offs#

Strengths

Trade-offs

rakazo vs alternatives#

Rakazo vs Grok Bot

Rakazo vs Lindy AI

Rakazo vs Zapier Central

Quick start#

What it's built on#

FAQ#

Other ways to replace Grok Bot, Lindy AI, Zapier Central, Make, Simular Pro and Muse#

Open source tools in these categories#

AI & Machine Learning

Product & Project Management

Business & Productivity

Developer Tools

Find open source alternatives to paid software

Who rakazo is for#

Developers automating repetitive operational workflows

Skip if:

Small teams replacing per-task automation billing

Skip if:

Security-conscious teams that cannot route credentials offsite

Skip if:

The problem it solves#

How it solves it#

Sandboxed browser and shell per bot

Persistent memory and saved routines

Bring-your-own model support

Approval gates and audit log

Bot templates for eight common roles

Strengths and trade-offs#

Strengths

Trade-offs

rakazo vs alternatives#

Rakazo vs Grok Bot

Rakazo vs Lindy AI

Rakazo vs Zapier Central

Quick start#

What it's built on#

FAQ#

Other ways to replace Grok Bot, Lindy AI, Zapier Central, Make, Simular Pro and Muse#

Open source tools in these categories#

AI & Machine Learning

Product & Project Management

Business & Productivity

Developer Tools

Find open source alternatives to paid software