ninenines/cowboy

Small, fast, modern HTTP server for Erlang/OTP.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 8th, 2026
Created on March 9th, 2011
Open Issues & Pull Requests: 65 (+0)
GitHub issues: Enabled
Number of forks: 1,171
Total Stargazers: 7,527 (+0)
Total Subscribers: 285 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.4 hours
Mean response time: 202.3 days
90th percentile: 718.1 days
Tracked items: 55

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 5% of issues opened in the past year have been closed. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 605 days
Stale 30+ days: 15
Stale 90+ days: 13

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Feature request (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Cowboy is a small, fast, and modern HTTP server for Erlang/OTP.

Cowboy addresses the need for a complete HTTP stack within a minimal codebase by optimizing for low latency and low memory usage through the use of binary strings. The server provides routing capabilities that selectively dispatch requests to handlers written in Erlang, and it leverages Ranch for connection management, allowing it to be embedded within other applications. The implementation emphasizes clean, well-tested Erlang code and supports HTTP/2, HTTP/3, WebSocket, and WebTransport protocols.

Cowboy suits developers building high-performance web services in Erlang/OTP environments where resource efficiency and low latency are priorities. It is particularly appropriate for applications requiring embedded HTTP server functionality or those needing to handle multiple concurrent connections with minimal overhead. The project is positioned as production-ready and includes comprehensive documentation available both online and offline, along with example code to guide implementation.

The project maintains active engagement through a Discord server and issues tracker for community support, with commercial support available. Documentation is extensive, including user guides in PDF and HTML formats, function reference man pages, and full Asciidoc sources. The codebase includes examples demonstrating various use cases, and the project provides mechanisms for offline documentation generation and installation.