// the take
Rakazo is a self-hosted, open-source agent platform (Apache 2.0) for running persistent "bots" with memory, tools, and sandboxed code execution, shipped as a web app plus Electron desktop and Expo mobile clients. It's for developers who want a Grok Bot/Muse-style assistant they control end to end, with bring-your-own model and a choice of compute sandboxes.
Pluggable sandbox layer (local Docker, E2B, Daytona, CreateOS, Boat, Railway) lets you run bots free on a laptop and move to a managed provider later without touching application code. Real security separation in Postgres: the app connects as a dedicated rakazo_app role under row-level security while migrations run as the owner, not a shared superuser connection. Ships genuine native clients (Electron + Expo) against the same oRPC API rather than a web view wrapper, including device-side screen proxying for live sandbox desktops. CI is taken seriously — separate lint/typecheck/unit/integration/e2e tiers plus nightly verification and a dedicated "computer replay" workflow for the sandbox runtime.
The project self-describes as beta, yet the feature surface (billing, team chat bridging, routines, messaging webhooks, referrals) is large for that maturity level, which is a lot of state to keep correct at once. Self-hosting from source isn't actually simple despite the one-command installer: it needs five independent secrets (BETTER_AUTH_SECRET, ENCRYPTION_KEY, SCREEN_PROXY_SECRET, SANDBOX_SUPERVISOR_TOKEN, two Postgres passwords) plus correct RLS role wiring, so a misconfigured deployment fails in ways that are hard to debug from outside. Any sandbox provider besides local Docker is a metered third-party dependency, so running agents that execute code at real scale means ongoing per-use cost beyond the self-hosting itself. Railway sandboxes default to PRIVATE networking that can reach other services in the same Railway project/environment — the docs recommend a separate project specifically because isolation isn't the default, a real footgun for anyone who puts the app and its sandboxes together.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →