Plow

github.com/six-ddc/plow Network Tools Open-source projectOpen source

Benchmark HTTP and HTTPS endpoints with Plow, which displays results in a web UI or terminal.

github.com/six-ddc/plow
Plow homepage screenshot

About Plow

Plow is an open-source tool for benchmarking HTTP and HTTPS endpoints. It sends concurrent requests to a URL and records summary statistics, a latency histogram, and percentiles, showing them in the terminal and on a web UI. It can run for a fixed number of requests, a set duration, or until interrupted with Ctrl-C. It supports settings for concurrency, request rate, method, headers, body, timeouts, proxies, and TLS options, and is available via Go, Homebrew, Docker, and release binaries.

Key features

  • Benchmark HTTP and HTTPS URLs with configurable concurrent connections
  • Show summary statistics, latency histogram and percentiles in terminal
  • Serve real-time charts on web UI at configurable listen address
  • Limit tests by request count, duration, or stop with Ctrl-C
  • Set request rate, method, headers, body file, and content type
  • Support TLS client certs, insecure mode, SOCKS5 and HTTP proxies
Best for: Developers who need to benchmark HTTP(S) endpoints from the command line.
Good for
  • Displays results in both terminal and real-time web UI
  • Installable via Go, Homebrew, Docker, or release binaries
  • Supports request-count, duration, and until-interrupted test modes

Plow at a glance

Type
Open-source project
Pricing
Not confirmed. Check the site
Open source
Yes · Source code
Language
English
Last checked
Oct 6, 2026 · Online when checked
Listed
Oct 5, 2026

Plow alternatives

Tools and sites you could use instead, ranked by how closely they match.

All 24 alternatives

Popular in Network Tools

Well-known listings from the same topic.

All 72

Plow FAQ

How can Plow be installed?
With Go using go install github.com/six-ddc/plow@latest, with Homebrew using brew install plow, with Docker using docker run --rm --net=host ghcr.io/six-ddc/plow, or from binaries on the releases assets page.
How is a benchmark run limited or stopped?
Use -n for a fixed number of requests, -d for a test duration such as 10s or 3m, or stop it with Ctrl-C.
Where is the web UI served?
It listens on :18888 by default, which can be changed with the --listen flag.
Is something wrong or out of date?

Tell us and an editor will check it.

Own this website?

Claim the listing and suggest updates yourself. An editor checks every claim first.

Claim this listing