Skip to content

Blueprint Catalog

Lane7 catalog blueprints are pre-composed, credential-injected Kubernetes networks ready to deploy. Each blueprint is a curated combination of pod types — see Pod Types & Composability for the building blocks.

Pricing

All blueprints are free to download. You pay only for active WoSP workloads while they are running. See Commercial Licensing.

All blueprints

Blueprint Security Mode Protocol Pods Environment Use Case
Armored Ferry — Secure API Gateway Armored Car HTTP1/REST 2 Single External-facing API entry point
Armored Convoy — Serial Relay Pipeline Armored Car HTTP1/REST 3 Single Transformation / enrichment middleware
Armored Trawler — Result Collector Armored Car HTTP1/REST 3 Single Fan-in aggregation from parallel sources
Armored Trimaran — Secure Application Router Armored Car HTTP1/REST 4 Single Fan-out broadcast to parallel services
Armored Carrier — Parallel Processing Cluster Armored Car HTTP1/REST 6 Single Full scatter/gather orchestration
Fast Ferry — WebSocket Streaming Relay Armored Tunnel WebSocket 2 Single Real-time telemetry / chat
Fast International Ferry Armored Tunnel WebSocket 2 Multi Cross-region WebSocket streaming
International Ferry — Cross-cloud Relay Armored Tunnel HTTP2/gRPC 2 Multi Cross-cloud gRPC connectivity
Armored Carrier — Zero Trust AI Pipeline Armored Tunnel HTTP + WebSocket 6 Single AI agent network with prompt injection prevention

Choosing a blueprint

1. Single or multi-cluster? If all your services live in one Kubernetes cluster, any single-cluster blueprint works. If you need to connect pods across separate clusters or cloud providers, choose Fast International Ferry (WebSocket) or International Ferry (gRPC).

2. HTTP, gRPC, or WebSocket? HTTP1/REST for standard APIs and webhooks. gRPC for bi-directional streaming and low-latency RPC. WebSocket for persistent real-time connections. The Armored Carrier AI Pipeline uses HTTP + WebSocket for mixed AI workloads.

3. Do you need external trigger access? If a client outside Kubernetes needs to call POST /trigger to start the network, the blueprint's Gateway must be a boundary pod (PINHOLE_ENABLED=true). All catalog blueprints include a boundary Gateway. If you need the result accessible externally too, the Sink boundary pod exposes GET /output.


Understanding the building blocks →