DigitalOcean Functions

Gotchas

• 90,000 GiB-seconds/month free compute

  Free tier is 90,000 GiB-seconds (25 GiB-hours) of compute per account/team per month; beyond it, usage is billed at ~$0.0000185/GiB-s. The number of free invocations is derived (e.g. ~3.6M at 256 MiB / 100ms), so high-memory or long-running functions exhaust it faster.

• Allowance resets monthly, no rollover

  The 90,000 GiB-seconds free allowance is not prorated and does not roll over to the next month; unused compute is lost.

• Payment method required

  A DigitalOcean account with a credit card or other payment method on file is required; a temporary ~$1 pre-authorization may be placed when adding a card.

• Runtime billed in 100ms increments

  Minimum billed runtime per invocation is 100ms; actual runtime is rounded up to the nearest 100ms.

• Memory capped at 1 GB per function

  Per-function memory is limited to 128 MB – 1 GB, defaulting to 256 MB. Cannot be raised beyond 1 GB.

• 15-minute max execution timeout

  Maximum timeout per invocation is 15 minutes, including initialization and execution.

• 600 invocations/minute per namespace

  Each namespace is limited to up to 600 invocations per minute and up to 120 concurrent functions.

• Up to 10 namespaces per account

  You may have up to 10 namespaces, and up to 200 namespace access keys per team/account (including revoked keys).

• 1 MB payload / 48 MB build size limits

  Max input parameter size is 1 MB, max result response size is 1 MB, max built-function size is 48 MB, and remote build time is capped at 2 minutes.

• 3-day log retention, no PG connection pools

  Logs are capped at 256 KB per invocation with up to 3 days retention; activation records (async only) are kept 72 hours. PostgreSQL connection pools are not supported, multi-file functions can't be edited in the control panel, and scheduled triggers are in limited private preview (max 3, not on App Platform).