WhoDB
The hidden cost of a fragmented data stack
The hidden cost of a fragmented data stack isn't infrastructure. It's the decisions you never make.
The Database Stack Has Changed. Why Are We Still Using Database Tools Built for 2010?
Most engineering teams don’t rely on a single database anymore. Modern stacks are a mix of specialized systems: Postgres for transactions, Redis for caching, Elasticsearch for search, Neo4j for relationships, object storage for files, and vector databases for AI. The hard part is managing them all.
WhoDB Mock Data Now Respects Foreign Keys
The Last Seed Script You'll Ever Write You know the feeling. You just pulled the latest changes from the repo. You run docker compose up. The containers spin up green. You open your localhost port. And the app is empty. It's a ghost town. No users.
WhoDB CLI now live
Why We Built a Database Client for the Terminal (and Made It an MCP Server) I live in the terminal. If you’re reading this, you probably do too. For years, my workflow for checking a database record looked like this: I’m writing code in Neovim or VS Code.
Your Schema is Your IP. Stop Leaking It.
Keep Your Data Secrets Safe: Why Your Schema is Your Most Valuable Intellectual Property (And How Not to Leak It)
The Bloatware Tax
Why Your Database Client Is Costing You More Than You Think
What if your DB tool was...fun?
What if Your Database Tool Was Actually Fun?
WhoDB ❤️ Postgres
WhoDB ❤️ Postgres: Unlocking New Levels of Productivity and Insight
Is Your Database GUI Slower Than psql?
We Built WhoDB to Fix That
WhoDB is the Marie Kondo of Database Tools
WhoDB: The Marie Kondo of Database Tools- Spark Joy by Letting Go of Bloat
Polyglot Persistence in a Single UI
Polyglot Persistence in One UI: Simplifying Modern Data Architectures with WhoDB
Chat2DB needs 4GB of RAM. WhoDB needs 100MB.
Breaking Boundaries: How WhoDB Runs on Just 100MB of RAM
WhoDB - less is more
The Great Unbundling of the Database GUI: From Bloat to Pure Speed