hostfunc

Limits and Plans

Per-plan execution limits and platform-wide request guardrails. Limits are enforced at registration time by the control plane and at the edge by the runtime.

Step-by-Step Guide

1.Plan limits

Current per-plan limits (Free / Pro / Team).

  • Functions per workspace: 3 / 2,000 / 20,000
  • Executions per day: 100 / 2M / 20M
  • Wall time per month: 5 min / 500 h / 2,000 h
  • Wall time per execution: 10 s / 120 s / 600 s
  • CPU time per execution: 1 s / 20 s / 120 s
  • Memory: 128 MB / 512 MB / 2 GB
  • Egress per execution: 1 MB / 20 MB / 200 MB
  • Subrequests per execution: 20 / 200 / 2,000
  • Nested call depth: 3 / 20 / 40
  • Secrets per function: 5 / 100 / 400
  • Team members: 1 / 6 / 50

2.Request guardrails

Applied to every /run/:orgSlug/:fnSlug request regardless of plan.

  • Inbound body limit: 1 MiB → 413 payload_too_large when exceeded.
  • HTTP triggers with requireAuth enabled need Authorization: Bearer <workspace API token> (paid plans).
  • Responses include x-hostfunc-exec-id and x-hostfunc-wall-ms headers for tracing.

Related Documentation

Functions
Executions
Security