I think the adoption hurdle will be hard unless you have a free plan that can be used for small things indefinitely. Having a hard cap on events would make me pass on this for fun side projects, which is where I would pivot later from to work projects. Just throwing that out there. This is why my last work project was supabase, I was using their free tier for some fun personal stuff.
If you have another vector for adoption that's fine too.
This is the first time I'm actually commenting on here, because this touches something I work with...
This seems to me like a cheap/worse copy of the EventSourcingDB by The Native Web (as others already mentioned).
I'm the auther of the rust sdk for the EventSourcingDB and therefore I know the API structure and so on pretty well and this looks like someone took an early version of that API, modified it a bit by renaming some fields and added some "features" that feel a little half-baked without addressing any of the things where there might be actual room for improvement.
At the same time the pricing model is also pretty similar to what the native web offers, just cheaper and offered by a single person instead of an established company.
tbh – this pretty much looks like they straight-up copied another database that dropped earlier this year. looks like GenesisDB grabbed all its ideas from here:
I'm Patric, and I just hit a major milestone - Genesis DB 1.0.(1) is officially production-ready.
Why I built this:
Existing event sourcing tools felt too heavy, opinionated, or expensive. I wanted something that matches how developers actually think about events - simple, transparent, and powerful.
What Genesis DB is:
- Event sourcing database engine written in Go
- HTTP + JSON interface (no proprietary protocols)
- Smart validation - Preconditions act as gatekeepers, enforcing business logic before writes hit the database
- Schema registration - Automatic event validation for type safety and data consistency
- Native GDPR compliance - One-command user data deletion, full data portability, built-in audit trails
- Battle-tested performance - Thousands of events/second, zero data loss, stable under load
- ...
The journey:
- Started because I love event-driven architectures but hated the tooling complexity
- A few versions, each adding features
- Now processing real production workloads across multiple industries
Want to try it?
- Free tier: 10,000 events for testing/small projects (I’m not here to be the biggest cost factor in any business. If you’ve got special requirements, let’s talk.)
- Self-host or use the managed platform (coming soon)
Amazing, well done. Having used Go for something similar can understand why you chose that for this venture. Wondering if there was anything in particular worked out for you with that decision?
this looks very cool. Rigging together your own event sourced Db is doable, but it gets a little annoying over time to keep DIYing everything, doing snapshot optimizations, etc...
one note: searchability on your query language named GQL may not be great, given the whole graphql thing.
Hi there,
I’m one of the creators of EventSourcingDB, and the CTO of the native web (the company behind EventSourcingDB).
Because of ongoing legal investigations I can’t comment any further, but I’d like to provide you with some links, so you can see for yourself:
https://www.eventsourcingdb.io
https://docs.eventsourcingdb.io
https://hub.docker.com/r/thenativeweb/eventsourcingdb
https://www.cqrs.com
https://www.eventsourcing.ai
Seems like very cool tech.
I think the adoption hurdle will be hard unless you have a free plan that can be used for small things indefinitely. Having a hard cap on events would make me pass on this for fun side projects, which is where I would pivot later from to work projects. Just throwing that out there. This is why my last work project was supabase, I was using their free tier for some fun personal stuff.
If you have another vector for adoption that's fine too.
This is the first time I'm actually commenting on here, because this touches something I work with...
This seems to me like a cheap/worse copy of the EventSourcingDB by The Native Web (as others already mentioned). I'm the auther of the rust sdk for the EventSourcingDB and therefore I know the API structure and so on pretty well and this looks like someone took an early version of that API, modified it a bit by renaming some fields and added some "features" that feel a little half-baked without addressing any of the things where there might be actual room for improvement.
At the same time the pricing model is also pretty similar to what the native web offers, just cheaper and offered by a single person instead of an established company.
TLDR: This is IMO a cheap copycat of the original EventSourcingDB by The Native Web (https://www.thenativeweb.io/products/eventsourcingdb).
tbh – this pretty much looks like they straight-up copied another database that dropped earlier this year. looks like GenesisDB grabbed all its ideas from here:
https://hub.docker.com/r/thenativeweb/eventsourcingdb
take a look and see for yourself… #copycat
Where can I see the architecture and the libraries used for this project?
Hey!
I'm Patric, and I just hit a major milestone - Genesis DB 1.0.(1) is officially production-ready.
Why I built this: Existing event sourcing tools felt too heavy, opinionated, or expensive. I wanted something that matches how developers actually think about events - simple, transparent, and powerful.
What Genesis DB is:
- Event sourcing database engine written in Go
- HTTP + JSON interface (no proprietary protocols)
- CloudEvents native with zero vendor lock-in
- One-command backups/restores
- Built-in Prometheus metrics & structured logging
Major features that made it to 1.0:
- Smart validation - Preconditions act as gatekeepers, enforcing business logic before writes hit the database
- Schema registration - Automatic event validation for type safety and data consistency
- Native GDPR compliance - One-command user data deletion, full data portability, built-in audit trails
- Battle-tested performance - Thousands of events/second, zero data loss, stable under load
- ...
The journey:
- Started because I love event-driven architectures but hated the tooling complexity
- A few versions, each adding features
- Now processing real production workloads across multiple industries
Want to try it? - Free tier: 10,000 events for testing/small projects (I’m not here to be the biggest cost factor in any business. If you’ve got special requirements, let’s talk.)
- Self-host or use the managed platform (coming soon)
Full docs at https://docs.genesisdb.io
Thanks for reading!
Congrats on hitting 1.0. love the focus on simplicity and real world dev workflows
Just a little hint: Read the other comments as well…
Thanks a lot! That means a lot. Simplicity + real-world workflows is exactly what I wanted to nail.
Amazing, well done. Having used Go for something similar can understand why you chose that for this venture. Wondering if there was anything in particular worked out for you with that decision?
Just a little hint: Read the other comments as well…
Nobody tell Greg Young!
this looks very cool. Rigging together your own event sourced Db is doable, but it gets a little annoying over time to keep DIYing everything, doing snapshot optimizations, etc...
one note: searchability on your query language named GQL may not be great, given the whole graphql thing.
Congratulations! I don’t think the db engine is open source. Any plans to do that?
Why not just hook up postgres to something like https://github.com/cpursley/walex or any of the other libraries like Debezium, https://sequinstream.com? Isn't postgres enough?