As a techie, I’ve been self-hosting my tools for a while now, mostly because I like owning my data and keeping my setup simple. The more I write, the more I’ve also realized how much I prefer markdown over heavy editors and complex file formats. It keeps my writing portable, future-proof, and easy to work with anywhere.

While experimenting with different wiki and documentation tools, I kept running into the same problem: too many features, too much setup, and not enough focus on writing. That’s when I found Otter Wiki. It’s a small, thoughtful tool that fits perfectly into how I already work, and I wish I had started using it much sooner.

What is Otter Wiki?

Installation is a breeze

Otter Wiki is a minimal, self-hosted wiki built around two ideas I already believe in: markdown and version control. At its core, it’s a personal or team wiki where every page is just a markdown file, stored in a Git repository. No database, no complex setup, no hidden formats.

What really pulled me in was how easy it was to get started. I spun it up using Docker in a few minutes. One container, a mounted folder for notes, and that’s it. The moment it was running, I just created an admin user and started writing. No configuration rabbit holes, no “setup wizard” fatigue. I used this simple docker-compose.yml file.

docker-compose.yml

services:
 otterwiki:
 image: redimp/otterwiki:2
 restart: unless-stopped
 ports:
 - 8080:80
 volumes:
 - ./app-data:/app-data

After setting up the docker-compose.yml, and placing it at my desired location, I simply ran the docker compose up -d command.

This minimal wiki tool feels honest. It doesn’t try to impress you with features upfront. It simply gives you a clean web interface to write, edit, and manage markdown notes, powered by Git from day one. That simplicity is exactly why I wish I had started using it sooner.

Clean, distraction-free writing experience

Markdown at the core

Writing in Otter Wiki feels calm and simple. The interface stays out of the way and lets me focus entirely on the text. There are no unnecessary pop-ups or catchy feature prompts fighting for attention. I open a page, start typing, and that’s it.

Everything revolves around markdown, which feels familiar. Headings, lists, code blocks, links, everything flows naturally from the keyboard. I don’t have to switch contexts most of the time. That uninterrupted flow makes a big difference when I’m documenting ideas, project notes, or long-form thoughts.

The editor behaves exactly how I expect. What I type is what gets saved. There’s no hidden formatting or editor-specific quirks to clean up later. Pages load fast, edits feel instant, and saving never breaks my rhythm. Otter Wiki reminds me why I fell in love with markdown in the first place. It respects the act of writing and gives it the space it deserves.

Version control that just makes sense

A safety net for every edit

One of my favorite parts of using Otter Wiki is how naturally version control fits into the writing flow. It uses Git in the background, but I don’t have to think about Git at all. It feels like version history made for writers, not developers.

I can choose to add a commit message or just save the document quietly. If I’m working on an important document, I add a short note in the commit message. If I’m working on a random draft, I save without overthinking it. That flexibility makes a huge difference in daily use.

Otter Wiki keeps a clear history of every change. I can open any page and see older versions, compare them with the current one, and understand what changed over time. I’ve even caught myself experimenting more freely, knowing I can always roll back if something doesn’t work. It gives me the safety of version control without the usual complexity. Simple, transparent, and very reassuring.

It is perfect for teams using a no-nonsense search feature

Simple collaboration, fast search

What surprised me about Otter Wiki is how well it works for teams without feeling heavy. User management is straightforward. I can add users, assign roles, and control who can view or edit pages. There are no complex permission trees to understand. It’s simple and practical, which is exactly what a shared wiki needs.

This makes Otter Wiki easy to use with small teams, side projects, or internal documentation. Everyone writes in the same clean markdown editor, follows the same structure, and edits stay transparent thanks to version history. There’s no confusion about who changed what.

The search feature follows the same no-nonsense approach. It’s fast, accurate, and does exactly what I expect. I type a keyword, and results show up instantly across all pages: no filters to configure, no indexing delays, no cluttered search UI.

When I’m working with others, speed and clarity matter more than advanced features. Otter Wiki gets this right. It keeps collaboration simple and makes finding information effortless.

Simple tools age better

Using Otter Wiki reminds me that productivity doesn’t come from having more features, but from having fewer obstacles. It fits into my workflow instead of forcing me to adapt to it. I spend less time managing the tool and more time actually writing, documenting, and thinking clearly. Tools like Otter Wiki don’t chase trends or overload you with options. They focus on doing one job well and staying out of your way. That kind of simplicity holds up over time.