All Functions API calls now require read-write tokens, even if they are for read-only actions. See the Functions section of the DigitalOcean API reference for more details.
DigitalOcean Functions now supports functions written in Go 1.20, PHP 8.2, and Python 3.11.
Visit the Functions documentation to learn more about which runtimes are available.
DigitalOcean Functions now support a maximum timeout of 15 minutes.
Longer timeouts enable functions to handle more complex and compute-intensive tasks such as video and image processing, data transformation, and report generation.
Visit the Functions documentation to learn more about creating and working with long-running functions.
DigitalOcean Functions now has limited beta access to scheduled triggers.
Scheduled function triggers allow you to set a cron-like schedule for running your function. An optional payload may be included with each invocation. Each function may have multiple triggers with different schedules and payloads.
Visit How to Schedule Functions to learn more about creating and working with scheduled triggers from the command line or control panel interface.
DigitalOcean Functions now has support for multiple namespaces.
Namespaces are a level of isolation and organization for functions. They allow you to isolate functions by project, by environment (production versus development, for example), by region, or by any other grouping that facilitates your development workflow.
Visit the Functions documentation to learn more about creating and working with multiple namespaces.
In order to improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to
Functions are blocks of code that run on demand in response to requests. DigitalOcean Functions let developers execute their code on DigitalOcean without managing compute resources like Droplets or Kubernetes clusters.