Wasmer · Rate Limits

Wasmer Rate Limits

Wasmer does not publish explicit numeric rate limits for the public Registry GraphQL API at registry.wasmer.io/graphql. Practical limits are governed by plan quotas - apps, requests, bandwidth, active CPU hours, provisioned memory, storage, build minutes - enforced per account on Wasmer Edge. The GraphQL endpoint applies standard abuse protection; specific per-account request ceilings are not documented and are not reconciled in this artifact.

Wasmer Rate Limits is the machine-readable rate-limit profile for Wasmer on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests, gigabytes, hours, and minutes.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include WebAssembly, Wasm, Registry, Edge, and Runtime.

5 Limits Throttle: 429
WebAssemblyWasmRegistryEdgeRuntimeRate LimitingQuotasThrottling

Limits

GraphQL Requests account
requests
see provider documentation
No explicit numeric ceiling documented for the public GraphQL endpoint; abuse protection applies.
Edge Requests (Plan Quota) account
requests
100000 (Hobby) / 1000000 (Pro) per month, then metered
Monthly Edge request allotment per plan; overages billed on Pro, capped on Hobby.
Bandwidth (Plan Quota) account
gigabytes
150 (Hobby) / 1000 (Pro) per month, then metered
Monthly Edge bandwidth allotment per plan.
Active CPU Hours (Plan Quota) account
hours
50 (Hobby) / 200 (Pro) per month, then metered
Monthly Edge compute allotment per plan.
Build Minutes (Plan Quota) account
minutes
500 (Hobby) / 5000 (Pro) per month, then metered
Monthly CI/build allotment per plan.

Policies

Plan-Based Quotas
Effective limits are driven by per-plan Edge resource quotas; Pro overages are billed, Hobby is capped.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses on the GraphQL endpoint.

Sources