Frameloft

You pay for bytes that reached a player.

No per-seat fee, no encoding minutes, no charge for origin pulls. Delivered traffic is metered per session, which is the same number your own logs count.

Sandbox

€0 / month

One project, for trying the API.

  • 100 GB delivered
  • 1 asset group
  • Shared edges
  • Email support
Request access

Studio

€19 / month

Most early-access projects land here.

  • 2 TB delivered, then €4 / TB
  • Unlimited assets
  • Session API with server keys
  • Per-asset traffic breakdown
Request access

Scale

€89 / month

Apps with a daily audience.

  • 12 TB delivered, then €3 / TB
  • Raised concurrency ceilings
  • Standby origin failover
  • Incident contact on request
Request access

The fine print, in plain words

What counts as delivered traffic

Bytes our edges hand to a player, segments and manifests together. A range request counts only the range. Retries after a 503 do not count, because nothing was sent.

What we never bill

Origin pulls, cache fills between our own regions, failed sessions, and anything a crawler asked for and got a 400 for.

Billing

Monthly, in euros, invoiced after the period. Overage is measured per started TB. During early access there is no contract term — stop any month and the assets stay reachable for 30 days so you can move them.

Limits

Plans differ only in included traffic and concurrency ceilings; the API is the same on all of them. Published limits are in the docs.