The Open Standard | VaultOS
Book a free walkthrough

Open standard

Built on the format
Google just standardized

In 2026, Google published the Open Knowledge Format (OKF) — an open, vendor-neutral standard for the knowledge AI agents need. We were already building it. It is why an enterprise knowledge layer can be adopted without a platform decision sitting behind it.

If you've used Obsidian, Notion, Hugo, or any of the LLM wiki patterns that have emerged over the past year, the shape will feel familiar. OKF formalizes the small set of conventions needed to make these patterns interoperable.

Google Cloud
Introducing OKF v0.1

Why not your platform vendor's knowledge layer?

You can, and many will. The difference shows up at the end. A vendor's knowledge layer holds your knowledge in their database and reads it back through their SDK, so leaving is an export project with losses. OKF keeps it in files you already own, so leaving is a git clone. Every tool on either end is swappable — us included. What we sell is the working system: discovery, import, encrypted sync, the grounded assistant, and a clean handover.

Knowledge as code

OKF treats organizational knowledge the way engineering teams treat source code — git-native, auditable, diffable.

Git-native

Plain markdown + YAML front-matter in a git repository — the canonical shape for knowledge AI agents can read. Your entire vault exports with a single git clone.

Auditable

The vault's manifest registers into BigQuery and Knowledge Catalog for governance and discovery — every note becomes a catalogued, queryable asset.

Diffable

Every change to your knowledge lands as a plain-text diff — reviewable and revertible, like code.

Go deeper

Read our OKF essay on the Emerge hub.

Read the essay

Give your AI a memory.

A free 30-minute walkthrough of a live VaultOS — the graph, the sync, the agent that knows three years of decisions.

Book a free walkthrough
See pricing