Three open-source libraries. One coherent stack. All Apache 2.0.

This is the story of what we built, why, and how the three pieces fit together

in a way that surprised even us.

The problem

Enterprise .NET integration in 2026 still looks like this:

EF Core for data — plus a migration file every time a field changes

MassTransit or NServiceBus for messaging — great if you only need message brokers, but IBM MQ, SFTP, MQTT, SQL polling? Custom adapters, every time

Kubernetes + etcd for clustering — because "that's just how you do it"

We needed all three. We built all three. And then we noticed they could share

the same storage layer — and everything clicked.

Layer 1: redb.Core — typed EAV without the pain

github.com/redbase-app/redb · Apache 2.0

RedBase (REDB) - Entity Database for .NET | LINQ, Trees, Aggregations

Not a key-value store. Real objects, real queries.…