Home ci 38. functions: Usage & Pricing for Functions

38. functions: Usage & Pricing for Functions

Last updated on Aug 05, 2025

Usage & Pricing for Epycbyte Functions

Epycbyte Functions provide a flexible and cost-effective way to deploy serverless applications. This guide outlines the usage metrics, pricing plans, and limitations for Epycbyte Functions.

Introduction

Epycbyte Functions are available for free with included usage limits. Depending on your plan (Hobby, Pro, or Enterprise), you'll be charged for additional usage according to on-demand costs. The pricing structure varies based on the runtime (Node.js, Python, Ruby, Go, or Edge).

Usage Metrics

Node.js Runtime

  • Billing Metric: GB-Hours (Memory allocated per function in GB multiplied by execution time in hours).
  • Example: A function using 3GB of memory for 1 second would be billed as 3 GB-s. To reach a full GB-Hr, you need 1,200 executions.

Edge Runtime

  • Billing Metric: Execution Units (CPU time per invocation, measured in 50 ms increments).
  • Example: A function using more than 50 ms will be divided into multiple units for billing purposes.

Functions using the Node.js runtime

Functions using the Node.js runtime are measured in GB-hours, which is the memory allocated for each Function in GB, multiplied by the time in hours they were running.

For example, a function configured to use 3GB of memory that executes for 1 second, would be billed at 3 GB-s, requiring 1,200 executions to reach a full GB-Hr.

Functions using the edge runtime

Functions using the edge runtime are measured in the number of execution units, which are the amount of CPU time — or time spent performing calculations — used when a function is invoked.

CPU time does not include idle time spent waiting for data fetching. A function can use up to 50 ms of CPU time per execution unit. If a function uses more than 50 ms, it will be divided into multiple 50 ms units for billing purposes.

Pricing

The following table outlines the price for each resource according to the plan you are on, and the runtime your function is using.

Resource Hobby Included Pro Included Pro Additional
Function Duration (GB-Hours) First 100 GB-Hours First 1,000 GB-Hours $0.18 - 1 GB-Hour
Function Invocations First 100,000 First 1,000,000 $0.60 - 1,000,000 Invocations

Viewing Function Usage

Usage metrics can be found in the Usage tab on your dashboard.

Functions are invoked for every request that is served. You can see the usage for functions using the Node.js runtime on the Serverless Functions section of the Usage tab.

Pricing Plans

Hobby Plan

  • Included Usage:
    • Node.js: First 100 GB-Hours and 100,000 invocations.
    • Edge Runtime: First 500,000 execution units and 100,000 invocations.
  • Additional Usage: Free for Hobby users. Exceeding limits may pause your account unless you upgrade to Pro.

Pro Plan

  • Included Usage:
    • Node.js: First 200 GB-Hours and 1,000,000 invocations.
    • Edge Runtime: First 5,000,000 execution units and 500,000 invocations.
  • Cost: Based on usage beyond included limits. Prices vary by runtime.

Enterprise Plan

  • Custom pricing based on usage and requirements. Contact Epycbyte for details.

Limitations

  • Hobby Plan: Accounts may be paused if usage exceeds limits without an upgrade.
  • Edge Middleware: Not supported for certain frameworks like Next.js (/app) or Next.js (/pages).

Conclusion

Epycbyte Functions offer a scalable and efficient way to build serverless applications. Choose the right plan based on your needs, and monitor usage through the dashboard for better optimization.

For more details, visit Epycbyte Documentation.