One subscription, which includes all features, and offers three tiers for different levels of usage.
Header | Header | Header |
---|---|---|
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Cell | Cell | Cell |
Our free tier, ideal for solo devs seeking monitoring, debugging, CI/CD, secrets & more.
Ideal for teams and production apps doing less than 15 million transactions per month.
Custom packages for teams & apps doing over 15 million transactions per month.
Can’t find any answer for your question?
Ask our customer support
A Concurrent Build refers to the number of jobs (build, test, deploy) which our CI/CD features can run at the same time. The free tier includes 1 Concurrent Build and the team tier includes 2 Concurrent Builds. This is enough for the majority of use cases; however, if you have a high volume of CI/CD deployments, you can buy more Concurrent Builds for $25/month.
A Monitoring Transaction is a data record containing performance information about a single serverless compute execution (e.g. AWS Lambda invocation, AWS Fargate). Monitoring Transactions power our charts, alerts, and Explorer.
The trigger or event source of the serverless compute execution is included in a single Monitoring Transaction. For example, if an AWS API Gateway request triggers an AWS Lambda invocation, that would count as 1 Monitoring Transaction, not 2.
Automatic deployments with CI/CD are included on both the Free and Team tiers; however, the Free tier is limited to deployments from personal user accounts. Deployments from organization accounts are available on the Team tier.
Yes. Just hit the “cancel” button on the dashboard at any time and you’ll be cancelled immediately.
Yes, we offer premium support packages for Serverless Framework and general serverless architecture help. A Subscription is required in order to purchase Support. Please check out the Support page for more details.
Yes, support plans can be cancelled but they are not refundable. Your plan will automatically cancel at the end of the billing cycle. For monthly subscriptions that will be the end of the month, for annual subscriptions that will be on the annual anniversary. Until the end of that billing period you will continue to have access to premium support.
For the "Team" tier, all payments are processed on the last day of each month. For the "Enterprise" plan, payments may be made in advance depending on your individual contract, as well as after each month if any overages apply. Please see your "Enterprise" subscription for more details.
The fees are calculated based on usage for the last billing period. The fees for monitoring transactions are calculated by the total number of monitoring transactions for the billing cycle. Member and CI/CD Concurrent Build usage is determined by the high water mark. The high water mark is reset at the end of each billing cycle. For example, if you have 10 members in the middle of the month, but you remove 5 of them by the end of the month, then you will be charged for 10 members as that is the high water mark. Since you have 5 members at the start of the next billing cycle you will only be charged for 5 Members at the end of the following billing cycle if you do not add members at any point in that billing cycle.
Currently we do not support proration if you chose to cancel your account. Therefore you will be charged for the full billing cycle for Members and CI/CD Concurrent Builds. Please contact support for a partial refund.
All major credit cards are supported on the Team tier. The Enterprise tier also accepts ACH bank transfers.
No. Deployments via the Serverless Framework CLI are unlimited. Also, automatic deployments via CI/CD are unlimited; however, each deployment is limited to 30 mins.
Yes. In each billing cycle the number of users is determined by the high water mark for the number of users. For example, if you start the billing cycle with 4 users, then add 1, but remove them before the end of the billing cycle, you will be charged for 5 users.
Credit card payments are automatically charged at the end of the billing cycle. The credit card transaction will be retried periodically for 14 days during the grace period. If the credit card payments continue to fail, then the organization plan will be cancelled.
ACH transactions must be completed within 30 days of issuing the invoice. If the invoice is not paid within the 30 day period, then the organization plan will be cancelled.
Once an account is in a cancelled state the organization will only have access to the Free tier features. CI/CD concurrent builds will be downgraded, monitoring transactions may be throttled, and only the organization owner will be permitted to deploy with the dashboard.