OPEN KNOWLEDGE, MADE PRACTICAL.
The IDE for knowledge repositories.
{{ heroSub }}
Markdown-native · Git-backed · OKF-ready · Local-first
Built around Open Knowledge Format (OKF), introduced by Google Cloud.
The format is already here.
Google Cloud introduced Open Knowledge Format to make knowledge portable, interoperable and usable by both humans and agents.
At its core, the idea is remarkably simple: structured Markdown, metadata, links and directories — open files that can live in Git.
THE PRIMITIVES
Markdown
Metadata
Directories
Links
Git
Open knowledge repository
OKF gives knowledge a format.
Okide gives you the IDE.
The pieces already worked.
Using them together didn't.
Markdown
Knowledge stays readable with or without Okide. Open it in any text editor. Render it on GitHub. Give it to an agent.
# Positioning Okide is the IDE for knowledge repositories. - [Strategy](strategy.md)
Git
Every meaningful change has history. Compare it, review it, revert it and understand how your knowledge evolved.
OKF
A shared structure for knowledge that humans and agents can understand without inventing a new format for every tool.
--- type: "Concept" title: "Positioning" tags: [product] ---
Okide
The interface that brings all of it together so you can focus on the knowledge instead of the plumbing.
One knowledge repository.
For humans and agents.
Your team maintains it. Your agents work from it. No copies, no separate knowledge layer — just the same versioned source of truth.
What belongs in a knowledge repository?
If knowledge matters enough to keep, share or give to an agent, it can live in a repository.
PERSONAL
Knowledge that belongs to you, not to an app.
Personal knowledge
Keep durable knowledge outside any single AI or note-taking app. What you actually believe, in files you keep.
knowledge/index.md
Research
Organize sources, concepts, findings and evolving conclusions. Sources stay linked to the conclusions they support.
research/sources/
Professional knowledge
Build a repository around everything you learn in your field. Ten years of judgment, written down instead of remembered.
craft/patterns.md
Consulting
Maintain structured knowledge for clients, industries and engagements. Each client gets a folder; the method stays yours.
clients/acme/index.md
Learning
Turn notes and materials into connected, reusable knowledge. Course notes become concepts you can revisit and correct.
learning/notes.md
Writing
Keep research, references, ideas and drafts in one versioned repository. Drafts and their research live in the same history.
writing/drafts/
YOUR ROLE
The context that makes you good at the job.
Engineering knowledge
Architecture, decisions, systems, patterns and technical context. Why the system looks like this, not only how it runs.
engineering/architecture.md
Product knowledge
Customer problems, decisions, research, specifications and strategy. The reasoning behind the roadmap, not just the roadmap.
product/decisions/
Design knowledge
Principles, patterns, research and design decisions that survive individual files. Decisions that outlive the file they were made in.
design/principles.md
Sales knowledge
Accounts, market context, objections, playbooks and customer insight. What worked, what lost, and what the market keeps saying.
accounts/objections.md
Operations knowledge
Processes, decisions, dependencies and operating context. How the work actually runs when nobody is watching.
operations/processes/
Domain expertise
Capture the knowledge that makes an expert actually expert. The part that usually leaves when the person does.
domain/index.md
TEAMS
What a group needs to stop re-explaining.
Team handbook
A living repository for how your team works. Rituals, ownership and defaults, in one reviewable place.
team/handbook.md
Decision repository
Preserve what was decided, why it was decided and what changed later. Each decision keeps its date, its context and its reversal.
decisions/2026/
Project knowledge
Give every contributor and agent the same project context. New joiners and agents start from the same brief.
projects/atlas/index.md
Runbooks
Operational knowledge that stays readable, searchable and versioned. The steps someone follows at 3am, kept current.
runbooks/incident.md
Onboarding
Give new people and agents the context they need to become useful. Week one reads a repository instead of asking around.
onboarding/week-one.md
Shared research
Build institutional knowledge instead of losing research inside conversations. Findings survive the thread they were discovered in.
research/shared/
COMPANIES
The knowledge the organization depends on.
Company knowledge
Policies, context, principles, operations and institutional memory. How the company decides, not only what it announced.
company/principles.md
Product portfolio
Keep knowledge across products structured without forcing everything into one document. Each product owns a folder; the company owns the index.
products/index.md
Customer knowledge
Maintain reusable customer and market context. Segments, objections and context every team reuses.
customers/segments.md
Internal documentation
Documentation that lives as portable files instead of inside another silo. Readable in the editor, on GitHub, or by an agent.
docs/internal/
Policies & procedures
Keep important operational knowledge reviewable and versioned. Every revision is a commit someone can review.
policies/security.md
AI-ready company context
Create a stable knowledge layer that different agents can consume. One maintained layer instead of a prompt per team.
context/index.md
AGENTS
The same repository, read by your tools.
Coding agents
Give coding agents architecture, conventions and product context beyond the codebase. Conventions and intent the code alone never states.
engineering/conventions.md
Research agents
Give research agents a persistent place to read and contribute knowledge. Findings land as files, not as a chat transcript.
research/agent-log.md
Internal assistants
Ground assistants in maintained company knowledge instead of scattered prompts. Answers trace back to a document you can fix.
company/faq.md
Agent handoffs
Let different agents work from the same durable context. The next agent reads what the last one wrote.
context/handoff.md
Multi-agent systems
Share knowledge without rebuilding memory independently for every agent. One repository, many readers, no duplicated memory.
knowledge/index.md
Agent-generated knowledge
Let agents contribute useful knowledge without hiding it inside proprietary memory. Review it, edit it, or revert it like any change.
log.md
Questions.
Short answers. The documentation goes deeper.
Is Okide really free?
Yes. The Okide desktop IDE is free.
Do I need to know Git?
No. Okide versions your repository for you. If you already know Git, everything is where you expect it.
Does Okide replace Markdown, Git or GitHub?
No. It is the product layer on top of them. Your repository stays a normal Git repository of Markdown files.
What is Open Knowledge Format?
An open specification introduced by Google Cloud for knowledge that both humans and agents can use: structured Markdown, metadata, links and directories.
Is Okide a Google product?
No. Okide is an independent product. Open Knowledge Format is an open specification published by Google Cloud, and Okide is built around it.
Where does my knowledge live?
On your computer, as files. Connecting GitHub is optional and up to you.
How do AI agents use the repository?
They read the same open files. Compatible agents can connect through MCP and work from the repository you maintain.
What happens if I stop using Okide?
Nothing happens to your knowledge. It is Markdown in a Git repository, readable by any editor.
Start with a repository.
{{ finalCtaSub }}
{{ finalCtaHint }}
Open knowledge deserves a great IDE.
Private beta
Get early access to Okide
Okide is in private beta. Leave your email and we’ll send the download link when your invite is ready.
macOS and Windows first. Linux is planned. No account required to install when your invite arrives.
Download Okide
The free desktop IDE for knowledge repositories. Local-first, Git-backed, built around Open Knowledge Format.
Okide for macOS
- Universal build
- Apple Silicon · Intel
- Version {{ version }}
- Released {{ releaseDate }}
Okide for Windows
- Windows x64
- Windows 10 · Windows 11
- Version {{ version }}
- Released {{ releaseDate }}
Okide for Linux
PlannedA Linux build is planned. Until then, the repository format is fully portable — the files work anywhere.
Signed builds. No account required to install.
Private beta
{{ thanksH }}
{{ thanksSub }}
{{ version }} · {{ dlPlatformLabel }}
{{ thanksH }}
Install Okide, then create your first knowledge repository. It starts as a folder of Markdown files on your computer.
Release notes by email
Occasional notes about new Okide releases and Open Knowledge Format. Nothing else.