Fair Use

Storm Buckets has no free tier and no metered egress bill. Every account pays
for the storage it provisions, or holds a grant on the alpha endpoint, and a
monthly egress allowance comes with that capacity. This page is the whole
fair-use policy: what the allowance is, what happens when you cross it, and
what Storm never meters.

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

The egress allowance

Egress is outbound data: the bytes that leave Storm on GET, HEAD, and LIST
responses, counted across every bucket you own on that endpoint.

Your allowance is 3x your capacity on that endpoint, per calendar month.
Capacity is everything provisioned to you there: paid blocks on montreal-1,
the alpha grant on the alpha endpoint.

Bandwidth is consumed at one endpoint, so allowances are counted at one. If you
hold capacity on both endpoints, each carries its own allowance and they are
not pooled.

The allowance resets on the first of each calendar month (UTC). The dashboard
shows egress used against it on your account and bucket pages.

Crossing the allowance

Running well past the allowance on a sustained basis slows your reads:
downloads take longer, they do not stop, and you are never billed for the
overage. Writes (PUT, POST, DELETE) are untouched. Storm emails you when it
happens. The egress that comes with your capacity is part of what you paid
for.

Nothing is slowed today. The monthly reading exists and the throttle is built,
and it is switched on per endpoint, not yet on either. Until then the dashboard
egress figure is informational. The 3x allowance is written down now so there
are no surprises when it turns on.

Sharing the port

Each endpoint has one network port, shared by everyone on it. Once the
throttle is on and the port nears saturation, every account reading at that
moment gets an equal share of it until the burst passes. Below that point
nobody is slowed. This applies inside your allowance too: it is how one heavy
reader is kept from starving the others.

What Storm never meters

These never count against any allowance and are not billed, on any endpoint:

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

• API operations. GET, PUT, HEAD, LIST, DELETE, and admin calls are not
  metered 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

If one account sustains traffic that degrades service for everyone else on an
endpoint, Storm contacts the account holder first: we email, ask what is
happening, and work out a path, more blocks, 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.

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