TiloBox
Back to directory
Pipy project preview

Pipy

Extensible, programmable cloud-native network stream proxy and traffic orchestrator.

LicenseApache-2.0
GitHub stars6.4k
Last commit1 weeks ago
Tags5 topics
Submillisecond Edge ProxyPipyjs Traffic ScriptingSsl Offloading Load BalancerDeveloper ToolsProgrammable Network Proxy
Overview

Why consider Pipy?

Pipy is an open-source lightweight network proxy written in C++ and scripted with PipyJS. Designed for edge computing and service meshes, it delivers sub-millisecond proxying, load balancing, SSL offloading, and custom packet filtering.

Guided learning

Learn Pipy by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Pipy

Pipy scripts complex network packet manipulation and request routing using standard JavaScript syntax.

Quickstart

bash
1git clone https://github.com/flomesh-io/pipy.git
2cd pipy
3# Run pipy script
4pipy my-proxy.js

Create custom TCP/HTTP filtering pipelines with simple JavaScript event handlers.

Pipy is licensed under the Apache License 2.0.

Related tools

More options with a similar category or technology profile.

Pipy FAQs

Pipy is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Pipy is listed under the Apache-2.0 license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Pipy is listed as an alternative to Envoy. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.