5/28/2026
When the Best Tool Still Feels Like Work
You sit down to write a thought. Something struck you during a conversation, or while reading, or in the shower. You open your note app. A toast notification tells you three plugins need updating. One of them has a breaking change. You open settings, scroll through a list of toggles you half-remember configuring, fix the conflict, and close the modal.
What were you going to write?
It’s gone.
The best tool in the world
Let’s be honest: Obsidian is a remarkable piece of software. Local-first files. A plugin ecosystem that can turn a Markdown editor into almost anything. A passionate community that builds, shares, and iterates at a pace most companies can’t match.
If you are the kind of person who enjoys configuring systems — who finds satisfaction in wiring Dataview queries, writing Templater scripts, and tuning a CSS snippet until the spacing feels right — Obsidian might be the best tool ever made for you.
But not everyone is that person.
The game-rules problem
A good game has simple rules and deep play. Chess has six piece types. Go has one rule for capture. The depth comes from the interaction, not from the rulebook.
Note apps should work the same way. The fewer rules you need to learn before you can start thinking, the faster your thinking begins. Every configuration screen, every plugin README, every “you need to enable X in settings first” is a rule you have to learn before the game starts.
Obsidian’s plugin system is extraordinarily powerful. But power and simplicity pull in opposite directions. The more a tool can do, the more a user must learn before the tool does anything at all.
Not everyone is a power user
The Obsidian community has built incredible things. Templater scripts that generate structured notes. Dataview queries that turn a vault into a personal database. Workflows so elaborate that people sell courses teaching you how to use a note app.
Read that again: people sell courses teaching you how to use a note app.
There’s a whole economy around the complexity. Template marketplaces. YouTube tutorials with thirty-minute setup walkthroughs. Prompt engineering guides for getting an LLM to write your Templater code, because the Templater code is too hard to write yourself, because you needed Templater in the first place because the app didn’t do what you needed out of the box.
This isn’t a criticism of the people building those things. They’re solving real problems. But the fact that the problems exist at all tells you something about who the tool was designed to serve.
Salieri’s users
In Amadeus, Salieri is the court composer who recognizes Mozart’s genius but cannot match it. He is talented, hardworking, and deeply committed to music. He is just not Mozart.
Most of us are Salieri.
We are not power users. We don’t want to write code to take notes. We don’t want to spend a weekend configuring sync before we can write on two devices. We don’t want to learn a query language to find something we wrote last month.
We want to sit down, write a thought, connect it to other thoughts, and close the app. That’s it.
The best tool in the world means nothing if it makes ordinary people feel like they are failing at note-taking. If your productivity system requires a course, a template pack, and a YouTube playlist before it starts working — the system is not working. You are working for the system.
What I don’t want to build
I don’t want to build a tool that makes its money selling templates. I don’t want to hold sync hostage behind a subscription. I don’t want someone else to build a course teaching people how to use my app, because if that course needs to exist, I have failed.
I don’t want users to feel the quiet shame of knowing a tool is powerful and suspecting they are not using it well enough. That feeling — that gap between what the tool could do and what you actually do with it — is plugin fatigue. It’s not laziness. It’s a design failure.
What Afterglow is
Afterglow is a personal knowledge workbench. Not a platform. Not a plugin marketplace. Not a canvas you assemble from parts.
The product scope is deliberately narrow: capture ideas, connect them, and make the library more useful over time. That’s it. If a feature doesn’t serve the flow of knowledge, it’s not in scope.
- Self-hosted is free. Your data, your server, no cost.
- Native apps for iOS, macOS, Windows, and Android are paid. That’s how the product sustains itself — convenience, not hostage-taking.
- No plugin system. What you need is already there.
- No template marketplace. The defaults work.
- No sync ritual. It just syncs.
- Beautiful by default. Not beautiful after a weekend of configuration.
The champion of the ordinary note-taker
Afterglow is not for people who love configuring tools. Those people already have a great option. Afterglow is for people who love thinking — and want a quiet, complete, beautiful place to do it.
You shouldn’t need to be a power user to feel like your knowledge tool is working. You shouldn’t feel left behind because you didn’t install the right plugin, or learn the right query language, or watch the right tutorial.
Your thinking deserves a home that’s ready when you are.