VillageSQL
A Fork of MySQL with Extensions
Details
- External ID
- 46900057
- Source
- HN
- Company
- —
- Product
- VillageSQL
- Website domain
- villagesql.com
- Launched
- Feb. 5, 2026
- Cohort
- —
- Upvotes
- 12
- Upvotes percentile
- 0.5970350404312669
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
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!
Enrichment
- Theme
- database infrastructure and developer tools
- Vertical
- Horizontal
- Function
- Data infrastructure
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Hobby / open-source project
- Normalized one-liner
- mysql fork with additional features
- Manually corrected
- False
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 — 148 launches clear the similarity bar, closest 8 shown.
Attention rank: #70 of 149 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 98 days after the earliest competitor.
- VillageSQL = MySQL and Extensions · hn · 2026-02-05 · 27 upvotes · similarity 0.87
- DeepSQL · hn · 2026-07-20 · 52 upvotes · similarity 0.54
- I'm not a PostgREST fan this is why I'm building an alternative · hn · 2026-09-09 · 5 upvotes · similarity 0.53
- PostgreSQL Migrator · ph · 2026-09-17 · 2 upvotes · similarity 0.50
- LinkedQL · hn · 2025-12-08 · 31 upvotes · similarity 0.48
- uplpgsql · hn · 2026-07-16 · 10 upvotes · similarity 0.47
- Xsql · hn · 2025-12-16 · 11 upvotes · similarity 0.47
- Pglayers · hn · 2026-07-01 · 40 upvotes · similarity 0.44
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a data infrastructure tool for Media & entertainment yet.