How does DO Functions pricing compare to AWS Lambda?

DO Functions includes a generous free tier (90,000 GB-seconds per month) and bills overages at a rate competitive with Lambda. For low-volume workloads (a webhook receiver, a daily cron) it is often entirely free; for high-volume workloads the difference is small enough that the right choice usually comes down to where the rest of your infrastructure lives.

Can DO Functions access a managed database in the same VPC?

Functions run in DigitalOcean infrastructure and can reach managed databases over the public internet (with database firewall trusted-source rules) or over a private connection if both are in the same region. The private path is preferred for production: lower latency, no egress charges, and no exposure to the public internet.

DO Functions Config Builder

ServerlessDigitalOcean

Build DigitalOcean Functions serverless configurations with packages, triggers, and runtimes.

Last verified: May 2026

DigitalOcean Functions Configuration

Build DigitalOcean Functions serverless configurations with packages, runtimes, triggers, environment variables, and resource limits.

Required Fields

namespacepackages

{
  "namespace": "prod-functions",
  "region": "nyc",
  "packages": [
    {
      "name": "api",
      "functions": [
        {
          "name": "process-webhook",
          "runtime": "nodejs:18",
          "main": "index.main",
          "web": true,
          "timeout": 30000,
          "memory": 256,
          "environment": {
            "DATABASE_URL": "$DATABASE_URL",
            "API_KEY": "$API_KEY"
          },
          "triggers": [
            {
              "name": "scheduled-trigger",
              "sourceType": "scheduler",
              "sourceDetails": {
                "cron": "0 */6 * * *"
              }
            }
          ],
          "limits": {
            "concurrency": 10,
            "logs": 10
          }
        },
        {
          "name": "resize-image",
          "runtime": "python:3.11",
          "main": "handler.main",
          "web": false,
          "timeout": 60000,
          "memory": 512
        }
      ]
    }
  ],
  "environment": {
    "NODE_ENV": "production"
  }
}

Generated Output

Output will appear here...

About This Tool

DigitalOcean Functions is a serverless runtime for short-lived event-driven code — HTTP triggers, scheduled jobs, or invocations from App Platform. The DO Functions Config Builder generates a `project.yml` spec for a Functions namespace including individual function packages, runtime (Node, Python, Go), memory and timeout settings, environment variables, and trigger configuration. Output is `doctl serverless deploy` ready.

Real-World Scenario

Your team has been running a Stripe webhook receiver on a t3.micro EC2 instance with nginx and a small Python service — total cost $9/month and continual maintenance for SSL certs and OS patches. You migrate the same logic to a DO Function with an HTTP trigger. Stripe sends webhooks directly to the function URL; the function processes them and writes to your existing Postgres. New monthly cost: $0, comfortably within the free tier. EC2 instance deprovisioned the same week.

When to Use This Tool

•Defining a small HTTP-triggered function for a webhook receiver that processes payloads and writes to a database.
•Setting up a scheduled function (DO Functions' cron equivalent) for periodic maintenance work without needing a long-running Droplet.
•Migrating an existing AWS Lambda function to DO Functions by translating the runtime, memory, and trigger configuration.
•Organizing a multi-function project where several related functions share environment configuration and deployment.

Pro Tips

TIP

Set the memory parameter realistically. DO Functions allocates CPU proportionally to memory, so a function set to 128 MB gets less CPU than one set to 1024 MB — meaning the cheaper memory setting can paradoxically cost more if the function takes much longer to run.

TIP

Cold starts in DO Functions are typically under a second, but they exist. For latency-sensitive HTTP endpoints, keep one function warm with a low-rate scheduled ping or move to App Platform where instances stay warm.

How It Works Under the Hood

The builder collects the namespace name, region, and a list of function definitions (name, runtime, source path, environment, memory, timeout, web flag for HTTP exposure). It validates the runtime against DO Functions-supported runtimes, the memory against allowed values (128 MB to 4 GB in steps), and generates a `project.yml` spec compatible with `doctl serverless deploy`. Triggers (scheduled, HTTP) are emitted as separate fields per the DO Functions schema.

Frequently Asked Questions

How does DO Functions pricing compare to AWS Lambda?: DO Functions includes a generous free tier (90,000 GB-seconds per month) and bills overages at a rate competitive with Lambda. For low-volume workloads (a webhook receiver, a daily cron) it is often entirely free; for high-volume workloads the difference is small enough that the right choice usually comes down to where the rest of your infrastructure lives.
Can DO Functions access a managed database in the same VPC?: Functions run in DigitalOcean infrastructure and can reach managed databases over the public internet (with database firewall trusted-source rules) or over a private connection if both are in the same region. The private path is preferred for production: lower latency, no egress charges, and no exposure to the public internet.

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.