redb

Typed data & integration ecosystem for .NET

Four products, one stack, .NET-first.

redb — RTTI Storage

storage

Typed object storage for .NET: store C# objects, query with LINQ, build trees — on PostgreSQL, SQL Server or SQLite. No migrations, full typing.

Learn more GitHub ↗ NuGet ↗

integration

The .NET equivalent of Apache Camel: 27 transports (Kafka, RabbitMQ, HTTP, SQL, S3, LLM, MCP …), a fluent DSL and 30+ EIP patterns.

Learn more GitHub ↗ NuGet ↗

runtime

The .NET analogue of Apache Camel K: runtime container for redb.Route — hot-reload DLLs, cluster with leader election, REST/CLI/dashboard.

Learn more GitHub ↗ NuGet ↗

auth & SSO

Transport-agnostic OAuth 2.1 / OIDC server on OpenIddict + redb.Route: DPoP, PAR, DCR, SCIM, FIDO2, first-class audit.

Learn more GitHub ↗ NuGet ↗

2026-08-13	redb 3.6.0: a bug report that turned out to live in six providers — plus AS2/EDI and a shared port A user's report exposed a cross-conversation leak in the core query provider — 6 of 6. Also in 3.6.0: AS2/EDI, a shared Kestrel, Camel parity.
2026-08-07	AS2 in .NET without a separate Java gateway: EDI with trading partners, right inside the route AS2 — signed, encrypted S/MIME document exchange with trading partners — is now a native redb.Route connector, not an external gateway.
2026-08-07	A real local database in Blazor WebAssembly and MAUI: no DbContext, no Include, no migrations Offline storage for complex graphs and an outbox queue: quick start for MAUI and the browser, everyday operations, and why EF Core just gets in the way here.
2026-07-30	What an integration layer really costs: a TMS backend counted line by line An integration layer on WSO2 MI and EF Core, counted line by line: what a real TMS backend costs to keep running.
2026-07-30	A TMS backend, architecturally: cluster, coordinate streams and a typed object store How a TMS backend is built: fifteen modules over three nodes, coordinate streams through Kafka and Redis, and a typed object store.
2026-07-30	We ported a module off an ESB and the code grew 1.7×. That was the right outcome One module moved off the ESB and the code grew 1.7 times. Why that was the right outcome, counted module by module.