The Problem With Admin Panels
June 24, 2026
So lets start from this; I've been building full stack applications, and one thing keeps coming up:
admin panels.
Every application eventually needs one.
You need somewhere to manage users, teams, settings, content, subscriptions, support requests, or whatever data your application revolves around.
The strange thing is that despite how common this problem is, I rarely find a solution that feels right.
Most admin tools fall into one of two categories.
The first category looks and feels like a spreadsheet. They're functional, but they're difficult to share with clients or non-technical team members because they feel more like database viewers than actual products.

The second category is platforms like Payload CMS.
And to be fair, Payload gets a lot right.
The admin panel is clean, polished, and genuinely pleasant to use.

The problem isn't the admin panel itself.
The problem is everything that comes attached to it.
To get that experience, you have to adopt the entire ecosystem. Your data models, authentication, collections, relationships, configuration, and much of your application's architecture start revolving around the CMS.
If all you wanted was a great admin panel for an existing application, that's a surprisingly expensive trade.
That realization is what led me to start Console.
I don't want a spreadsheet.
I don't want a CMS that becomes the center of my application.
I just want an admin panel that connects to my existing database, understands my schema, and gets out of the way.
It's still early.
most of what exists today are notes, experiements, learning.
the goal is simple:
Connect a database, manage your application move on with your life