Show HN: File0 – An easier way to manage files in serverless apps

Original Article ↗ Hacker News Discussion ↗

Product concept & target users

  • File0 is positioned as a very simple file storage layer for “small guys” / indie hackers and serverless apps.
  • Goal: hide S3/R2-style complexity; make file uploads feel as simple as localStorage with minimal setup.
  • Not intended to cover all enterprise use cases; for those, commenters say S3/R2/Backblaze/etc. are more appropriate.

Simplicity vs. S3 complexity

  • Many agree S3’s permission model and feature bloat are overkill and error‑prone for common use cases (public vs private buckets).
  • Others argue you can just ignore advanced features and use S3 as a basic CRUD store, especially with IaC or prebuilt configs.
  • Several note that complexity exists for good reasons (permissions, compliance, org‑level controls) and can’t be fully abstracted away.

Pricing & business model

  • File0 charges flat tiers by storage (e.g., 100GB at a much higher per‑GB price than raw S3/R2/B2) but with no egress fees.
  • Some see value in paying a premium for simplicity; others call the markup high or “unfair,” especially as a thin wrapper around R2.
  • Concern raised that relying on Cloudflare’s current “no egress fees” may be risky if pricing changes at scale.

Security, auth, and trust

  • Authentication: backend uses an environment variable secret; frontend uses per‑file tokens issued by the backend.
  • Some find this model straightforward; others say the marketing downplays the real auth flow and security responsibilities.
  • Multiple commenters highlight missing public information on: regions, legal responsibilities, takedowns, data privacy, and incident response.
  • There is explicit concern about trusting a brand‑new, single‑founder service with critical or sensitive data.

Architecture & dependencies

  • File0 is built on Cloudflare R2 plus Workers; most reliability/HA characteristics derive from R2.
  • It adds features like simple publish/unpublish, per‑file tokens, and basic filtering (e.g., by extension) that aren’t direct S3 APIs.

Docs, DX, and transparency

  • Strong praise for the clean landing page and simple JS/TS API.
  • Equally strong criticism that:
    • Public docs, HTTP API specs, and technical details are missing or hidden behind signup.
    • NPM package is minified and closed, with no README or repo link.
    • Side‑by‑side code comparisons with S3 are seen by some as misleadingly bloated on the AWS side and thinned on the File0 side.

Features, limitations, and scope

  • Currently JS/TS‑only; other languages would require custom wrappers against undocumented HTTP endpoints.
  • Default behavior: overwriting an existing filename replaces the file; some worry about multi‑user collision risks.
  • Lacks many S3‑style features (ACLs, bucket policies, CORS control, multipart uploads, versioning, fine‑grained auth), which is a plus for some and a deal‑breaker for others.
  • Use cases mentioned as good fits: profile pictures, small side projects, early prototypes, “don’t want to think about infra” apps.