· 2 min read

Why my private, AI-powered research and writing stack runs on a truly Open-Source tool, and it's not Obsidian

Obsidian is popular, but Joplin is sovereign. We explore how to build a private, AI-powered research and writing stack using truly open source tools that keep your intellectual property strictly on your own hardware.

Why my private, AI-powered research and writing stack runs on a truly Open-Source tool, and it's not Obsidian

From a spark of an idea written on paper, grounded with Google's Deep Research and NotebookLM to a final published piece, my writing-publishing workflow lives inside a single, private, Open-Source ecosystem: Joplin. Let me show you my setup.

My process has three core stages, all connected within one central hub:

1. Research & Capture

The process starts with broad discovery using tools like Google Gemini (Deep Research). But once I find valuable articles, papers, or snippets, they need a home. For this, Joplin's Web Clipper is indispensable. I can save full web pages or simplified articles directly into my knowledge base, creating a rich, offline-first library of source material.

2. Writing & Synthesis

Now, many people in this space use and love Obsidian. It's a fantastic tool. But for me, a core principle was non-negotiable: the software must be truly #OpenSource. Obsidian is not. Joplin is. That was the decisive factor.

Plus: Joplin becomes an AI-powered studio with the Jarvis plugin. The key difference from the fragmented Obsidian ecosystem is that Jarvis is a single, cohesive suite that feels native to the app.

My writing process inside Joplin looks like this:

Crucially, by using local models, my research, notes, and drafts never leave my machine. This is the ultimate in privacy and control.

3. Publishing

The entire pipeline, from initial outlines and messy drafts to final, polished versions, is organized in Joplin notebooks. It’s my single source of truth before anything gets published.

This stack gives me the best of all worlds: the principles of open source, the security of local-first data, and a powerful, private AI assistant.

There's a fascinating ecosystem of tools out there. What does your personal knowledge stack look like? Share your setup below!

Sources:

Official website: https://joplinapp.org/
GitHub repository: https://github.com/laurent22/joplin/
Joplin cloud: https://joplinapp.org/plans/
Jarvis plugin: https://joplinapp.org/plugins/plugin/joplin.plugin.alondmnt.jarvis/

Read next

A roller conveyor in a dim warehouse carries a long row of identical new cardboard boxes. Among them ride a few old, crumpled boxes patched with tape, one in sharp focus at the center.
Article Open Source Digital Sovereignty

The fix is out. Is it in?

Almost four years after a free fix shipped, about one in eight Log4j downloads was still a vulnerable version. Now AI has bank regulators counting the days. Why private copies slow the fix down, what the banks' new alliance changes, and the question to ask your IT team.

Kai A. Hartung
Kai A. Hartung
· 2 min read
A long till receipt listing licences, cloud, add-ons and contractors, torn off just below the word TOTAL.
Article Open Source Digital Sovereignty

The bill nobody can add up.

The Dutch government has a Linux desktop on trial, no new money for its digital autonomy plans, and no total for what it pays Microsoft. Leaving shows up as line items someone must sign for. Staying hides in budgets nobody adds up.

Kai A. Hartung
Kai A. Hartung
· 6 min read
Mock AI model page labelled "Open Source" but marked "not an open release," with a locked, disabled "Request access" button and a "Sold via a private cloud" sticker.
Article Open Source Digital Sovereignty

Open in name only.

Germany spent public millions on a "Sovereign Open Source" AI, then gated it and let a vendor sell it. Switzerland and the Netherlands show the difference: real openness is a mandate, not a label.

Kai A. Hartung
Kai A. Hartung
· 2 min read