How does OCI Functions pricing compare to AWS Lambda?

Both charge per invocation and per GB-second of compute time. OCI Functions includes 2 million free invocations and 400,000 GB-seconds per month, comparable to AWS Lambda's 1 million free invocations and 400,000 GB-seconds. Per-invocation and per-GB-second rates are similar, but OCI's advantage is the higher free invocation count and the absence of data transfer charges within the same region. For high-volume workloads, the pricing difference is usually marginal.

What factors most affect OCI Functions costs?

The three biggest cost drivers are invocation count, memory allocation, and execution duration. Memory is the most impactful because it directly multiplies the GB-second calculation — a function running with 1024 MB for 1 second costs twice as much as one running with 512 MB for 1 second. Optimizing execution duration through code performance improvements and right-sizing memory allocation are the most effective cost reduction strategies.

OCI Functions Cost Estimator

ServerlessOCI

Estimate OCI Functions costs based on invocations, memory, and execution duration.

OCI Functions Configuration

Invocations per Month

Memory (MB)

Average Duration (ms)

Include Free Tier (2M invocations + 400K GB-seconds/month)

Raw Output

Output will appear here...

About This Tool

OCI Functions is a serverless compute platform based on the open-source Fn Project that lets you run code without provisioning servers. Pricing is based on function invocations and the compute time measured in GB-seconds (memory allocated multiplied by execution duration). OCI Functions includes a generous free tier of 2 million invocations and 400,000 GB-seconds per month. This cost estimator calculates monthly expenses based on your expected invocation volume, average execution duration, and memory allocation per function, helping you understand when serverless is more economical than always-on compute.

When to Use This Tool

•Estimating monthly costs for an event-driven image processing pipeline that handles 500,000 invocations with 512 MB memory functions
•Comparing the cost of running a lightweight API on OCI Functions versus a small compute instance running continuously
•Projecting costs for a data transformation function triggered by Object Storage events with variable monthly volumes
•Calculating how much of your workload falls within the free tier to determine if OCI Functions costs anything at all

Frequently Asked Questions

How does OCI Functions pricing compare to AWS Lambda?: Both charge per invocation and per GB-second of compute time. OCI Functions includes 2 million free invocations and 400,000 GB-seconds per month, comparable to AWS Lambda's 1 million free invocations and 400,000 GB-seconds. Per-invocation and per-GB-second rates are similar, but OCI's advantage is the higher free invocation count and the absence of data transfer charges within the same region. For high-volume workloads, the pricing difference is usually marginal.
What factors most affect OCI Functions costs?: The three biggest cost drivers are invocation count, memory allocation, and execution duration. Memory is the most impactful because it directly multiplies the GB-second calculation — a function running with 1024 MB for 1 second costs twice as much as one running with 512 MB for 1 second. Optimizing execution duration through code performance improvements and right-sizing memory allocation are the most effective cost reduction strategies.

Related Learning Guides

OCI Cost Optimization Strategies18 min read

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.