What is this website?
Rakazo is a self-hostable, open-source AI teammate platform for people and teams who want standing bots to take repeatable work while keeping models and data under their own control. It is not a one-off chat window. Bots run by job—inbox triage, sales follow-up drafts, expense matching, recruiting shortlists, coding changes, and similar roles. Users can check progress from web, desktop, or mobile, and can message bots from Slack, Teams, and related channels. Compared with hosted-only assistants, it emphasizes your own keys, your choice of model, and control on a local machine or self-managed server.
Key Features
- Create long-running bots from job templates, each with its own tasks and approval boundaries.
- Connect Gmail, GitHub, Notion, and MCP servers so bots can read and act inside real apps.
- Watch steps on a bot computer and save repeatable flows as reusable skills.
- Wake bots on schedules, webhooks, GitHub events, and other watched changes.
- Self-host with your APIs or local OpenAI-compatible servers, or use hosted plans that include computer hours.
- Use web, desktop (macOS/Windows/Linux), and iOS/Android clients to review and approve work.
Common Use Cases
- Founders or operators clear a weekend inbox with an Inbox Manager bot that archives noise, drafts replies, and flags contract questions for human review.
- Sales teams mention an outbound bot in Slack to research quiet leads and draft follow-ups before a person decides what to send.
- Technical leads point self-hosted Rakazo at private on-prem models so coding agents can change code and reproduce issues without sending sensitive repos off-network.
- Individuals schedule bots to scan marketplaces and pricing pages, then push only matching candidates to a phone.
- Small teams use a Chief of Staff-style bot to roll up multi-bot progress into a briefing before standup.
Who is it for?
- Individual developers and small teams that want multi-role AI teammates and will configure models and integrations.
- Companies and studios that need data residency, self-hosting, or local models.
- Collaborative users already in Slack/Teams who want to dispatch bots by mention.
- Not a fit for users who only want a zero-setup hosted chat and refuse key or self-host configuration.
- Also a poor fit when the expectation is one unrestricted assistant that decides everything without approvals.
How does it compare to similar tools?
Use these checks to decide whether Rakazo fits better than a generic chat assistant or a heavier multi-agent framework:
- Do you need multiple standing job bots, not a single Q&A session?
- Must you self-host, bring your own keys, or attach local inference?
- Do bots need to act inside email, repos, Slack, and similar tools—not only generate text?
- Are you willing to maintain a runtime? If you want zero ops, a hosted chat product may be simpler.
- If you care more about complex visual orchestration than job templates, compare agent-orchestration tools separately.
What Our Customers Say
- People moving from other Grok Bot-style products often note clearer multi-bot job split and smoother mobile check-ins.
- Self-hosting tech leads focus on private models and local GPUs: once bots point at internal inference, sensitive work can stay in-house.
- Productivity-minded users apply it to verifiable chores such as inbox zero and follow-up drafts, not one long chat.
- Others warn that first-time client, model, and integration setup still has a learning curve; tap-and-chat expectations can feel heavy.
FAQ
Q: Is Rakazo free?
A: The self-hosted open-source edition can be used without a paid product license. Hosted plans offer trials, include bot computer hours by tier, and can add usage credits.
Q: Can I use Claude or ChatGPT subscriptions, or local models?
A: Yes. Docs describe eligible subscription/API connections, and bots can point at local OpenAI-compatible servers such as Ollama or LM Studio, with different models per bot.
Q: Does my computer need to stay on?
A: For self-hosting it depends on how you deploy. Hosted plans provide cloud bot computers billed by plan hours. Sensitive actions can still require human approval.





















