Fair Use

Storm Buckets has no free tier and no metered egress bill. Every account pays
for the storage it provisions, and a monthly egress allowance comes with that
storage. This page is the whole fair-use policy: what the allowance is, what
happens when you cross it, and what stays free no matter what.

Nothing here cuts your traffic silently. The allowance is written down, the
dashboard shows where you stand, and a genuine anomaly gets you an email, not
a surprise suspension.

The egress allowance

Egress is outbound data: the bytes that leave Storm on GET, HEAD, and LIST
responses, counted across every bucket your account owns.

Your allowance is 3x your total storage capacity, per calendar month.
Capacity is everything provisioned to the account: paid blocks plus any
Founding Alpha grant.

The allowance resets on the first of each calendar month (UTC). The dashboard
shows egress used against it on your account and bucket pages, so there is no
guessing where you are.

Crossing the allowance

Crossing the allowance throttles your read throughput: downloads slow
down, they do not stop, and you are never billed for the overage. Writes
(PUT, POST, DELETE) are untouched. Your data stays safe and reachable; a heavy
month just reads slower until the reset.

There is no hard cutoff, no 429 wall, and no overage invoice. Block pricing
means you pay for the capacity Storm allocated to you and nothing else, and
the egress that comes with that capacity is part of it, not a separate meter.

During alpha, egress is uncapped. The throttle is not switched on yet, so
the dashboard egress figure is informational for now. The 3x allowance is how
egress works once enforcement turns on; it is documented now so there are no
surprises later.

What's always free

These never count against any allowance and never cost anything, during alpha
or after:

• Ingress. Uploading into Storm Buckets is free, with no cap.

• API operations. GET, PUT, HEAD, LIST, DELETE, and admin calls are free
  regardless of count. Your bill never moves with your request count.

• Buckets and keys. Create as many as your project needs. Storm does not
  charge by bucket or key count.

When a workload looks off

The alpha runs on a single shared node. If one account sustains heavy traffic
that degrades service for everyone else, Storm contacts the account holder
first: we email, ask what is happening, and work out a path, a larger block, a
private cluster, whatever fits the workload. Suspension is a last resort and
only after we have talked. The allowance is published precisely so there is no
hidden throttle sitting behind it.

Changes to this policy

If the egress allowance is ever tightened, existing accounts get at least 30
days notice by email before it takes effect. If it is loosened, the change
applies immediately and we note it in the next Dispatch.

Founding Alpha accounts get all features unlocked during alpha and the
standard 3x allowance on their grant. The grant persists past alpha as a
permanent allocation; the post-alpha terms are in the alpha invitation.

Pricing detail lives on the Pricing page.
Questions: contact@stormdevelopments.ca