ZeroFS – A log-structured filesystem for S3: SKIP, 42/100 | Ideas Lab

A filesystem abstraction layer that makes S3 behave like a traditional file system using log-structured storage patterns.

The pain

Developers working with S3 face friction: no true directory hierarchies, eventual consistency issues, high latency for metadata operations, and the mental model mismatch between filesystem semantics and object storage. Teams building on S3 write custom abstraction layers repeatedly.

The gap

Existing solutions (s3fs, goofys) are FUSE-based wrappers that don't solve fundamental S3 limitations. They're slow, unreliable, and don't leverage S3's actual strengths. A purpose-built log-structured approach could optimize for S3's append-friendly nature and batch operations, but no mature product exists.

Build angle

Start by identifying a specific use case where log-structured semantics on S3 create measurable wins: machine learning training pipelines needing fast sequential reads, data lakes with append-heavy workloads, or backup systems. Build a minimal implementation for that use case, measure latency/cost improvements, then expand. Don't try to be a general filesystem replacement initially.

Strengths

Addresses real friction point in S3 workflows that developers encounter repeatedly
Log-structured design aligns with S3's actual performance characteristics (batch operations, eventual consistency)
Could reduce costs by optimizing request patterns and metadata overhead
Technical depth attracts engineering-focused customers who understand the tradeoffs

Risks

Market size unclear, most S3 users accept its model or switch to databases; unclear how many would adopt a new abstraction
Competing against free/open-source FUSE solutions and cloud provider native tools (EBS, EFS)
Requires deep S3 expertise to build correctly; easy to create a slower, buggier version of existing tools
Adoption requires integration into existing workflows and tooling; high switching costs
Performance gains may only materialize for narrow workload types, limiting addressable market
AWS could build this natively, eliminating the business

Fly Labs Method

Is the pain real, is there a gap, is it the right time, can one person build it.

42

Value Equation

Dream outcome and how likely it feels, against the time and effort it costs.

35

One-Person Business

Curiosity pull, identity fit, and a path from free value to paid for a solo creator.

58

Viral Frameworks

Hook strength, shareability, and how cheaply it can be tested.

48

Builder Lens

Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.

52

Five lenses, one composite. How scoring works

The angle

Start by identifying a specific use case where log-structured semantics on S3 create measurable wins: machine learning training pipelines needing fast sequential reads, data lakes with append-heavy workloads, or backup systems. Build a minimal implementation for that use case, measure latency/cost improvements, then expand. Don't try to be a general filesystem replacement initially.

No market research recorded for this idea yet.

SaaS founders lack a platform for finding partners and organizing joint advertising campaigns with bloggers to reduce costs by 5 times while maintaining the same reach

Other

BUILD

85FL score

Founders waste hours daily on repetitive tasks that AI could automate instantly

Founders spend excessive time on routine tasks that AI could complete in minutes, but no simple, purpose-built tool exists to handle them automatically without complex setup.

Other

BUILD

82FL score

Owners of modern Macs can't launch old games due to complex instructions involving emulators and file conversion

Other

BUILD

79FL score

All Other ideas