# pewpew

> pewpew is an open source, self-hosted micro-benchmark CLI from bengadbois, scripted in Go.

- Canonical: https://perf.jmeter.ai/tools/pewpew/
- Official: https://github.com/bengadbois/pewpew
- Source: https://github.com/bengadbois/pewpew
- Vendor: bengadbois
- Category: Micro-benchmark CLI
- License: Open Source — Free; MIT License.
- Deployment: Self-hosted
- Status: Unknown
- Scripting: Go
- Protocols: HTTP, HTTPS
- OS support: Windows, macOS, Linux, BSD
- First released: 2015

- Last verified: 2026-08-12

## What it is
pewpew sends configurable HTTP and HTTPS stress or benchmark workloads to multiple targets and exports raw statistics. Its repository provides cross-platform binaries and records an unknown lifecycle because maintenance evidence is limited.

## Choose it when
- Quick HTTP or protocol micro-benchmarks from a single machine
- Teams that prefer open-source licensing and self-hosting options
- Groups comfortable scripting in Go

## Look elsewhere when
- Full multi-protocol enterprise journeys and rich business-flow reporting
- Teams unwilling to operate generators, results storage, and scaling

## Architecture
pewpew is typically driven as a CLI micro-benchmark with Go. It favors single-host or simple distributed runs rather than enterprise controller grids.

## Pricing
Free; MIT License.

## Compare

## FAQ
### Who is pewpew for?
pewpew is best for developers who need fast HTTP or protocol micro-benchmarks from a terminal. It is open source, so teams can self-host and extend it. Vendor: bengadbois. Deployment model: self-hosted. Free; MIT License. Confirm details against the official site and a short proof-of-concept in your environment.

### How does pewpew differ from Vegeta?
Compared with Vegeta, both sit in micro-benchmark cli, so shortlist on protocols, team skills, and pricing rather than category alone. pewpew lists protocols HTTP, HTTPS; Vegeta lists HTTP, HTTPS. Status is unknown versus active. Use the Test Rig to compare full specs side by side before a proof-of-concept.

### What scripting language and concurrency model does pewpew use?
pewpew uses Go for scripting or scenario definition. Runtime model: CLI-driven request generation with a lightweight concurrency model suited to single-host benchmarks. OS support: Windows, macOS, Linux, BSD. Protocols: HTTP, HTTPS. Match these to how your team already authors tests and which systems you must drive under load.

### What is the cloud or enterprise path for pewpew?
pewpew is primarily self-hosted; teams typically run generators on their own machines, CI runners, or private cloud. Plan for generator capacity, network access to targets, and result storage yourself. As open source, commercial support or hosted siblings may exist separately. Check the official site. Pricing note: Free; MIT License.

### What are known limitations of pewpew?
pewpew limitations to weigh: CLI micro-benchmarks excel at raw HTTP throughput but usually lack enterprise scenario orchestration, rich reporting, and multi-protocol suites; self-hosted tools require you to provision, scale, and observe load generators yourself. Status: unknown. Always validate against your target protocols and scale with a proof-of-concept.

---
Curated by NaveenKumar Namachivayam (QAInsights) · methodology: https://perf.jmeter.ai/about/#methodology · corrections: https://github.com/QAInsights/Performance-Testing-Tools/issues/new?title=Tool%20submission%3A%20&body=Tool%20name%3A%20%0AOfficial%20URL%3A%20%0AWhat%20should%20be%20added%20or%20corrected%3F%20%0A