vane

Process multi-layer network traffic with composable flow-based pipelines.

82|4|Updated Sep 9, 2025
One-click install
npx skills add https://github.com/canmi21/vane --skill vane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vane
Source: https://github.com/canmi21/vane/tree/main
Command: npx skills add https://github.com/canmi21/vane --skill vane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Vane provides a high-performance, flow-based network protocol engine that bridges the gap between raw transport layer forwarding and complex application layer processing, offering a dynamic and composable pipeline architecture.

Core Features & Use Cases

  • Flow-Based Pipeline: Dynamic, composable pipeline architecture treating network connections as programmable flows.
  • Multi-Layered Processing: Handles traffic across L4 (TCP/UDP), L4+ (TLS/QUIC inspection/termination), and L7 (HTTP/1.1, HTTP/2, HTTP/3, WebSocket).
  • Extensible Plugin System: Supports internal and external plugins (HTTP, Unix, Command) for custom logic.
  • Use Case: Route TLS connections based on SNI without termination, upgrade listeners to L7 HTTPX for application handling, or apply middleware like header-based authentication for specific paths.

Quick Start

Use the vane skill to start the Vane proxy server with default configurations.

Frequently Asked Questions about vane

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does flow-based network traffic processing handle multiple protocol layers?

Flow-based network traffic processing treats connections as programmable pipelines, enabling dynamic multi-layer handling across L4 TCP/UDP, L4+ TLS/QUIC, and L7 HTTP protocols within a unified engine.

Can I route TLS connections based on SNI without termination in a reverse proxy?

Yes, you can route TLS connections based on SNI without termination. The proxy engine inspects L4+ traffic directly, allowing dynamic routing decisions before any application-layer handshake occurs.

How do I add custom middleware for HTTP header authentication in a Rust network proxy?

You add custom middleware for HTTP header authentication via the extensible plugin system. It supports internal and external plugins through HTTP, Unix, and Command interfaces to apply custom logic to specific paths.

Does the Rust network proxy engine support HTTP/3 and QUIC protocols?

Yes, the Rust network proxy engine supports HTTP/3 and QUIC protocols. It handles multi-layered traffic including HTTP/1.1, HTTP/2, HTTP/3, and WebSocket across L4+ and L7 processing layers.

What is the best way to maintain context continuity across L4 and L7 network layers?

The best way to maintain context continuity across L4 and L7 network layers is using a unified key-value store. This provides cross-layer context continuity throughout the composable traffic pipeline.

Can I apply hot-swappable configuration to a Rust reverse proxy without restarting?

Yes, you can apply hot-swappable configuration to the Rust reverse proxy without restarting. The flow-based engine allows dynamic pipeline reconfiguration during live traffic processing.