Skip to main content

Rate Limits & Fair Use

Cruma.io is built by a small team with limited resources. There is no formal SLA; we will do our best to keep tunnels responsive and reliable. Fair-use limits protect shared capacity.

What to expect​

  • Throughput/latency: Best-effort. Typical dev workloads (web apps/APIs) should feel snappy; heavy load tests or bulk transfers may be throttled.
  • Concurrent tunnels/targets: Keep to a small number per beta account.
  • Request/byte volume: We monitor request counts and bandwidth. Sustained high volume may be rate-limited.
  • Burst control: Sudden spikes can be shaped to keep the service healthy for everyone.

Custom domains​

Custom hostnames routed via CNAME follow the same fair-use policies as *.cruma.io hostnames.

Tiers and typical limits​

  • Anonymous: Tight limits on concurrent tunnels, bandwidth, and requests. Intended for quick tests; expect aggressive throttling or short-lived sessions.
  • Registered: Higher allowances than anonymous; suited for sustained dev use, moderate bandwidth, and a handful of tunnels/targets.
  • Subscribed (Basic/Pro): Highest allowances and more headroom on concurrency and throughput. Exact limits may evolve; the goal is to support heavier workloads reliably.

Bandwidth per TCP stream (caller ↔ target):

  • Anonymous: ~1 MB/s per stream
  • Registered: ~5 MB/s per stream
  • Subscribed: ~10 MB/s per stream

Agent and tunnel connection limits​

We plan to enforce limits on how many agents can connect to a single tunnel, and on the number of concurrent agents per user. These limits are being refined and will be better defined after the beta period.