Obsidian for business: why a folder of Markdown files beats a proprietary database as your company's knowledge layer, with honest trade-offs.
My company's memory is a folder of Markdown files. Client knowledge bases, decision logs, meeting registers, project timelines: plain text files on disk, edited through Obsidian, updated three times a day by scripts. No proprietary database, no vendor account holding my work hostage.
That sounds primitive next to a Notion workspace or a Confluence instance. It is the most robust infrastructure decision I have made. The reason is simple: Obsidian is not really a note app. It is a lens over a folder of files you own. The app can disappear tomorrow; the knowledge layer survives, readable by any editor, any script and any AI agent, forever.