FAQ

Ramo owns the fiber end to end, so a read costs approximately nothing at the margin — there is no transit bill to pass through. Hyperscalers resell transit and meter it at $87–90 per TB. This is the same zero-egress economics that worked for the web's small objects, extended to the world's datasets.

No. Reads are uncapped and bounded by your connection, not a meter. For comparison: Wasabi's free egress carries a fair-use cap — reads above your stored volume can limit or suspend service — and B2 is free up to 3× stored data, then $0.01/GB. Ramo has no read cap.

A 100 Gbps floor, written into signed customer contracts today — line rate is the design target; the floor is what we sign. For scale: that floor moves 100 PB in 93 days. The same job takes ~93 days at S3's best-effort ~100 Gbps and ~370 days under Azure's ~25 Gbps default account ingress cap.

Two US regions today — SMF (US-West) and IAD (US-East) — joined by a 400 Gbps trunk. Expansion is pod-based: Ramo pods fit a standard colocation footprint and plug into existing PoPs and carrier hotels, so new regions need rack space, power, and 400G ports, not a greenfield buildout.

Eleven nines (99.999999999%) durability, erasure-coded. Storage runs on bare metal Ramo owns and operates — no hypervisor, no shared fabric.

128 PB is live in production. Customers store petabyte datasets on Ramo and sell access to frontier AI labs — Forbes AI 50 names among them — which pull training data straight off the backbone into whichever cloud their GPUs are in.

Small hot objects at the edge. Edge stores like R2 are cache-optimized for KB–MB web objects served globally; discount tiers like Wasabi and B2 are built for backup and archive. Ramo's design center is TB–PB corpora read sequentially at line rate — feeding training runs, not serving thumbnails.