We want to offer a lot of value for free so you can get your idea off the ground, before introducing any infrastructure cost. The intent of the fair use policy is to ensure that we can provide a high quality of service without incurring significant infrastructure costs. The great majority of users will fall well within range of the typical usage guidelines. While we reserve the right to throttle services if usage exceeds the fair use policy, we do not intend to do so as long as we can deliver a high quality of service without significant infrastructure costs.
If you anticipate your project will exceed these guidelines, please contact our support team. We’ll work with you on a plan which scales well.
If you are using the CI/CD service, then your service will automatically deploy from Github or Bitbucket. A concurrent build refers to the number of jobs (build, test, deploy) which 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/mo.
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.
All payments are processed on the last day of each month.
Enterprise customers may pay using ACH transfers which are issued as invoices on the last day of each month. The invoice must be paid within 30 days.
All major credit cards are supported on the Team tier. The enterprise tier also accepts ACH bank transfers.
Yes, standard support is available to all users through email and in-app chat. Premium support is also available which includes an SLA on response time and additional methods of communication. Visit the support
to inquire about available packages.
No, there are no hard limits for the number of monitoring transactions. The legacy Free and Team tiers had limits but those have been deprecated.
No. Deployments via CLI are not limited. Automatic deployments via CI/CD are not limited; 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.
On July 7th we updated the billing model to simplify and reduce the bill. Prior to that update the pricing model included fees for monitoring transactions. In most cases these additional charges did not account for a significant portion of the bill. As such, we’ve eliminated these charges to simplify billing.
If you signed up for an account before July 7th and you had 2 or 3 members in your organization, then your organization account is grandfathered into the legacy Free tier. The legacy free tier includes up to 3 members. If you signed up after July 7th, then you will be on the new Free tier which includes 1 member per organization.
Serverless Framework includes monitoring of AWS API Gateway and AWS Lambda. When the function or API endpoint is invoked it will generate a monitoring transaction which is used by features like the invocation explorer, monitoring and alerting.
A single API request therefore results in a single transaction which includes the request to the API Gateway and AWS Lambda. If the API request only invokes the API Gateway or the lambda function, but not the other, it is still considered a single transaction.