We built this because every team we knew had a wiki that nobody opened.

OakWiki is a real-time document workspace built by two people in Helsinki. We started in 2024 because we’d both spent years inside wiki tools we’d come to resent — and watched our teams quietly stop trusting them.

The wiki that nobody opens.

Aino had been an engineer at Notion. Mikko had been at Slite, then at Klarna where he’d run the internal Confluence migration. We met at a Helsinki meetup about writing tools in spring 2024, which is a sentence neither of us thought we’d say.

The pattern we’d both seen was the same. Every team starts with a wiki. The wiki grows. Pages duplicate. Permissions get accidentally restrictive. Someone’s out-of-date doc gets quoted in a roadmap meeting. The team starts distrusting the wiki. They start asking each other in Slack instead. The wiki becomes a graveyard. Someone proposes migrating to a new wiki. The cycle repeats.

The reasons aren’t mysterious. Pages get stale because editing them feels heavy. Permissions get tangled because the model is complicated. People don’t find what they need because the tree is messy and search isn’t great. Every wiki we’d worked on had failed at one of these three.

"A wiki your team will actually open is a wiki you’d open yourself."

What it turned into.

OakWiki keeps a small surface: pages, links between pages, real-time presence, granular permissions that inherit down the tree. That’s the product. We don’t do AI sidebars, page suggestions, or auto-summaries. We don’t do a marketplace, a no-code automation layer, or 47 block types.

The opinionated bit is the writing experience. Markdown-style shortcuts that actually work, a slash menu for the rare cases when you want a specific block, code blocks with proper syntax highlighting, serif body text because text is for reading. Editing should feel like writing in a notebook, not assembling a slide.

How we run the company.

We’re two people. We’re bootstrapped. We’ve been customer-funded since month four. Our growth target is “cover salaries, reinvest the rest, hire when the support inbox starts feeling heavy.”

There’s no growth team. There’s no sales team. We answer email ourselves. The roadmap is public. Pricing won’t silently increase. We’ll keep the API stable. We’ll deprecate before we remove.