You know the feeling. You’re using Workflowy, and everything is smooth — the zooming, the bullet structure, the buttery keyboard shortcuts. It’s the best outliner you’ve ever touched. And then you think: I wish I could just add one plugin. Just one. A calendar view. A kanban board. A way to connect notes the way Obsidian does.
And Workflowy says: no.
That “no” is the entire story.
A tool that refuses to grow with its users isn’t a tool. It’s a cage with good UX.
So someone did something about it. Over the past three weeks, a developer built an open-source Workflowy alternative — and not just a clone. Think Workflowy’s elegant outliner structure, Obsidian’s plugin extensibility, and Linear’s design polish, all in one. Built on TanStack Start, TanStack DB, and TanStack Virtualize.
Here’s where most people get it wrong. They look at this and see a copycat. A tribute act. Oh, another Workflowy clone. But that’s missing the point entirely.
The real opportunity isn’t replicating Workflowy. It’s building the platform Workflowy should have been — one where the community decides what comes next.
Workflowy’s best feature was never its simplicity. It was the promise that your notes could scale with your thinking. They just never delivered on the second half.
Think about what happened with Obsidian. It started as a Markdown editor. Then the community built plugins — and suddenly it was a Zettelkasten system, a task manager, a daily journal, a database, a whiteboard. The core team didn’t plan all of that. They just got out of the way.
That’s the play here. You don’t beat Workflowy by copying it. You beat it by letting a thousand developers out-innovate a single product team.
The developer behind this project put it simply: they wanted to explore directions Workflowy never would, and since Workflowy isn’t open source or plugin-based, they took things into their own hands.
That sentence should make every closed-source productivity tool a little nervous.
When you lock down your platform, you’re not protecting your product. You’re creating the exact frustration that births your replacement.
Now, will this project succeed? Three weeks of development is a starting point, not a victory lap. The plugin architecture needs to actually work. The community needs to show up. The beauty of Linear is notoriously hard to replicate — design at that level is a discipline, not a feature flag.
But the direction is right. The bet is correct. And the tension it exposes — between polished closed tools and messy open ones — is one of the defining arguments in software right now.
Workflowy built something beautiful and then built a wall around it. This project is what grows on the other side.
The best products don’t ask for permission to evolve. They hand the keys to the people who use them.
FAQ
Q: Isn't this just another Workflowy clone that'll be abandoned in 3 months?
A: Maybe. But the plugin architecture is the differentiator. If the community builds even a fraction of what Obsidian's community did, this becomes more than a clone — it becomes a platform. The risk is real, but so is the upside.
Q: Why should I switch from Workflowy to an unproven open-source alternative?
A: You shouldn't — yet. If Workflowy meets all your needs and you never crave plugins or customization, stay. This project is for the people who've hit Workflowy's ceiling and felt the wall.
Q: Won't plugins ruin the simplicity that makes Workflowy great?
A: That's the excuse closed platforms always use. Simplicity and extensibility aren't opposites — Obsidian proved that. You ship a clean core and let users opt into complexity. The fear of bloat is real, but it's a design problem, not a reason to lock the door.