Quotas, Limitations, and Technical FAQ

Quota Limits

The following are the quota for users based, stratified by the three Subscription Plans offered by Fermyon Cloud:

* Signifies a resource that is not an explicit line item in the Fermyon Cloud Subscription Plan but is eligible for a quota increase for Growth and Enterprise Plan users who can reach out to Fermyon team for assistance.

Starter PlanGrowth PlanEnterprise Plan
Application Quota
Spin application count5100Contact us
Spin application package size (MB)*100100Contact us
Spin application deployments per minute*1010Contact us
Request handler duration (seconds)*3030Contact us
Rate Limiting Quota
Request execution count100,0001,000,000Contact us
Request executions per second*1,0001,000Contact us
Serverless AI inferencing requests per hour*7575Contact us
Serverless AI embedding requests per hour*200200Contact us
Spin application deployments per hour*100100Contact us
Outbound requests per hour per Spin app*500500Contact us
Custom domains *5100Contact us
Custom Fermyon subdomain character count*6262Contact us
Bandwidth egress (GB)550Contact us
Key value store key size (bytes)*255255Contact us
Key value store value size (MB)*11Contact us
Key value maximum keys*1,0241,024Contact us
Key value store count5100Contact us
Key value storage size (GB)12Contact us
SQLite database count11Contact us
SQLite database size (GB)12Contact us
Serverless AI
Token count per request (response only)*1,0241,024Contact us
Region count11Contact us

Note: The above quota numbers are per month and are spread across all apps for a single Cloud account.

Known Limitations

Fermyon Cloud Limitations

  • A custom Fermyon subdomain must be unique
  • A user can execute a maximum of 3,000 requests per hour toward the Cloud API. This includes API requests from the CLI (spin) and navigating the Fermyon Cloud website.
  • The device and browser token lifetime for Fermyon Cloud Dashboard authentication is 7 days
  • A Spin application can have a maximum of 1 key value store

Custom Domains Limitations

Additional records for custom domains are not supported on Fermyon Cloud at this time. This means any additional records (such as TXT or MX) that you have already set through your registrar will become inactive once top-level (apex) domain delegation to Fermyon Cloud is completed. Updating your domain’s nameserver records will cause any additional records you’ve set through your registrar to no longer take effect e.g. TXT or MX records for services like Google Workspace. If you need to assign your Spin application to an apex domain (example.com rather than a subdomain of the apex domain app.example.com) and you also need to set additional DNS records associated with that domain, please share this feedback here. In the meantime, please consider delegating a subdomain or using a Fermyon custom subdomain for your Spin application instead.

Spin Limitations

Fermyon Cloud 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 Cloud. Please review the table below to see what is supported today on Fermyon Cloud:

FeatureSDK Supported?
RedisNot supported
Outbound HTTPSupported
Configuration VariablesSupported
Key Value StorageSupported (only default store)
SQLite StorageSupported
Serverless AISupported
Service ChainingNot supported
Outbound RedisSupported
Custom TriggersNot supported

To learn more about what feature support looks like for various programming languages, visit the Spin Language Support Guide.

Other Limitations

Technical Frequently Asked Questions

  • Why do I see mixed replies from my service during an upgrade?

    • When doing an upgrade of an application, there is a gradual roll-out happening. This means that requests will hit both the existing and new modules, as the upgrade completes. You will see a pattern like the one below, showing the body reply from an HTTP request:
  • Can I export data from my SQLite Database? At this time, Fermyon Cloud does not have a data export feature. We’d love to hear your thoughts on what an ideal experience would look like at github.com/fermyon/feedback

  • If I upgrade my Spin application, can I still access the same instance of my SQLite Database? Yes, as long as you haven’t deleted your database, the instance will be running and stateful.

  • If I delete and redeploy my Spin application, can I still access the same instance of my SQLite Database? Yes, Fermyon Cloud uses abstract labels and links to enable seamless database sharing and management among Spin applications.

11:08:13 : Hello from Rust
11:08:18 : Hello from Rust - updated
11:08:19 : Hello from Rust
11:08:23 : Hello from Rust - updated
11:08:24 : Bad Gateway
11:08:26 : Hello from Rust - updated
11:08:27 : Bad Gateway
11:08:29 : Hello from Rust - updated
  • Q: It’s been over 72 hours and my custom domain hasn’t successfully verified, now what?

    • If you’re a Growth or Enterprise plan user, please reach out to support@fermyon.com. Otherwise, please go to Discord’s #cloud channel for assistance.
  • Q: How do I add a new record?

    • At this time, you can only add a maximum of 1 custom domain to your Spin application. We do not support additional records at this time. To file a feedback request, please visit github.com/fermyon/feedback.
  • Can I configure external DNS for my custom domain on Fermyon Cloud?

    • Fermyon Cloud only supports Fermyon DNS at this time for custom domains. To file a feedback request, please visit github.com/fermyon/feedback.
  • Unable to redeploy an app on Fermyon Cloud?

    • If spin deploy fails with the error No channel with app_id xxxx and name spin-deploy, but the app works locally (via spin build --up), please delete the app from your Fermyon Cloud dashboard and try again.
  • How does Fermyon Serverless AI compare to OpenAI? In what situations am I better off using Fermyon Serverless AI?

    • With Fermyon Serverless AI, you don’t need to be worried about vendor lock-in. With Fermyon Serverless AI you can run your inferencing workloads locally with Spin or on your infrastructure of choice with Spin install. In fact, Fermyon Serverless AI is built using open source models that can be used completely outside the context of Spin in case you decide to host your own infrastructure end to end.
  • Which specific model(s) is Fermyon Serverless AI using for inferencing? [i.e. 7B, 13B, 70B] Why was this model chosen?

    • Fermyon Serverless AI is using the 13B model for inferencing, both for llama2-chat and codellama-instruct, as it strikes an excellent balance of performance and accuracy. If you’re interested in another model, please share this feedback at github.com/fermyon/feedback.
  • How do I choose which model I’m using?

    • llama2-chat is trained for chat use cases, although it can be used for general language model tasks as well. code llama is meant for generating code based on instructions. However, these are just high-level guideposts. Please visit Meta AI’s documentation for more specific instructions and to learn more about the tradeoffs between llama2 and Code Llama.
  • Do you support Fine Tuning? Bring your own Model? Any models other than LLaMa2 and CodeLlama? Vector Databases?

    • At this time, we do not support Fine Tuning or bringing your own model. Fermyon Serverless AI supports llama2 and CodeLlama. If you’re interested in another model, please share that feedback with our team by raising an issue here. Vector databases, backed by our SQLite Database.
  • I read somewhere that I’ll receive data about my AI inferencing usage — where can I find that data? Where can I find a reference as to the definition(s) of each of those data elements?

    • In the request response body, you will see the number of prompt tokens and the number of generated tokens for inferencing requests. For embedding requests, you’ll be presented with the number of prompt tokens.
  • What programming languages / SDKs can I use to invoke Serverless AI?

    • Please visit the API Guide for this information.

Next Steps

  • Learn how to engage with Fermyon to get support