nwtgck

piping-server: Stream Data Between Devices Over HTTP

Piping Server pairs an HTTP sender and receiver on the same path to stream data between devices without storing it on the server. It suits command-line workflows and browser-based transfers, and can be self-hosted.

View on GitHub Compare
Stars
3.2k
Forks
168
Stars, last 30 days
+1
Last commit
8 months ago
Contributors
10

Our take

Quietno commits in the last 90 days and no release in a year

Health score

27/100

How it is scored
Activity
19
Community
47
Issues
21
Pull requests
20

+1 stars in the last 30 days

Piping Server is a focused, practical HTTP relay, but its quiet maintenance signals and lack of recent release activity merit review before relying on it as a critical service.

Good fit if

  • You need direct, streaming transfers that work with curl or a browser.
  • You can run the Node.js server or Docker image and want to self-host the relay.
  • MIT licensing suits your project, and you can assess the maintenance gap yourself.

Look elsewhere if

  • You need evidence of active recent development or releases: the measured record shows no commits in the last 90 days and no release in over a year.
  • You require recent issue or pull-request handling: none were recorded as closed or merged in the measured 90-day period.
  • You need the server itself to provide end-to-end encryption; the README points to a separate UI that supports it, rather than describing that as a server feature.
All health signals
Last commit2026-02-02 (8 months ago)
Commits, last 90 days0
Releases, last 12 months0 (latest v1.12.9, 2023-04-08)
Contributors10 (top contributor: 59% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age8 years

Checked on 2026-10-12 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

3,170

Forks

168

Change since Nov 14, 2026: 0 stars·0 forks

Overview

Piping Server connects an HTTP upload to a matching download, so devices can pass data through a shared server without first saving the transfer there. The sender and receiver can connect in either order, and the stream can stay open for ongoing data rather than requiring a completed file.

It is aimed at people who want to move data using common tools such as curl or a browser, without installing a client on each device. Self-hosting is available for teams that want to run the relay themselves; the project also supports browser-based applications built on its HTTP stream.

Key Features

  • Matches POST or PUT uploads to GET requests using the same URL path.
  • Streams data between sender and receiver, including ongoing or unbounded streams.
  • Lets either side connect first and wait for the other.
  • Supports transfers to multiple receivers using a query parameter.
  • Provides command-line usage with curl and a browser UI on public servers.
  • Offers Docker and portable-binary options for self-hosting.
  • Passes selected metadata headers, including content type, length, disposition, and a custom X-Piping header.

Use Cases

  • A developer can pipe command output from one machine to another with curl, without setting up a separate transfer client.
  • A team can stream large or continuously generated data when saving the complete transfer first is impractical.
  • A user can send a file between devices through a browser when command-line tools are unavailable.
  • Application developers can use the HTTP stream as a transport for real-time tools such as chat, screen sharing, or browser-based SSH, as shown in related projects linked by the README.

What you need

Detected in the repository

  • Node.js (from package.json)
  • A Dockerfile, so it can run in a container
  • A test suite and automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Run a local server with Docker:

docker run -p 8080:8080 nwtgck/piping-server

Then send and receive on the same path, for example with curl -T - http://localhost:8080/hello and curl http://localhost:8080/hello. See the README for other setup options and usage details.

Alternatives

  • copyparty: Copyparty provides a persistent file server for browsing and sharing, rather than streaming directly between a sender and receiver without server-side storage.
ProjectLanguageLicenseStarsStatus
piping-serverTypeScriptMIT3.2kQuiet
copypartyPythonMIT46.9kActive

Considerations

The project is marked Quiet in the measured health data: there have been no commits in the last 90 days and no release in over a year. The measured data lists ten contributors and does not flag contributor concentration, but also records no issues closed or pull requests merged in that recent period. Plan to review the code and deployment requirements before depending on it for a critical transfer service.

Running the server requires Node.js, or Docker as an alternative deployment route. The README describes a storageless design, but does not claim that the server encrypts transfer contents; its separate modern UI is the component specifically noted as supporting end-to-end encryption. The repository is MIT-licensed.

Found this useful?

Share it with someone who would like piping-server.

Comparisons