Files.md is a lightweight, open-source note-taking tool that stores everything as plain Markdown files — no proprietary formats, no lock-in, no subscriptions. Here is what software teams should know.

Files.md: The Open-Source Note-Taking Tool Challenging Obsidian

Plain text has outlasted every productivity fad of the last two decades. Wikis, mind maps, interactive notebooks — they all came with promises and eventually came with problems. Files.md bets that the smartest thing a knowledge tool can do is get out of the way and let Markdown files be Markdown files.

What Files.md Actually Is

Files.md is a minimal, open-source knowledge base and note-taking tool built around a single principle: your notes are just files on disk. There is no proprietary database, no sync server you have to trust, and no binary blob that holds your thinking hostage. You point the tool at a directory of .md files, and it renders them into a navigable, linkable knowledge base.

That is it. That is the pitch — and for a certain class of user, it is a very compelling one.

Why Obsidian Generates Frustration

Obsidian is genuinely powerful. Its graph view, plugin ecosystem, and community are difficult to beat. But it carries a set of trade-offs that quietly accumulate over time:

Sync costs money. Obsidian Sync starts at $4/month per user — trivial alone, but it adds up across a team.
The plugin ecosystem is a double-edged sword. A vault that leans heavily on community plugins becomes brittle. Plugins break on updates, get abandoned, or introduce performance regressions.
It is not truly open. The core application is free to use but not open-source. For teams with strict compliance requirements or self-hosting mandates, that matters.
Portability is theoretical, not practical. Yes, files are Markdown — but metadata, plugin-generated content, and internal link formats create soft lock-in that makes migration painful.

Files.md addresses nearly every item on that list by simply not having those features in the first place.

The Philosophy of Doing Less

There is a class of software tool — call it "sharp-edged minimalism" — where the constraints are the feature. sqlite, htmx, and rsync all belong to this category. Files.md is making a case for membership.

By refusing to abstract away the file system, it gives you something most modern tools have quietly taken: the ability to use any other tool on your notes at the same time. Your notes are just files. Run grep across them. Pipe them through pandoc. Commit them to Git. Back them up with rsync. None of that requires a plugin or an export step.

# Full-text search across your entire knowledge base — no plugin required
grep -r "microservices" ~/notes/ --include="*.md" -l

This composability is something senior engineers instinctively value. A note-taking tool that plays nicely with the rest of your toolchain is worth more than one that replaces it.

What This Means for Software Teams

Engineering teams are knowledge-intensive by nature. Architecture decisions, incident post-mortems, onboarding guides, API contracts — all of it lives somewhere, and "somewhere" is often a chaotic mix of Confluence pages nobody updates, Notion docs with broken embeds, and Slack threads that vanish after 90 days.

A Git-backed, plain-Markdown knowledge base solves several problems at once:

Version history for free. Every change is a commit. You can see who changed the architecture decision record and when, without a paid audit log.
Pull request reviews for documentation. Changes to the team wiki go through the same review process as code changes. Junior engineers cannot accidentally delete the deployment runbook.
Works in air-gapped environments. For teams building in fintech, healthcare, or government — sectors common in Ghana's growing tech ecosystem — self-hosted, offline-capable tooling is often a regulatory requirement, not a preference.
Zero marginal cost at scale. Whether you have five engineers or fifty, a directory of Markdown files costs the same to run.

The Honest Trade-Offs

Files.md is not for everyone, and it would be dishonest to pretend otherwise.

Teams that rely heavily on embedded databases, Kanban boards inside their notes, or rich media embedding will find the experience sparse. The graph view that makes Obsidian's backlink navigation so satisfying is absent. There is no mobile app with offline sync baked in.

For non-technical users — product managers, designers, or clients who need a polished editing experience — a raw Markdown tool with a file-system metaphor can be alienating. The onboarding cost is real.

But for teams of engineers who are already comfortable in terminals and text editors, the friction is minimal and the payoff is significant.

Where Open-Source Knowledge Tools Are Heading

The broader trend here is worth noting. The success of tools like Logseq, Foam (VS Code), and now Files.md signals a growing appetite for local-first, open-source knowledge management. Users are increasingly skeptical of cloud-first tools that hold their data hostage behind a subscription wall.

The local-first software movement — championed by researchers at Ink & Switch — argues that software should work offline, sync without a server, and give users ownership of their data. Files.md is a practical implementation of those values, even if it does not invoke that framing explicitly.

For SaaS founders, this is an instructive signal. Users are not just buying features anymore. They are buying trust, portability, and control. Products that make data export easy, support open formats, and avoid aggressive lock-in are earning loyalty that pure feature richness cannot.

Why This Matters for Your Project

If your team is building or scaling a software product, your internal knowledge infrastructure is part of your engineering velocity. A documentation system that lives in Git, costs nothing to host, and works with your existing CLI toolchain removes friction from the moments that matter most — onboarding a new engineer, recovering from an incident, or making an architectural decision under pressure. Files.md is a reminder that sometimes the best infrastructure choice is the one that trusts you to be an adult with your own files.

Source: Files.md on GitHub, via Hacker News.