The first knowledge platform for product, engineering, and design

Every agent. Shared context.
Nothing lost.

Your AI agents share a living knowledge base — automatically built from the tools you already use, always current, never stale.

Join the Waitlist

Your agents are context-starved

Your PM's agent doesn't know what engineering decided yesterday. Your engineer's agent has never seen the design rationale. Every role, the same gap.

Decisions live in Slack threads, PR descriptions, and individual conversations. Then they vanish. Wikis go stale within weeks. There's no source of truth that both your team and its agents can rely on.

PM Builds PRD with agent
90%
Design Interprets spec
55%
Engineering Builds from spec
25%
Marketing Writes launch copy
12%
New hire Onboards
3%

Context degrades at every handoff. Every team feels it independently.

PMs spend 50–100 minutes a day re-explaining decisions to AI agents. That's 10–20% of productive capacity — invisible, because nobody tracks it.

"I run a team of 20 engineers across 4 subprojects. Every one of us uses AI agents daily. We tried a shared GitHub repo for team knowledge — it validated the concept but couldn't scale. Grimoire is what that repo was trying to be."

Stop re-explaining your product to ChatGPT

Same models you already use — but they know your product, your codebase, your decisions, and your constraints.

Grimoire Chat — Billing Portal SSO
Context used
Decision Auth migration to OAuth 2.0
Architecture Billing service v3 API
Requirement SSO for enterprise tier
3 knowledge entries referenced
Write the technical approach for adding SSO to the billing portal.
Based on the auth migration decision and the billing v3 API architecture, here's the approach: → SSO leverages the existing OAuth 2.0 identity provider → Billing portal authenticates through the v3 gateway → Enterprise tier flag controls SSO availability
+ Inscribe to Grimoire

Bring your own model

Connect Claude, GPT, or any model with your own API keys. Grimoire enriches every conversation with your team's knowledge automatically.

See what your agent knows

A sidebar shows exactly which knowledge entries are powering each response. No black box.

One-click inscribe

Made a decision in a conversation? Push it to the Grimoire with one click. Knowledge captured where work actually happens.

Not a wiki. A living knowledge graph.

Typed, linked, and versioned. You write pages. The Scribe auto-generates scannable entries for your team and retrieval-optimized cards for agents. One source of truth, two perfect formats.

14 knowledge types — decisions, architecture, design rationale, conventions, competitive intel, and more — with bidirectional links across teams and sources. Agents traverse the connections automatically.

Decision Migrate billing API to v3 Verified 3 days ago
depends_on
Architecture Billing service overview Verified 1 week ago
implements
Requirement Multi-currency support Verified 2 weeks ago
You write Pages Free-form, any length
Scribe generates
Your team browses Entries Focused, scannable
Scribe optimizes
Agents retrieve Cards 200–500 word chunks

Write once. The Scribe generates the rest.

Wikis rot. The Grimoire doesn't.

The Scribe crawls your connected tools, drafts entries, and flags what's gone stale. You just review.

GitHub
Google Drive
Notion
Confluence
Slack

Extracts from your tools

GitHub PRs, Google Docs, Notion pages, Confluence wikis, Slack threads. The Scribe crawls them all and drafts structured knowledge entries.

Detects staleness

When a new PR lands in an area covered by an existing entry, the Scribe flags it for review. Knowledge doesn't silently go out of date.

Flags contradictions

Two entries describe conflicting approaches? The Scribe catches it and creates a relationship so your team can resolve it.

Gets smarter over time

The Scribe learns from your edits. Approve a draft untouched? That's signal. Change the framing? That's signal too. Less review over time.

Grimoire lives in your IDE

Your coding agents know your codebase. Grimoire gives them everything else — product decisions, design rationale, architecture, and team conventions.

Claude Code MCP server
Codex MCP server
Cursor MCP server
VS Code MCP server
Any MCP-compatible tool Open protocol

Agents query, Grimoire answers

Your agent asks Grimoire through MCP. The relevance engine returns the right knowledge cards — scoped to your permissions, ranked by freshness and semantic match.

No wasted tokens

Knowledge cards are 200–500 word chunks, split on semantic boundaries. Your agent gets exactly what it needs — no pasting docs, no re-explaining.

Same knowledge, every tool

One Grimoire serves every agent across your stack. A PM using Claude Code gets the same knowledge as an engineer in Cursor.

From zero to fully operational in 30 minutes

I

Connect your tools

GitHub, Google Drive, Notion, Confluence, Slack. OAuth in, pick what matters.

II

The Scribe synthesizes

Grimoire ingests your existing content, structures it into knowledge entries, and cross-links across sources. No blank page.

III

Every agent levels up

Every agent on your team shares one knowledge base from the first query.

Your knowledge stays yours

We treat your organizational knowledge as what it is: sensitive intellectual property.

Workspace isolation

Database-level tenant isolation. No cross-workspace data access, ever.

Encryption at rest & in transit

TLS everywhere. Database and embeddings encrypted at rest.

Bring your own keys

BYOK model routing. Your content is never sent to models for Grimoire's purposes.

Audit logging

Full trail of access, modifications, and agent queries.

Granular permissions

Scoped to workspace, division, team, and project. Agents respect every boundary.

SOC 2 controls from day one

Type II certification on track for Q3 2026.

SSO / SAML

Enterprise SSO with SAML 2.0 support. Integrate with your identity provider from day one.

Join the waitlist

Built by a PM who got tired of re-explaining everything to every agent.

Free for small teams. Pro starts at $20/user/month.

Enterprise team? Let's talk.