Quotas, Limitations, and Technical FAQ
Quota Limits
Limits are subject to change as part of public preview. If you’re interested in higher limits, please contact us for assistance.
| All limits can be increased on request | Default Limit |
|---|---|
| Memory (MiB) | 128 |
| App Size (MiB) | 50 |
| Request handler duration (seconds) | 30 |
| Request/response size (MiB) | 10 |
Known Limitations
Spin Limitations
Fermyon Wasm Functions supports Spin CLI v0.6.0 or newer. That being said, there are certain Spin SDK triggers and APIs that are not yet supported on Fermyon Wasm Functions. Please review the table below to see what is supported today on Fermyon Wasm Functions:
| Feature | Supported in Fermyon Wasm Functions? |
|---|---|
| Triggers | |
| HTTP | Supported |
| Redis | Not supported |
| APIs | |
| Outbound HTTP | Supported |
| Configuration Variables | Supported |
| Key Value Storage | Supported |
| SQLite Storage | Not supported |
| Serverless AI | Limited Access |
| Service Chaining | Supported |
| MySQL | Supported |
| PostgreSQL | Supported |
| Outbound Redis | Supported |
| wasi-blobstore | Not supported in Spin |
| wasi-config | Supported (2024-09-27 snapshot) |
| wasi-keyvalue | Supported (2024-10-17 snapshot) |
| wasi-messaging | Not supported in Spin |
| Features | |
| Component dependencies | Supported |
| Extensibility | |
| Custom Triggers | Not supported |
To learn more about what feature support looks like for various programming languages, visit the Spin Language Support Guide.
Other Limitations
- You cannot communicate between Spin applications using local name resolution
- Runtime configuration is not supported at this time
Technical Frequently Asked Questions
- Q: Where is Fermyon Wasm Functions available today?
- Currently Fermyon Wasm Functions are deployed throughout North America and Europe, with larger geographic coverage coming soon.
- Q: How is user data structured in Fermyon Wasm Functions?
- Each user has an associated account (created implicitly with
spin aka login), which serves as the primary entity for managing their resources. An account is linked to zero or more Spin applications, allowing flexibility in how users develop and deploy their workloads.
- Each user has an associated account (created implicitly with
- Q: How are Spin applications managed within a Fermyon Wasm Functions account?
- Each Spin application belongs to a specific account and operates independently, ensuring modularity and security. Applications include metadata, dependencies, and deployment configurations, allowing for scalable and efficient management. If you have additional questions or need further clarification, please reach out to support.
- Q: How long does a login session last with Fermyon Wasm Functions? Will my Spin applications persist after I’ve been logged out?
- Your login session (started by
spin aka loginis persisted until 30 days without activity. To learn more about thespin akaplugin, please visit the reference documentation.
- Your login session (started by
- Q: How do I get help with Fermyon Wasm Functions?
- We’re here to help! Checkout the “How Do I get Help” page in the developer documentation for next steps.
Next Steps
- Learn how to engage with Fermyon to get support