WrenLore v0.1.11 is available Read the release →

Your team’s knowledge.
Ready for people and agents.

WrenLore is an open-source, self-hosted knowledge base with collaborative editing, grounded AI and governed access for MCP clients.

AGPL-3.0Docker deploymentNo mandatory cloud
Operations / Incident response
RUNBOOKS
Database failover

Use this procedure when the primary PostgreSQL node is unavailable or replication lag exceeds the agreed threshold.

Before you start
✓Confirm the incident owner
✓Check replica health and lag
Record the failover decision
Ask WrenLore

Which services depend on the primary database?

The customer API, job scheduler and audit service use the primary cluster. 3 sources
Answers respect your space permissions.
Built for knowledge that cannot live in a random SaaS accountSAML SSOPage permissionsAudit historyMCP tokensPostgreSQL

A wiki people will use. Controls operators can explain.

Write and organise knowledge in a familiar workspace. Keep identity, storage, AI providers and agent access under the same operational model.

01

Collaborative knowledge

Real-time editing, team spaces, diagrams, comments and page history for runbooks, decisions, policies and project context.

Architecture decision 014Move event delivery to an outbox pattern
LSMKEdited 12 minutes ago
02

Grounded answers

Ask questions across the pages you can access. Answers stay linked to the source instead of becoming detached chatbot folklore.

How AI works in WrenLore →
03

Governed MCP access

Give approved agents scoped credentials and readable user-via-agent attribution. Revoke access without untangling a shared API key.

Read about MCP access →
04

Private deployment

Run the application, PostgreSQL and storage on your infrastructure. Connect the identity and AI services that fit your environment.

Deployment options →

One permission model.
Human or machine.

Agents do not need a hidden back door into company knowledge. WrenLore uses scoped credentials, existing page access and an audit trail people can read.

Read the MCP documentation →
Leo StehlikEngineering space · editor
scoped MCP token
Claude CodeActing as Leo · 3 actions logged
Updated “Database failover”User, via agent

Leave the SaaS wiki behind.

Start with the route that matches the system your team is replacing.

Knowledge infrastructure you can inspect.

Source, releases, deployment notes and security work are public.