FAQ
Questions.
Every answer here describes a plan. Living Brain is in design and not built yet.
Product
What does "living" mean?
Most wikis start going stale the day they're written. Living Brain revisits its own pages on a schedule: it merges duplicates, flags contradictions, retires facts that are no longer true and rewrites summaries. It also learns how each person works, so its answers improve every week.
How is it different from Slack AI or Glean?
Search tools find what already exists. Living Brain writes and maintains a wiki you own as Markdown, cites the message behind every fact, acts in your tools, gives your coding harnesses the same memory, and is priced per workspace instead of per seat.
Which chat apps does it work with?
Slack and Discord, as equals. Both are planned. WhatsApp and Telegram come later. You don't need a chat app at all: coding harnesses such as Claude Code, Codex, Cursor, OpenCode or Claude Desktop connect over MCP, and the livingbrain command-line tool, a single Rust binary, and the app work on their own. All of it is planned, like the rest of the product.
Is there an app?
Planned. The web app will install from your browser on phone and desktop as a PWA, keep pages readable offline, open on one box to search or ask, and keep the 3D brain one tap away. Like the rest of Living Brain, it is not built yet.
Can we put our own brand on it, or build on it?
Planned. On Teams and Crew, the app runs on your own domain with your name, logo and colours, and installs on phones and desktops as your app. A small "powered by" link is optional. There's also an open API with webhooks and SDKs for TypeScript, Python and Rust, so you can build the brain into your own tools. If you self-host, the code is yours to rebrand.
Coding harnesses
Which coding harnesses can I connect?
Any harness that supports MCP. Planned first: Claude Code, Codex, Hermes, Cursor, OpenCode and Claude Desktop. Then Gemini CLI, GitHub Copilot, Goose, Cline, Aider, Kimi CLI and Qwen Code. We're not affiliated with these tools; they connect through the open protocol.
Do you store my agent prompts and code?
Only if you opt in. Prompts and session notes are stored with secrets redacted first. Source code is never stored unless you allow it.
Can it collect my coding harnesses' logs?
Planned. The livingbrain CLI collects the session logs that Claude Code, Codex, Cursor, OpenCode and Colonizer already write, redacts secrets on your machine, and uploads them only if you opt in. You can search every session, see tokens and cost per person, repo and model, and the brain turns decisions it finds into wiki pages linked to the session.
Integrations
Can it connect my Gmail or Outlook?
Planned. The simplest and safest way needs no mailbox access at all: forward, BCC or auto-forward mail to your brain's own address on Owlpost, our sister email service, and only what you send arrives. If you want a whole mailbox kept in sync, you can also connect Gmail, Outlook.com or Microsoft 365, or any IMAP mailbox, plus your calendar, read-only. Your mail stays in your personal memory, encrypted with your own key, and no one else can draw on it unless you share a specific label or folder. Every message is screened for spoofing and prompt injection before the brain reads it, and mail can never trigger actions. Revoke the connection at any time and its stored mail is erased. When you self-host, you use your own Google or Microsoft app, so mail never touches our servers.
Can I import my ChatGPT history?
Planned. Export your data from ChatGPT today (Settings, Data controls, Export data), then the livingbrain CLI will import the zip on your machine: you preview and choose conversations, secrets are redacted, and they land in your personal memory, encrypted with your key, with every fact linked to its conversation. Claude exports will import the same way. Read the step-by-step guide.
Does it work with Grafana and our logs?
Planned. Connect Grafana with a read-only token and the brain can answer "is prod down?" with the current numbers and a link to the exact panel. It reads your logs too, from Loki, Elasticsearch, Datadog, CloudWatch, Cloudflare or Sentry, and says what changed: when the errors started, which deploy came before, and the most common messages, with secrets redacted. Alerts become incident pages linked to the deploy and pull request that caused them, and the nightly pass drafts the postmortem for a person to confirm. In the other direction, Living Brain exports its own metrics, traces and logs over OpenTelemetry, so you can watch it in Grafana, Datadog or Honeycomb.
Can it answer my customers?
Planned, through SupportGenius, a sister Factory Zero venture for customer support. It answers customers only from pages your team has explicitly published to customers, with citations, and never from internal, private-channel or personal memory. When it can't answer, it asks the brain who owns the topic and routes the question to that person. Customer messages are screened for hidden instructions before they touch the brain.
Security
Is my data encrypted?
Planned. Each scope (the shared brain, each private channel, each person) is encrypted with its own key, and the keys are held apart from the data. Search runs only inside the scopes you can see, so it stays fast. Deleting a scope's key erases that memory everywhere, backups included. On Teams you can bring your own key. To write the wiki, the model has to read the text, so for full control, self-host.
Is my data used for training?
No. Your workspace's messages and pages are never used to train models, ours or anyone else's. If you bring your own LLM, requests go to your provider under your account's terms.
Can someone hide instructions in a message to trick my agents?
Planned. Every source is screened for hidden text by PromptDecode, a sister Factory Zero venture: invisible Unicode tag characters, bidi controls and variation selectors are decoded and flagged before a page is written, and again before context is served to an agent. Anything that decodes to an instruction is held for a person to review. Mail also passes Owlpost's spoofing and prompt-injection checks.
Pricing
Can I self-host?
Yes. The Community plan is free for up to 5 people: it runs on your own Cloudflare account with your own LLM key. Larger teams need a Teams license, planned at $5 a month per workspace with unlimited people. The plan and the code as it lands are public on GitHub, open core: Apache-2.0, with the Teams features under a commercial license.
Which models?
On every plan you choose your own models, per role (triage, answers, research): Anthropic, OpenAI, OpenRouter, your LiteLLM gateway, or any OpenAI-compatible endpoint, including self-hosted ones. Crew also includes $5 of DeepSeek credit each month, so you can start without a key of your own; past that, add your own key or top up.
What does a question cost?
Planned, for hosted plans: writing the brain (reading sources and writing pages, with the nightly evolve pass included) costs $1 per million tokens, and reading it (search, pages and context for agents) is unlimited. Harder questions are priced per question by reasoning level: Minimal $0.001, Low $0.005 (the default), Medium $0.02, High $0.05, Max $0.25. Crew's $5 monthly DeepSeek credit covers about 1,000 questions at the default level. On your own LLM key you pay only your provider, with no fee from us.
How much storage is included?
Hosted Teams includes 10 GB and Crew includes 25 GB, covering wiki pages, sources, search indexes and aggregated agent logs. Extra hosted storage is $0.25 per GB a month. Self-hosted plans use your own Cloudflare storage, with no limit from us. Planned pricing.