Codetje docs

Limits

What a request and a package may use. Going over a limit fails the request, and the reason goes to the package's logs.

Per request

Limit When it's reached
Time 30 seconds, including streaming the response 504
Memory 256 MB, shared with the packages it imports The module traps: 500
CPU 1 billion units of fuel, shared with the packages it imports The module traps: 500
Imported packages 4 levels deep, 8 instances in all Refused when it runs
Log lines 16 KiB each The line is cut

Each request gets a fresh instance, so nothing is kept between requests.

Per package

Limit
Module size 64 MiB
Stored source 1 MiB, 256 files
Name 64 characters

Per month

Every organization has a plan with monthly limits, counted for its namespace. The namespace that runs the code pays: for a package's URL, its own namespace, also when anonymous visitors call a public package; for a graph, its owner, for every step in it, including other namespaces' packages. A package you import runs on your quota, not its owner's.

Free plan When it's reached
Runs 10,000 Requests and graph runs get a 429
CPU 1,000,000 compute units (a million fuel each) Requests and graph runs get a 429
Outgoing requests 5,000 Fetches fail, as for an origin that isn't allowed; everything else keeps working
Storage 100 MB of modules and source Publishing a module that doesn't fit gets a 403

Storage isn't monthly: it's every distinct module and source your namespace's versions have, each counted once, so publishing the same bytes again costs nothing. Free space by deleting versions you no longer need, on a version's page in the console or with rt version delete ns/name@version. A version can't be deleted while a tag points at it, another version imports it, or a published graph uses it; move the tag or publish without it first. Its bytes stop counting at once. Source for a version that's already published is always accepted.

A run is one request to a package, one step run by hand, or one graph run, however many steps it has. Requests turned away (401, 404, 429) don't count. CPU and outgoing requests count everything the request and its imported packages used, also when it traps or times out.

The month starts on the day the organization joined its plan, not on the 1st, at 00:00 UTC. A 429 says which limit was reached and when it resets:

HTTP/1.1 429 Too Many Requests
Retry-After: 1209600
Content-Type: application/json

{"error": "acme has used this month's runs limit on the free plan. It resets at 2026-12-14T00:00:00Z. ...", "limit": "runs", "resets_at": "2026-12-14T00:00:00Z"}

A module host gets the same message as plain text, and a scheduled trigger is skipped until the reset. Either way, the package's runner log stream says why, at most once a minute; nothing goes to its stdout or stderr. A request that's already running always finishes, so a namespace can go slightly over a limit.

See what you've used, and what's left, on the console's Usage page, or with rt usage.