Orimora is a knowledge base that lives. A Markdown editor with block focus, built-in AI (BYOK), MCP for your LLMs, an Obsidian plugin, and gamification that turns upkeep into a habit. Open source from Germany.
Pre-registration for the beta opens soon.
The same app, the same Markdown files: whether it is your private thinking archive, your team knowledge base, or the context layer for assistants.
Notes, ideas, daily reviews. A focus mode for writing and reading without distraction lets you go deep. Everything is Markdown and stays yours: portable and available offline.
Most tools treat notes like dead files. Orimora thinks in networks: the library has a pulse. Teams have rituals. AI is a thinking partner, not the owner.
Notes, tasks, and references link together. Orimora surfaces connections and backlinks without forcing a rigid structure on you.
Block focus highlights the section you are working on. The library pulse shows when content was last edited or read. What matters stays visible without endless clicking through.
Open Markdown. AGPLv3-or-later, opening with the public beta. Upstream contributions via CLA. BYOK for every AI provider. Self-hosting is not an add-on; it is the foundation.
No feature hailstorm. Just the things that make daily knowledge work easier: for you alone, for your team, for your AI.
Keyboard-first, slash commands, tables, Mermaid, math, and embeds. The active block gets a subtle outline: calm without a fullscreen mode.
The Kaizen score measures how well your library is maintained. See at a glance what is current and what is going stale.
Native MCP server for Claude, Cursor, and local models: read, write, link. Also a strong fit as a Karpathy brain: your assistant keeps context across sessions. No scrapers, no detours.
Several people in the same document, with visible cursors and presence. No more “who has the latest version?” More clarity for the team, less merge stress.
OpenAI, Anthropic, or Ollama locally. Keys encrypted per workspace, never on our servers.
Streaks, badges, leaderboards. Motivation through rhythm, not pressure.
Required docs with acknowledgement. Compliance without email ping-pong.
Push from your vault, pull via snapshot or selectively. Markdown stays Markdown, local files stay local.
GDPR-compliant when self-hosted on your infrastructure (any EU/DE host you choose). AGPLv3-or-later, built in Germany. No US cloud in the path, no shadow data flows.
Orimora is not another silo. It speaks MCP, respects Markdown, runs on your hardware. Use the tools you already have.
Add-ons for daily work and onboarding: vault sync, n8n automations, and one-step importers from WordPress and Kirby. Markdown stays the source of truth.
Vault ↔ Orimora
Push and pull between your vault and the team knowledge base. Markdown stays the source of truth: offline in Obsidian, online for the team.
Download with the open betaWorkflows · webhooks
Wire Orimora into n8n flows: create documents, set tags, fire webhooks. Built for ops, onboarding, and reporting.
Download with the open betaWordPress → Orimora
Bring existing WordPress posts and pages into Orimora as Markdown documents — a clean migration path off your old CMS.
Download with the open betaKirby → Orimora
Migrate content from a Kirby site into Orimora as Markdown — pages and structure carried over, ready for the team.
Download with the open betaOpen source and self-hosted is the whole product, free under AGPLv3-or-later — every feature ships in the free edition. There are no feature gates between free and paid: a paid plan only adds customization, installation help, and support.
Votes, issues and discussions open up with the public beta. This is the short version.
Orimora is AGPLv3-or-later — the source opens with the public beta. External contributions go through a Contributor License Agreement (CLA) so we can evolve the product cleanly. Forking and self-hosting are first-class.
Missing a question? Write to us — we are happy to extend this list.
No. Orimora uses your own API keys (OpenAI, Anthropic) or local models via Ollama. We never see your keys. They stay encrypted in your workspace.
Obsidian is a local editor without real team features. Notion is a polished silo with vendor lock-in. Orimora uses open Markdown (like Obsidian), is team-ready (like Notion), and MCP-native (like almost nothing else). Plus: open source and self-hostable.
A simple signal for how actively a document is maintained: last edit, reads, references. Teams see at a glance what is alive and what is fading, and get a gentle nudge not to let docs rot.
A plugin you install in Obsidian. It syncs your vault with Orimora. Markdown stays Markdown. You work offline in Obsidian; your team sees changes online. Conflicts resolve via diff.
Orimora is an MCP server. Claude Desktop, Claude Code, and any other MCP-capable tool can access your documents directly: read, write, link. No custom integration, no scraping.
Self-hosting runs on your own infrastructure — PostgreSQL and Redis via Docker, no external SaaS. A one-click Coolify template and a bare-metal guide ship with the open beta.
AGPLv3-or-later keeps fork and self-host rights for you. The CLA applies only to contributions to the official repository: it lets us evolve the product, managed hosting, and enterprise offerings without diluting copyleft for users.
Your self-hosted Orimora keeps running. The code is AGPLv3-or-later; you can fork and operate it. Your data lives as Markdown on your infrastructure. No lock-in.
Run Orimora on your infrastructure: Docker, Coolify, or bare metal. Your first note in minutes. Open source, AGPLv3-or-later, no vendor lock-in.