redb.Route

integration framework

The .NET equivalent of Apache Camel

Enterprise integration framework for .NET — wire any system to any system in a few lines of C#. A fluent DSL builds From → Process → To pipelines. No XML, no message-bus lock-in, no per-endpoint license fees.

GitHub ↗ NuGet ↗llms.txt ↗
25
transports
30+
EIP patterns
32
NuGet packages
OTel
built-in

What's inside

  • Brokers & messaging: Kafka, RabbitMQ, Azure Service Bus, IBM MQ, Amazon SQS/SNS, MQTT 5.0, AMQP 1.0, Redis.
  • Network & web: HTTP, gRPC, WebSocket, SignalR, raw TCP, Telegram Bot API.
  • Files & storage: File, FTP/SFTP, AWS S3 / MinIO, redb typed object storage.
  • Data & search: SQL (ADO.NET), Elasticsearch, LDAP / Active Directory, Firebase.
  • AI / LLM: llm: connector (OpenAI-compatible — 14 APIs — + native Anthropic, token streaming), MCP client (mcp:), and .AsLlmTool() to expose any transport as an LLM-callable tool.
  • 30+ EIP patterns (Splitter, Aggregator, CBR, Saga, Circuit Breaker, Idempotent Consumer, Scatter-Gather…), compiled expression engine, transactional routes, OpenTelemetry built-in.
  • Runs in production on redb.Tsak: .tpkg modules, hot-reload, clustering, REST/CLI/dashboard. 32 packages, Apache 2.0.

Latest releases

  • 3.6.0
    • Fluent DSL builders — endpoint URIs now round-trip through the parser; space-bearing values no longer
    • redb.Route.Llm — conversation isolation no longer depends on tree-filter semantics
    • redb.Route.Llm — tool routes now run on a child of the agent exchange, not on a naked one.
    • redb.Route.Llm — the run's principal and audit tags reach tools. The engine copied a hard-coded
  • 3.5.1
    • redb.Route.As2 — new AS2 (RFC 4130) B2B/EDI connector. Exchange business documents with trading
    • redb.Route.Http.Hosting — new shared Kestrel hosting package. SharedHttpServerManager (the
  • 3.5.0