Short answers.

What is Lorah?

Lorah is a secure, local-first AI workspace. You run a team of persistent AI specialists (“teammates”) that share project memory — you approve what becomes shared truth. Your workspace, your keys, your machine. Multi-model: OpenAI, Anthropic, Gemini, Perplexity. macOS and Windows.

Learn more →

Who is Lorah for?

Founders, consultants, operators, researchers, and AI power users who already use multiple AI tools and lose time re-explaining project context. If you flip between ChatGPT, Claude, Gemini, and Perplexity for the same project, Lorah is the workspace around them that keeps the context.

How is Lorah different from ChatGPT Projects or Claude Projects?

Four things:

Local-first. Your workspace lives on your machine, not in their cloud.

Multi-provider in one workspace. Lorah spans OpenAI, Anthropic, Gemini, and Perplexity — you don’t pick a platform-lock.

BYOK with zero markup. You bring your own API keys and pay the provider directly.

Reviewed memory with provenance. You decide what becomes durable memory. Every memory entry traces back to the conversation that produced it. ChatGPT and Claude Projects capture memory automatically and silently.

Can I use Lorah with Claude, ChatGPT, Gemini, and Perplexity at the same time?

Yes. One workspace, four providers. Each teammate is bound to one provider at a time, but a single workspace can have teammates on different providers running side by side. Council and Meeting let them work on the same question from different models.

What does “local-first” mean?

Your workspace data — teammates, memory, conversations, library — lives on your machine. Lorah’s servers do not host any of it. There is no “Lorah cloud” mirroring your data across devices, because we don’t have one. Network is only used for model calls (direct to providers) and license / update checks.

Full trust story →

Does Lorah store my workspace data?

Lorah’s servers don’t store it. Your workspace lives on disk where you installed Lorah. The only things our servers see are licensing (email, Stripe customer ID, plan type, status, date) and software update checks. No telemetry. No logging of prompts or completions. No crash analytics that ship your data anywhere.

Full trust story →

How does Lorah use my API keys?

You bring your own keys (BYOK). They’re stored locally, encrypted via your operating system’s keychain (AES-256-GCM). When a teammate makes a model call, the request goes from your machine directly to the provider. Lorah’s servers are not involved, and Lorah adds zero markup on inference — you pay the provider at their published rate.

What’s a “teammate”?

A persistent AI specialist with a role, prompt context, and accumulated memory. Long-lived, not session-based. You give it a name, a personality, a mandate. It builds memory across every conversation. Common starter teammates: Strategist, Builder, Researcher, Critic, Writer.

What is Council?

A session where multiple teammates answer the same question from different perspectives, side by side. Then, in round two, each teammate sees the others’ answers and offers a synthesis. Useful when you want a Strategist’s take, a Builder’s take, and a Critic’s take on the same decision — without bouncing between four chat tabs.

How does Lorah memory work?

Memory in Lorah is reviewed, not automatic. Teammates propose memory entries during conversation. Proposed entries land in the Review Queue. You approve, edit, or reject each one. Approved entries become durable memory with provenance (a link back to the conversation that produced it). You can supersede entries when facts change, or reject them entirely.

This is different from automatic chat-history memory in other tools, where everything is remembered silently and nothing is traceable.

Is Lorah an autonomous agent platform?

No. Lorah is workdesk-style, not agent-style. Important outputs — memory, sync briefs, MCP write-backs, task results — pass through human approval in the Review Queue. Lorah is designed for serious work that benefits from oversight, not for unattended long-running action.

Can Lorah connect to Claude Desktop, Cursor, or Claude Code?

Yes. Lorah supports MCP. Lorah can act as an MCP server so compatible tools can read approved workspace context, and Lorah can connect to external MCP tools through teammates.

Write-back goes through the Review Queue before it becomes durable memory.

MCP setup guide →