Nicheloom visits: 58,050 all-time · 7,694 in the last 7 days

The opportunity tracker for new startups.

Today: 1,953 launches · Niche of the day: specialized calculation tools · See what launched today →

VillageSQL

A Fork of MySQL with Extensions

Get picks like this daily. Today's launch numbers, the top launches, AI and tech news, and a daily opportunity pick, straight to your inbox.

Want to reach these readers? Sponsor an issue.

We built VillageSQL because we love MySQL, but we’ve watched the ecosystem stagnate while PostgreSQL flourished with extensions like pgvector and pg_textsearch. We wanted to give MySQL that same extensibility so teams don’t have to migrate databases just to keep building nowadays. VillageSQL is an open-source, tracking fork of MySQL that is a drop-in replacement and adds a true extension framework.How it works: +It’s a drop-in replacement+We added an interface to load external shared libraries (.so files) as extensions.+You define custom data types and functions (with indexes coming soon) that run natively inside the engine.+We are launching with a few proof-of-concept extensions: vsql-ai, vsql-uuid, vsql-crypto, vsql-network-address. We’re currently in alpha.We know forking MySQL is a big swing, but we believe the community needs a way to innovate on the core engine without waiting for Oracle and in a way that is easier to use than plug-ins.The code is open source here: https://github.com/villagesql/villagesql-serverWe’d love your feedback. Happy to answer any questions about the implementation!

HN · launched Feb 5, 2026 · 12 upvotes (top 40%) · 0 views

Niche: database management systems and engines · 162 launches, 5 in the last 7 days ▼ -17% · Explore this niche →

Category and tags

  • Horizontal
  • Data infrastructure
  • Developer
  • Not AI
  • Commercial product

Visit website ↗ Source listing ↗

Could you build this?

No Forking MySQL to implement a PostgreSQL-style extension framework requires deep systems engineering inside the MySQL C++ codebase.

What it would actually take: The architecture requires maintaining a fork of MySQL Server, refactoring internal subsystems (parser, lexer, optimizer, executor, and storage engine interfaces) to support external shared objects and runtime-registered data types or functions. The primary difficulties are MySQL's monolithic architecture, lack of native hook points compared to Postgres, and maintaining ACID compliance, memory isolation, and binary replication across custom extension boundaries. This requires experienced C++ systems database engineers.

Discussion

2 comments analyzed.

Competitors mentioned: Postgres

Concerns raised: GPL2 license requirement for extensions limits proprietary use, licensing incompatibility with non-GPL2 licenses

Feature requests: out-of-process SDK for independent extension licensing

Competitors

Other products that read as similar to this one : 260 launches clear the similarity bar, closest 8 shown.

Attention rank: #114 of 261 (itself plus its competitors, highest first, normalized so YC and Product Hunt are compared fairly).

Launched 98 days after the earliest competitor.

The niche, labels, vibe code rating and competitor comparison on this page are analysis by Nicheloom. If you use them, please credit nicheloom.com. How you may use our data.