Functions Release Notes

Validated on 5 May 2026

May 2026

5 May

• A remote MCP server is now available for Functions, providing API-based access for AI tools to manage DigitalOcean resources.

March 2026

13 March

• Namespace access keys are now available for Functions. They provide user-specific credentials per namespace, so you can create a key for each user or application and revoke access individually. Keys linked to removed team members are revoked automatically. The legacy shared namespace token is deprecated and will be removed on 3 June 2026. During the migration period, both methods work. After 3 June 2026, legacy tokens will no longer authenticate.

  Visit How to Manage Namespace Access Keys to learn more about managing namespace access keys.

February 2026

12 February

• DigitalOcean Functions now supports functions written in Python 3.12 and Python 3.13.

11 February

• DigitalOcean Functions now supports functions written in PHP 8.3, PHP 8.4, and PHP 8.5.

10 February

• DigitalOcean Functions now supports functions written in Go 1.24 and Go 1.25.

5 February

• DigitalOcean Functions now supports functions written in Node.js 22 and Node.js 24.

January 2026

21 January

• The daft package in the Functions Python 3.11 runtime has been updated from version 0.4.8 to 0.4.10. Visit the Python 3.11 runtime documentation for more information about included packages.

September 2025

2 September

• The Functions Python 3.11 runtime now includes the daft, duckdb, polars, pyiceberg, and pyspark packages. Visit the Python 3.11 runtime documentation for more information.

August 2023

28 August

• 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.

April 2023

26 April

• 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.

September 2022

29 September

• 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.

20 September

• 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.

June 2022

27 June

• To improve security, DigitalOcean no longer accepts TLS 1.0 and TLS 1.1 connections. This includes connections to www.digitalocean.com, cloud.digitalocean.com, and api.digitalocean.com.

May 2022

23 May

• DigitalOcean Functions and functions components in App Platform are now in general availability.

  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.