Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

PicoMQ

Durable Streams over HTTP, on object storage

Details

External ID
49421806
Source
HN
Company
—
Product
PicoMQ
Website domain
picomq.com
Launched
Aug. 24, 2026
Cohort
—
Upvotes
159
Upvotes percentile
0.9583333333333334
Tags
—
Fetched at
Sept. 10, 2026, 5:32 a.m.
Updated at
Sept. 10, 2026, 5:32 a.m.

Description

PicoMQ is a Rust server for Durable Streams, built on Object Store. Cheap, URL-addressable, granular streams (create/append/read/long-poll/SSE), with Pico Protocol or Durable Streams Protocol as the facade.S3Stream is the stream storage primitive, used in AutoMQ, shipped as a Rust library. Coordination is a command log in Postgres.

Enrichment

Theme
database infrastructure and developer tools
Vertical
Horizontal
Function
Data infrastructure
Audience
Developer
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
message streaming over http and object storage
Manually corrected
False

Could you build this?

No Implementing a durable streaming engine directly on object storage requires world-class distributed systems and low-latency storage primitives engineering.

What it would actually take: Requires building an asynchronous I/O engine in Rust (using Tokio) that abstracts append-only commit logs directly over S3 multipart uploads. It demands implementing distributed lease management/consensus for partition ownership, sophisticated read-ahead and write-back caching to mask object store latency, and zero-disk garbage collection protocols.

Discussion

20 comments analyzed.

Competitors mentioned: Apache Kafka, AWS Kinesis, AutoMQ, WarpStream, S2/S2-lite

Concerns raised: Cold-start latency for WAL recovery during rapid scaling to zero, Lacks batching, caching, and low-latency benefits of fully serverless systems, Not suitable for very high-scale traffic (GBs/sec+) or ultra-low latency (microseconds) use cases, Limited project maintenance and developer attention, Durability ACK latency higher than systems with local consensus (vs S3-dependent)

Feature requests: Disk/EBS-staged WAL for lower-latency durability ACKs, GCP deployment example with Rapid Bucket support, Kafka wire protocol support with restrictions (single partition, no transactions), FAQ section clarifying when PicoMQ is not suitable replacement for Kafka

Competitors

Other products that read as similar to this one — 50 launches clear the similarity bar, closest 8 shown.

Attention rank: #2 of 51 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 296 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a data infrastructure tool for Media & entertainment yet.