Skip to main content

DigitalOcean Functions

Runtime Platform · FaaS

On-demand functions in production namespaces or as components of managed App Platform applications.

DigitalOcean Functions runs event-driven code without managing servers. Developers can deploy functions to production namespaces through the CLI or include them as components of managed App Platform applications. HTTP invocation and scheduled execution support small APIs, webhooks, and automation, while the namespace and App Platform paths have different deployment workflows.
Best for

APIs, webhooks, scheduled jobs, and event-driven code for developers who want a relatively simple serverless service inside the DigitalOcean ecosystem.

Watch out for

Functions has a smaller runtime and integration ecosystem than the major hyperscalers, and namespace-wide concurrency and invocation-rate limits are comparatively restrictive.

Workloads
  • APIs
  • Backend Services
  • Background Workers
  • Scheduled Jobs
Services
  • Functions
Delivery
  • Managed

Development & Execution

Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.

Runtimes

  • Node.js

Languages

  • Go
  • JavaScript
  • PHP
  • Python
  • TypeScript

Frameworks

  • Express.js

Capabilities

  • Compute Autoscaling
  • Scale to Zero

Architecture

  • x64

Deployment & packaging

  • Local Emulator
  • Serverless (Managed Runtime)

Integrations

  • GitHub
  • GitLab

Triggers

  • Scheduled Invocation
  • HTTP Requests
  • Direct Invocation

Pricing

Published pricing structure, representative costs, and material billing factors.

Starting Price
$0.0000185 Compute
Primary Billing
Resource based DigitalOcean Functions Usage
Free Tier
Recurring free allowances
Commitment
Usage-based billing with a 100 millisecond minimum per invocation.

DigitalOcean Functions Usage

Primary Pricing

Functions are billed according to allocated memory and execution duration.

ResourceBilling UnitPrice
Compute Invocation count is not separately pricedper GiB-second beyond the monthly allowance$0.0000185

Free Tier

Each team receives 90,000 GiB-seconds, equivalent to 25 GiB-hours, of Functions compute per month.

  • Compute: 90,000 GiB-seconds per team per month

Billing Commitment

Usage-based billing with a 100 millisecond minimum per invocation.

Infrastructure & Availability

Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.

DigitalOcean Functions namespaces can currently be created in nine numbered DigitalOcean regions. The doctl region-listing output also includes short aliases such as ams, blr, fra, lon, nyc, sfo, sgp, and tor; these refer to the numbered regions rather than additional regions. Functions availability is separate from DigitalOcean's App Platform and broader datacenter footprint.

Execution

  • Single Region

Deployment scope

  • Regional

Geographic availability

North America
3
Europe
3
Asia Pacific
3

Infrastructure providers

  • DigitalOcean

Available regions

LocationAreaRegion ID
New York DigitalOcean Functions namespace region; short alias nyc is also accepted.North Americanyc1
San Francisco DigitalOcean Functions namespace region; short alias sfo is also accepted.North Americasfo3
Toronto DigitalOcean Functions namespace region; short alias tor is also accepted.North Americator1
Amsterdam DigitalOcean Functions namespace region; short alias ams is also accepted.Europeams3
Frankfurt DigitalOcean Functions namespace region; short alias fra is also accepted.Europefra1
London DigitalOcean Functions namespace region; short alias lon is also accepted.Europelon1
Bangalore DigitalOcean Functions namespace region; short alias blr is also accepted.Asia Pacificblr1
Singapore DigitalOcean Functions namespace region; short alias sgp is also accepted.Asia Pacificsgp1
Sydney DigitalOcean Functions namespace region.Asia Pacificsyd1

Availability reviewed · Availability source

Resource & Execution Limits

Memory

128 MB-1 GB

256 MB default

Concurrency

120

Per namespace

Invocation rate

600/minute

Per namespace

Execution time

15 minutes

Per invocation

Invocation payload

1 MB input / 1 MB result

Per invocation

Built function size

48 MB

Per function

Security & Compliance

Security Controls

Access Control
Revocable namespace access keys and authenticated web functions Functions namespaces
Encryption at Rest
Function code and sensitive parameters DigitalOcean-managed storage
Encryption in Transit
HTTPS/TLS function endpoints DigitalOcean Functions
Network Isolation
Dedicated networking and compute safeguards Functions managed service

Audits & Certifications

SOC Reports
SOC 2 Type II DigitalOcean Functions

FAQ

Is DigitalOcean Functions free?
Yes, within the recurring DigitalOcean Functions allowance. Each team receives 90,000 GiB-seconds of Functions compute per month before additional usage is billed.
How much memory can DigitalOcean Functions use?
DigitalOcean Functions can be configured from 128 MB to 1 GB of memory, with 256 MB as the default.

Explore

Explore more runtime platforms

FaaS Type Functions Service

Alternatives to DigitalOcean Functions

AWS Lambda Functions Azure Functions Google Cloud Run functions