Governed knowledge for AI

Grow what your AI knows.

OKForest turns your organization's knowledge into an asset AI can use and people can trust. It lives as Open Knowledge Format files in your own Git repositories, reaches your AI assistants over MCP, and changes only with an owner's approval.

The open-source CLI and GitHub Action are available today. The hosted service is in early access.

Your AI doesn't know your organization

AI assistants start from zero

Every new model, vendor, or session has to learn your organization again, from whatever someone pastes in.

Knowledge is buried in prose

Wikis and shared drives hold long documents written for people, with no consistent metadata, relationships, or owners.

One central knowledge base doesn't scale

The teams closest to each subject have to own it, while the standards stay shared.

How it works

  1. Step 1

    Keep knowledge in Git

    Write concepts as Open Knowledge Format files in your own repositories, with owners, sources, and trust signals in each file's frontmatter.

  2. Step 2

    Connect OKForest

    Install the OKForest GitHub App on the trees you choose. It reads them, and never pushes to your default branch.

  3. Step 3

    Ask, browse, and verify

    Claude, ChatGPT, and other assistants answer from your trees over MCP, and say when an answer rests on a draft or unverified concept. People read the same source in the browser.

  4. Step 4

    Propose, never publish

    Changes from people and AI assistants become pull requests that the tree's Owner or a Steward approves.

Built on a few firm principles

You own the content

Your knowledge stays in your Git repositories, with its full history. Cancel OKForest and nothing is lost.

Deterministic by default

Indexing, permissions, and validation involve no model calls. Anything an AI infers is labeled as a suggestion.

No Git skills required

Contributors and Stewards work through their AI assistant or the browser. Git is the storage, not the interface.

Diagrams as code

Diagrams are D2 or Mermaid source, so they can be diffed, reviewed, and edited like everything else.

From one tree to a canopy

Start with one tree and grow. Every edition is the same service; public or private is a setting at every level.

Tree

One OKF repository, served over MCP and in the browser: read, search, validate, and propose changes.

For: A team, or a small company getting started

Plan: Free hosted plan

Grove

Many trees combined into one company knowledge base, with shared standards, access control, and Steward approval.

For: A company

Plan: Subscription

Canopy

Many groves, plus shared and public trees from partners, vendors, and regulators, and llms.txt sites.

For: Groups of companies, or anyone mixing internal and external knowledge

Plan: Subscription

Self-hosted

Grove or Canopy, running in your own cloud environment.

For: Regulated enterprises

Plan: Annual license

Open source, available today

The format is open, and so are the tools that check it. The same rules run in the CLI, in CI, and inside OKForest, so a tree gets the same results everywhere.

OKForest CLI

Validate a tree, list its metadata, or start a new one.

npx okforest validate .
CLI documentation

OKForest Validate

Check every pull request, with each finding annotated on its line.

- uses: okforest/validate-action@v1
Action documentation

Bring your knowledge to your AI

OKForest's hosted service is in early access. Tell us about your team and the knowledge you'd like your AI assistants to use.

Get early access