automq/automq

Diskless Kafka® on S3. 10x Cost-Effective. No Cross-AZ Traffic Cost. Autoscale in seconds. Single-digit ms latency. Multi-AZ Availability.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 5th, 2026
Created on August 17th, 2023
Open Issues & Pull Requests: 61 (+0)
GitHub issues: Enabled
Number of forks: 768
Total Stargazers: 10,660 (+1)
Total Subscribers: 64 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 17.9 hours
Mean response time: 72.8 days
90th percentile: 177.9 days
Tracked items: 207

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in under an hour, while "enhancement" waits about 4 days. Only 7% of issues opened in the past year have been closed. Three people close 67% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 3
Closed in 7 days: 1
Avg open age: 426 days
Stale 30+ days: 26
Stale 90+ days: 18

Recent activity

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

Top labels

  • enhancement (73)
  • bug (52)
  • Stale (47)
  • good first issue (27)
  • question (5)
  • s3stream (5)
  • documentation (4)
  • wal (3)

Detailed Description

AutoMQ is a diskless Kafka implementation that replaces local storage with object storage on S3.

The project addresses the operational and cost challenges of running traditional Kafka clusters by eliminating the need for local disks on broker nodes. Instead of storing message data locally, AutoMQ streams data directly to S3, which reduces infrastructure costs and simplifies cluster management. The approach decouples storage from compute, allowing brokers to be stateless and enabling rapid scaling without the overhead of managing persistent local storage or rebalancing data across nodes.

Organizations running high-throughput message systems should evaluate AutoMQ if they operate in cloud environments with S3 access and want to reduce total cost of ownership. The tool suits workloads where scaling speed matters and where cross-availability-zone traffic costs are a concern, since data lives in S3 rather than being replicated across broker disks. Teams already committed to Kafka's API and ecosystem can adopt AutoMQ as a drop-in alternative that preserves compatibility while changing the underlying storage model.

The project shows active development with regular commits addressing core functionality and performance optimization. Work spans infrastructure improvements, bug fixes, and feature additions that extend the diskless architecture. The codebase receives ongoing refinement to the S3 integration layer and broker scaling mechanisms. Documentation and playground resources are maintained to support new users evaluating the system.