Live demo: a one-person "AI company"

Nothing on this page is a mockup. Every screenshot comes from our own rakazo test instance (running on a Hetzner server, captured in October 2026), using the demo persona "Alex". We set up four bots for this solo founder, each with its own job:

Chief · Chief of staff

Remembers, coordinates, plans. Code words, files and to-dos live in its memory — and survive version upgrades.

Scout · Research analyst

Watches the field and competitors, produces structured briefs and comparison tables with sources.

Ink · Content writer

Turns research briefs into blog posts — and can even code a cover image for the article.

Care · Customer support

Drafts support replies: apologize, state the plan, offer a concrete next step.

Setup is one paragraph per bot

Creating a bot means writing one persona instruction; its tone, format and way of working follow from it. The panel on the right shows Scout's full instruction text:

Scout's persona instruction panel next to its comparison table answer — Scout's settings panel (right): "You are Scout, a research analyst…" — behind it, the self-hosted vs hosted comparison table it produced in that persona.

Chief: it remembers, and it has a real computer

Tell it a code word one day, ask the next — it remembers. Ask it to create a file, and the file really exists on its computer, code word included:

Chief answers the code word BANANA-42 and creates demo-notes.txt — "Your code word is BANANA-42." It then created demo-notes.txt and showed the three lines it wrote.

Not just talk — ask it to read the file back and it reports the exact size; ask about the weather and it looks up Hamburg's live forecast:

Chief reads the file back at 68 bytes and gives Hamburg's live weather — Read-back: "The file size is 68 bytes." Weather: about 10°C with a light shower possible — fetched live, not canned data.

Research: from brief to saved document

Scout's standing job is a weekly monitoring brief: the three most important developments, one line each, every one with a source link — then it saves the brief as a file:

Scout's self-hosted AI monitoring brief with sources, saved to a file — The full brief (MiniMax, Kimi, DeepSeek — each with its source), its confirmation "Done — I saved the brief as scout-brief.md", and a cost comparison table right below.

Chief does the same kind of work: asked to research the latest rakazo release, it read the GitHub release notes, wrote a short brief and saved it to its computer:

Chief saves its release research as rakazo-update.md and shows the content — "Saved as rakazo-update.md" — research becomes a file you can pick up later, not a chat that scrolls away.

Teamwork: the brief relay

Each bot has its own private computer (that is privacy isolation, not a bug), so hand-offs travel by message: send Scout's brief to Ink and it writes a ~300-word blog draft on the spot and saves it:

Ink turns Scout's brief into a blog draft saved as blog-draft.md — Ink's output: the title "Open AI's Big Week…" with the full first paragraph, saved as blog-draft.md.

Back with Chief, the draft becomes a 5-step launch checklist with an owner per step. At the bottom of the frame you can also see it delegate a question straight to Scout (the "sent to Scout" marker) — bots can hand work to each other natively, no copy-paste by you:

Chief's launch checklist and its delegation marker to Scout — The checklist (verify, check sources, edit, package, final review) is saved as launch-plan.md; the blue bubble at the bottom is the delegation, with the system marker beneath it.

Meanwhile: a cover image, written as code

Rakazo has no native AI image generation, and we won't pretend it does. But Ink can code — asked for an SVG cover (dark navy background, the title in large white type, three small orange dots), it produced exactly that:

Preview of the SVG blog cover Ink generated as code — The real preview of blog-cover.svg. This is the difference between a bot that only chats and a bot with a computer.

The honest print: ① These are real product screens; rakazo is still in beta, so UI and wording may change between versions. ② Rakazo has no native AI image or video generation — this page shows none; the cover above is an SVG drawn with code. ③ Each bot's computer is isolated by default; cross-bot hand-offs go by message or delegation, and a shared team computer can be configured instead.

Want a team like this of your own?

Deployment and persona setup is exactly what DeployButler sells: guided setup from $49, done-for-you deployment $149 one-time (first 3 launch-offer slots at $99).

See services & pricing DIY? Read the install guide