About Neorgon
We made 24 tools and forgot to add a paywall.
Here's why we're keeping it that way.
The Problem We Started With
Every week, I'd build a small tool to solve a specific problem. A timezone converter for client calls. A visual canvas for mapping project strategy. A break-fix challenge to learn AWS. Each tool lived in its own silo—scattered across domains, repositories, and mental models.
The friction wasn't building the tools. It was finding them again when I needed them. I'd bookmark a URL, forget it existed, and rebuild something similar months later. Sound familiar?
Then friends started asking: "What was that tool you showed me?" I'd dig through browser history, Slack messages, old READMEs. The tools solved real problems, but discovery was broken.
Consolidation as a Feature
Neorgon is a deliberate consolidation strategy. One hub. One brand. One place to discover, remember, and share. Every tool keeps its own domain and identity, but they all answer to the same gravitational pull.
No Paywalls, No Signup, No Nonsense
Every Neorgon tool follows three rules:
Why? Because friction kills utility. A timezone converter that requires login is a broken timezone converter. A learning tool behind a paywall helps fewer people learn. We optimize for time-to-value: click link, solve problem, move on.
This isn't anti-business. It's pro-clarity. If a tool deserves to exist, it deserves to be accessible. Monetization (if it ever comes) will be additive—enterprise features, sponsorships, not paywalling the core utility.
Built for Builders
The hub itself is a teaching tool. Every animation, physics simulation, and accessibility choice is meant to be studied, forked, and remixed.
Technical Principles
We document the why, not just the what. Blog posts explain architecture decisions. Code comments reference GitHub issues. The source code is the spec.
The Road Ahead
Neorgon will keep growing—new tools, better accessibility, deeper documentation. But the core philosophy won't change:
- Tools solve real problems—no toy projects, no resume padding
- Consolidation over fragmentation—one hub, many tools
- Accessibility by default—motion, screen readers, keyboard nav
- Transparency in decisions—blog posts, Git history, open discussions
Maybe we'll add team features. Maybe we'll ship a CLI. Maybe we'll stay a solo project forever. The tools serve the mission, not the other way around.
Start Exploring
Try the tools. Read the source. Build something weird.
Neorgon is infrastructure for curiosity.