upmostly

Thanks Simon! Looking into that now. Big fan. Hope you enjoyed the post.

Edit: This should now be fixed for you.

I was inspired to write this blog post after reading bambax's comment on a HN post back in 2023: https://news.ycombinator.com/item?id=37082941

Thanks for taking the time to share your thoughts. We’ve heard this feedback loud and clear from a lot of people, and we completely understand where you’re coming from.

We’re about to introduce a one time purchase option that includes a full year of updates. No subscription required. This will be available later this coming week.

Really appreciate you checking out the project and pushing us to make the right call for our users. Stay tuned.

Without a doubt, 100%. In fact, you can use it offline if you want. We only make network requests when authorising user accounts. But even then you don't need to create an account. You can just use the free version offline.

We just wouldn't do that in a million years.

Our goal is to build the best DB client around, and one aspect of that is building trust. We haven't even added user analytics tracking into the product.

Agreed! The more competition, the merrier. Good luck to you guys!

Great question! Postgres is supported right away because it behaves like a standard, direct database connection. But with services like Neon and Supabase, there are extra nuances we want to handle properly.

We want Neon, Supabase, and similar cloud providers to feel like first-class citizens inside DB Pro and not just “another Postgres connection”. Each of them has their own quirks, authentication flows, and connection requirements. For example, Supabase actually needs a paid IPv4 add-on if you want to connect to it in the traditional way, which isn’t obvious to most users.

So instead of lumping them in as generic Postgres connections, we’re building dedicated flows that understand these details and make the whole experience seamless. That’s why they’re marked as “coming soon”. We’re doing them properly.

It all goes back to our UX first philosophy to build the absolute best experience.

I’m building DB Pro, a modern database workbench that makes working with Postgres, SQLite, and MySQL fast and intuitive.

I’m documenting the journey in monthly devlogs.

Here’s the first devlog: https://youtu.be/cSY-C8oiUU8

You can check it out here. We're very close to launching a v1: https://dbpro.app

For me, the only lacking feature of vanilla HN is dark mode. I wish they'd add that. Other than that, it's perfect.

This is really interesting — I’ve been working on something in a similar space called DB Pro (https://dbpro.app), a modern desktop database workbench.

We ran into the same challenge with SQL parsing and validation early on. Most open-source parsers tend to either choke on dialect quirks or fail silently when dealing with incomplete queries, which makes proper linting or fault tolerance a nightmare. For DB Pro, I ended up writing a lightweight validation layer on top of the parser that can recover gracefully and still provide syntax hints or AI-assisted corrections.

The LLM side gets especially tricky when you want to offer reliable query generation but still ensure correctness and safety. That’s why DB Pro lets users optionally download and run a local model for SQL assistance — so everything stays on the machine and we can still iterate safely without sending any data to the cloud.

Curious how you approached error recovery — did you build your parser from scratch or extend an existing one? And do you plan to release it as a standalone library?

I’ve been working on DB Pro — a modern desktop database workbench built with Electron, React, and Drizzle ORM. It’s designed to feel fast, cohesive, and genuinely enjoyable to use — something that sits somewhere between TablePlus, Notion, and VS Code.

Right now it connects to local and remote databases like SQLite and Postgres, lets you browse schemas and tables instantly, edit data inline, and create or modify tables visually. You can save and run queries, generate SQL using AI, and import or export data as CSV or JSON. There’s also a fully offline local mode that works great for prototyping and development.

One of the more unique aspects is that DB Pro lets you download and run a local LLM for AI-assisted querying, so nothing ever leaves your machine. You can also plug in your own cloud API key if you prefer. The idea is to make AI genuinely useful in a database context — helping you explore data and write queries safely, not replacing you.

The next big feature is a Visual Query Builder with JOIN support that keeps the Visual, SQL, and AI modes in sync. After that, I’m working on dashboards, workflow automation, and team collaboration — things like running scripts when data changes or sharing queries across a workspace.

The goal is to make DB Pro the most intuitive way to explore, query, and manage data — without the usual enterprise clutter. It’s still early, but it’s already feeling like the tool I always wanted to exist.

You can see it here: https://dbpro.app

Would love to hear feedback, especially from people who spend a lot of time in database clients — what’s still missing or frustrating in the current landscape?

Scrolling through that page feels like an incredible speedrun of design history. You can literally see the decades fly by — the photography, layouts, and even the fonts slowly evolving until suddenly, around 2006, it all starts to feel “modern.”

I’m 37, and that’s exactly the point where it clicks for me — when things stop looking “old” and start looking like the world I remember stepping into as an adult. It’s fascinating how our personal timelines sync up with broader shifts in design trends.

The N+1 problem basically means instead of making one efficient query, you end up making N separate queries inside a loop. For example, fetching a list of tables, then for each table fetching its columns individually — that’s N+1 queries. It works, but it’s slow.

We ran into this while building, funnily enough, a database management app called DB Pro (https://dbpro.app) At first we were doing exactly that: query for all schemas, then for each schema query its tables, and then for each table query its columns. On a database with hundreds of tables it took ~3.8s.

We fixed it by flipping the approach: query all the schemas, then all the tables, then all the columns in one go, and join them in memory. That dropped the load time to ~180ms.

N+1 is one of those things you only really “get” when you hit it in practice.

Absolutely stunning experience. The way the houses rolled over the hill as I walked. Incredible.

Wow, that's a really nice thing to say. I personally don't think so but that means a huge amount to hear. Thank you. One thing I did before jumping into making the video was to look, like really look at other YouTuber's videos. Kind of what I assume the author of the original article did. Look at how other successful people are doing something and copy as much of the execution as possible.

A new kind of database workbench for developers/founders/teams for:

- managing your database

- creating beautiful dashboards quickly

- writing, running and sharing queries (think postman but for db)

- visually building workflows to export and manipulate your database (so underrated)

- eventually building apps directly on to your database (think retool but a desktop app)

It's an all in one, modern way to interact with your database. Desktop app.

Right now we're totally bootstrapped so it's a combination of:

- Davinci Resolve (free)

- Epidemic Sound (for music and sound)

- ClearAudio.ai for VO processing

I then give myself the whole week to produce the video and honestly that has increased the quality by 10x. I'm not rushing it and can properly spend 2 days putting the video clips together, and another day on just the voice over alone.

I've always struggled to find the right balance as a solo/indie dev.

However, recently I decided to try something I'm calling the SaaS Schedule Sandwich.

Each month is split into four weeks:

- Week 1: Build

- Week 2: Market

- Week 3: Build

- Week 4: Video Journal

And so far it's kept me honest and not made me go live in a cave and code for a year.

I actually released the first video journal last week for our new product:

https://youtu.be/cSY-C8oiUU8

This space is SERIOUSLY saturated. We tried our hardest to break into the vibe coding space with Hypership, but we counted about 40 different vibe coding tools with that number growing weekly.

Yours will make it 41.

Good luck. Seriously. It's a war zone out there.

Not only do we give you auth out of the box (like Supabase) but we give you app hosting, analytics, event tracking, logs and we have plans to expand our services to cover forms, a help widget, and even Cookie consent!

Also we let you build an app using AI, which is a pretty huge difference between us and Supabase.

We've been working on a vibe-coding platform called Hypership.

https://hypership.dev

What's different with Hypership is that your apps get user auth, page view analytics, event tracking, logging, and an admin dashboard all set up and ready to go out of the box.

It's also a much nicer platform for devs because we host VS Code in the cloud for you as you're vibe coding. That means you can manually edit the code as you go.

It's basically what web development should be in 2025.

This could be incredible. Kind of like Strands on NY Times but in Wordle format.

Tried this but ended up building our own competitor: Hypership.dev

We're solving slightly more than what Coolify are by providing Auth, analytics, event tracking, an admin dashboard and more.

Great article. I 100% agree with the "too much magic" section.

I mean, have you ever tried to self-host Next? Good luck!

We managed to get it working when building Hypership, but it took my co-founder a long time to figure out and then the fantastic work of the devs at OpenNext in order to get it working.

https://hypership.dev

Just tried emailing you and your contact form doesn't work.

Agree about changing the name. Manus is the joke name of child in a British TV comedy called Amandaland. It's more of a joke name than anything.

I’m working on Hypership (https://hypership.dev) – a platform that lets you deploy full-stack React and Next.js apps with auth, user management, events, and analytics in minutes. We’ve built first-class support for Next.js, handling SSR, static exports, and edge deployments seamlessly.

We’re also building our own CDN to optimise asset delivery and improve performance across deployments. But beyond infra, we’re betting on something bigger: developers want everything they need to ship an app in one place—not just UI kits, but fully hooked-up components that handle state, auth flows, and analytics automatically.

That means forms, a help desk, user management, and more—all tightly integrated so you can focus on building rather than stitching services together.

Would love to hear from anyone who’s been frustrated by piecing together third-party tools just to get a product off the ground!

Could not agree more.

In fact, we’re tackling this exact problem with Hypership (https://hypership.dev) but in the React/Next.js and JavaScript space. Infra, auth, events, analytics, forms, database, API, everything you need to ship a product, all configurable in minutes with no glue code.

Laravel is 100% going all in on their cloud, tightly integrating their entire ecosystem. I mean, have you seen how many products they have?!

The trade-off is clear: speed vs lock-in. I'm betting on flexibility without the setup overhead. Agencies will gobble this service offering up in no time.

I was also very confused by this.

"Will create a Show HN post that reaches #1, showcasing a developer tool that simplifies the modern web stack"

It knows me so well.

This is incredible.