Meridian Studio — content tooling, dark by design.
A dense, opinionated content production console for one solo software-engineering creator. Linear’s density meets Bloomberg’s data confidence meets Raycast’s polish — and zero light theme, because the operator runs at midnight.
Most “creator tools” are made for people who don’t write code.
We make content as part of the actual job — building products, writing about what we learn, posting about it on three different surfaces in three different formats. The existing creator tools are designed for a person who has a marketing team and a content calendar. We have neither.
Meridian Studio is the tool we wanted: dense panels, drafts and queues you can navigate by keyboard, model usage and cost in the chrome, evals on whatever the LLM touches. It’s ours. It’s a daily driver. It will be open source when it’s less embarrassing.
Decisions baked in.
- Dark, on purpose. Not “light theme with the colors inverted.” Composed specifically for the dark monitor of someone working past midnight.
- Information density first. Whitespace is a tool, not a religion.
- Keyboard-navigable everywhere. The mouse is for visiting websites, not for using software you live in.
- Model usage and cost visible on every action that touches an LLM. You should not have to leave the page to know what you spent.
- Evals run on the draft pipeline. Hook score, claim check, tone score, before the draft ever goes to queue.
Boring stack, on purpose.
Next.js with tRPC and Postgres. Anthropic + structured outputs for the LLM bits. Tailwind for the dense panels because there’s a single operator and shipping speed wins. No microservices, no queue infrastructure, no compromises that exist to be photographed for an architecture diagram.
“I do not believe in your tool. I believe in mine. Mine is awful too. But it is mine.”
— studio notes, every product strategy meeting