CheckOps home

Tools directory

O

CheckOps

oha

oha is an MIT-licensed Rust HTTP load generator inspired by hey, with a real-time terminal UI showing progress, latency and status codes as the test runs.

Visit website

Latest public signals

Last updated: 11 November 2026 (page expanded from the official README or site).

Visit Website

Introduction

oha (from the Japanese greeting “ohayou”) sends load to a web application and shows a real-time TUI. It is written in Rust, powered by tokio for async I/O and ratatui for the interface, and inspired by rakyll/hey.

The source code is at hatoo/oha on GitHub under the MIT licence, with about 10,700 stars; the most recent commit was on 2 November 2026.

oha is a tiny Rust program that sends load to a web application and shows a real-time terminal UI, inspired by hey. It is built on tokio and ratatui, supports HTTP/1.1 and HTTP/2, and can be installed with cargo, package managers or prebuilt binaries. It reports latency percentiles, a histogram and status code distribution after the run.

Where it fits: on CheckOps, oha is listed alongside alternatives such as hey, bombardier, Vegeta and Plow. When comparing them, check licence and hosting model, how results reach developers (pull requests, CI logs or dashboards), how much tuning is needed to keep noise low, and whether the project or vendor is actively maintained.

Features

  1. Real-time TUI: Live view of requests, latency and status codes.
  2. Rust performance: Async engine built on tokio.
  3. Request count, duration or rate: Flexible run modes.
  4. HTTP/2 support: Test HTTP/2 endpoints; see the README options.
  5. JSON output: Machine-readable summaries.

Pros

  1. Free to use: Open source under MIT.
  2. Maintained: Commits as recent as 2 November 2026.
  3. Community: About 10,700 GitHub stars.

Cons

  1. Single endpoint: No scripted scenarios.
  2. Install via cargo or binaries: Building from source needs Rust tooling.
cargo install oha
oha -z 30s -c 50 https://staging.example.com/

Resources:

Getting started tips: run oha against a production-like test environment, never an unprepared shared system, and agree the target throughput and latency thresholds before the test. Start with a short smoke test, increase load gradually, watch server-side metrics alongside the tool’s client-side numbers, and keep test scripts in version control so results can be repeated and compared between releases.

Pricing

oha is free and open source under the MIT licence.

  1. Developers who like a live view of quick load tests.
  2. Teams replacing hey or ab.
  3. Not a fit for complex workflows.

Conclusion

oha is a fast, friendly hey-style load generator with a helpful live TUI.

As with any tool in this category, the value of oha comes from running it consistently and acting on what it finds, so wire it into an existing workflow rather than treating it as an occasional audit.

Alternatives

Other tools on CheckOps that cover similar ground. Open a page, or compare one with oha side by side.