Quotas and limits

Keep these limitations in mind when designing your Spin applications. You can also refer to the FAQ section to learn more about Akamai Functions.

Quota app limits

Limits are subject to change as part of public preview. If you’re interested in higher limits, please contact your Akamai representative for assistance.

DescriptionDefault limit
Memory (RAM allocated per function execution)128 MiB
App Size50 MiB
Request handler duration30 seconds
Request/response size10 MiB

Functions KV quota limits

DescriptionDefault limit
KV Storage (across all store instances)2 GB
Requests supported per app1,000 RPS
Maximum value size1 MB
Maximum key size8 KB

Spin limits

Akamai Functions supports Spin CLI v0.6.0 or newer. Some Spin SDK triggers and APIs are not yet supported on Akamai Functions.

To view the feature support for various programming languages, visit the Spin Language Support Guide.

Spin featureAkamai Functions support
Triggers
HTTPSupported
RedisNot supported
APIs
Outbound HTTPSupported
Configuration VariablesSupported
Key Value StorageSupported
SQLite StorageNot supported
Serverless AILimited Access
Service ChainingSupported
MySQLSupported
PostgreSQLSupported
Outbound RedisSupported
wasi-blobstoreNot supported in Spin, Not supported in Akamai Functions
wasi-configSupported (2024-09-27 snapshot)
wasi-keyvaluewasi:keyvalue/store and wasi:keyvalue/batch interfaces supported (2024-10-17 snapshot)
wasi-messagingNot supported in Spin, Not supported in Akamai Functions
Features
Component dependenciesSupported
Extensibility
Custom TriggersNot supported

Other limits

You cannot use local hostnames such as localhost or short service names, as you might in Docker Compose or Kubernetes, to communicate between Spin applications. To call another Spin application, use its full public URL instead, for example,https://<app-id>.fwf.app.

Runtime configuration is not supported at this time.

Support for Cron jobs and the ability to Schedule tasks with cron jobs in Spin is currently in Tech Preview.