SWire.Redis 0.8.5-beta.2

<div align="center">

<picture> <source media="(max-width: 600px)" srcset=" <div align='center'> <img src='assets/SWire-Logo_Big.png' width='100' style='display:block; margin:auto;' /> <h1 style='font-family:monospace; margin-top:10px;'> <span style='color:#54CFC0;'>S</span>Wire </h1> </div> "> <div align="center"> <table border="0" cellpadding="0" cellspacing="0"> <tr> <td valign="middle"> <img src="assets/SWire-Logo_Big.png" width="120" style="padding-right: 20px;" /> </td> <td valign="middle"> <h1 style="font-family: 'Courier New', monospace; font-size: 3em; border-bottom: none; margin: 0;"> <span style="color: #54CFC0;">S</span>Wire </h1> </td> </tr> </table> </div> </picture>

<p align="center"> <strong>The Essential Secure Plumbing for Agents as a Service (AaaS)</strong> </p>

<p align="center"> <img src="https://img.shields.io/github/actions/workflow/status/Swire-Labs/SWire/ci-cd.yml?branch=dev&style=for-the-badge&logo=github&label=Build" alt="Build Status" /> <img src="https://img.shields.io/badge/NuGet-v0.8.5--beta.2-blue.svg?style=for-the-badge&logo=nuget" alt="NuGet Version" /> <img src="https://img.shields.io/badge/Coverage-100%25-brightgreen.svg?style=for-the-badge&logo=codecov" alt="Code Coverage" /> <img src="https://img.shields.io/badge/.NET-10.0-512bd4.svg?style=for-the-badge&logo=dotnet" alt=".NET 10" /> <img src="https://img.shields.io/github/license/Swire-Labs/SWire?style=for-the-badge" alt="License" /> </p>

</div>

🌟 The Vision: AaaS Tunneling Plumbing

SWire provides the critical secure infrastructure required for modern Agents as a Service (AaaS) architectures. It fills the gap by acting as a high-performance, encrypted nervous system, enabling agents to establish secure, bidirectional tunnels through any network barrier.

📦 Installation (NuGet)

SWire is modular. Install only what you need:

# Core installation
dotnet add package SWire --version 0.8.5-beta.2

# For a SignalR client
dotnet add package SWire.SignalR --version 0.8.5-beta.2

🏗 Architecture & Strategy

SWire follow an Open-Core model:

• Core (Community): Secure plumbing, E2EE, SignalR transport, and basic discovery.
• Premium (Enterprise): High-performance gRPC Bridge, advanced Redis scaling, and specialized connectors.

🔄 Protocol & HTTP Version Bridge

The Hub acts as a protocol-agnostic relay, enabling seamless communication across different network generations. SWire handles the complexity of bridging HTTP/1.1 (SignalR) and HTTP/2 (gRPC) flows:

• Legacy Compatibility: Agents on restrictive networks or older hardware can use HTTP/1.1.
• Modern Performance: High-speed agents can leverage HTTP/2 multiplexing.
• Seamless Interop: A SignalR agent can talk to a gRPC agent without knowing the underlying transport or HTTP version.

🛡️ Strategy-Based Routing

Since v0.8.0, the routing logic is fully decoupled using the Strategy Pattern. This allows adding new routing rules (like MCP-specific routing or user groups) without modifying the core MessageRouter.

🚀 Quick Start

1. Hub Setup (Server)

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddSWireServer(); // Core Relay & Hub Logic
var app = builder.Build();

app.MapSWireHub(); // Expose SignalR Endpoint
app.Run();

2. Agent Setup (Client)

var services = new ServiceCollection();
services.AddSWire();
services.AddSWireSignalRClient("https://hub.your-aaas-cloud.com/agentHub");

var provider = services.BuildServiceProvider();
var transport = provider.GetRequiredService<IMessageTransport>();

// Establish secure tunnel
await transport.ConnectAsync();

🛡️ Security & Privacy

• Zero-Knowledge: The server never sees unencrypted payloads.
• E2EE: AES-256-GCM encryption with RSA trust establishment.
• Anonymization: Built-in metadata scrubbing before any telemetry broadcast.

For more details, see our Security Policy.

💎 Open-Core Strategy

SWire is built on an Open-Core model, providing universal secure plumbing to the community while offering advanced binary optimizations for high-scale enterprise environments.

⚡ Performance & Efficiency

SWire is designed to be ultra-lean, making it suitable even for legacy hardware or low-power IoT devices.

Benchmark Results (Legacy Hardware)

Tested on: Dell Inspiron 1520 (Core 2 Duo @ 2.2GHz) - JSON-in-Binary Payload

Why gRPC even in Core? Even with JSON payloads, gRPC over HTTP/2 significantly reduces CPU overhead on older hardware compared to the SignalR management layer. Premium tier takes this further by removing JSON parsing entirely.

🗺️ Roadmap & Contributing

We are now at v0.8.5. Our path to v1.0.0 includes:

• Implementing the "Invisible Office" marketing sample (US#9.2).
• Generalizing the Result<T> pattern for all services.
• Finalizing the High-Performance gRPC Bridge (Premium).

Want to help? Check out our Contributing Guide.

<p align="center"> Built with ❤️ for the Privacy-Conscious AI future.<br/> <strong>Official Website: <a href="https://www.swire.be">www.swire.be</a></strong><br/> <strong>Part of the <a href="https://github.com/Swire-Labs">Swire-Labs</a> ecosystem.</strong><br/> Contact: <a href="mailto:swire-labs@proton.me">swire-labs@proton.me</a> </p>