Can’t find any answer for your question? Log into Serverless Dashboard and ask us in the support widget.
Starting in 2024, the Serverless Framework CLI remains free for most users. However, all organizations that earned over $2M in their last fiscal year must purchase a Serverless Subscription which includes a license to use Serverless Framework V.4 and beyond.
You can purchase a Serverless Subscription via Credit Card or the AWS Marketplace. To use either checkout option, go to the Serverless Framework Dashboard. You can also go to our AWS Marketplace listing to simply add a Serverless Subscription to your AWS bill.
Small businesses slightly above the revenue limit or Non-profits qualify for significant discounts via the Small Business Discount (read this F.A.Q. for more info). Additional savings are available through an Annual Contract, billed monthly.
You do not have to buy a License for Serverless Framework V.3 and less. V.3 will continue to receive essential security and bug fixes throughout 2024.
Don't hesitate to reach out to us if you have questions at [email protected]
If you're using the Serverless Framework CLI and meet the criteria mentioned in the "Do I have to pay for a License..." F.A.Q., obtaining a License is straightforward. Just purchase a Serverless Subscription and make sure to toggle the "Serverless Framework V.4 License" option in the "Plan" section during checkout. This process is managed on the Billing page of the Serverless Framework Dashboard: https://app.serverless.com/settings/billing.
The cost of the Serverless Framework CLI License is included in your Serverless Subscription and paid for with Credits. By activating the "License" option, the Service Instances you've utilized through the CLI will be documented in the "Usage" section. Although CLI Service Instances are always monitored, turning on this option ensures their inclusion in your monthly usage calculation, which determines the cost of your License.
A Service Instance in the Serverless Framework is defined by a specific combination of "service", "stage", and "region" parameters in your serverless.yml file, essentially representing a unique deployment in a particular stage and region. Think of it as a distinct AWS CloudFormation stack managed by the Serverless Framework.
Fees for Service Instances apply under two conditions: if they're used with Serverless Framework V.4 through any CLI command or if they're published to the Serverless Framework Dashboard, regardless of the Framework version. Service Instances will incur charges only if their cost exceeds the free tier limit and they exist for more than 5 days. This policy is designed to exempt temporary preview Service Instances from fees, supporting teams in deploying short-term test environments without additional costs.
Service Instances can be paid for using Credits. Whether you're utilizing Serverless Framework V.4 or the Dashboard, you're charged only once for each Service Instance. This approach streamlines the cost associated with deploying and managing your cloud resources. It's important to note that individual functions (such as AWS Lambda functions) or standalone cloud resources do not qualify as Service Instances and are therefore not subject to these specific fees.
On the Serverless Framework Dashboard, navigate to the Settings/Billing page to find the "Usage" section, which displays all active Service Instances. Service Instances used in Serverless Framework Dashboard are always shown in here. But by enabling the "Serverless Framework V.4 License" switch during checkout, V.4 Service Instances will also appear in this usage data. CLI Service Instances are always monitored, but turning on this option ensures their inclusion in your monthly usage calculation, which determines the cost of your License.
Should you remove a Service Instance within 5 days of activation, the "Usage" section will immediately update to reflect this change. For billing purposes, at the end of your 30-day billing cycle, only Service Instances that were active for more than 5 days are counted towards your usage. If you terminate a Service Instance within the billing period after it has been active for over 5 days, it will be included in your usage calculations and deducted from your Credits.
A Service Instance needs to be deployed across 5 days; i.e. time between first deployment and last removal is 5 or more days, to count against your Credits. If you deploy a Service Instance and remove it permanently within 5 days, it will not affect your Credits.
No. When a Service Instance is used with the Serverless Framework CLI and Dashboard it is only tracked as 1 Credit used. In other words, you pay once and you get both Serverless Framework V.4 and Serverless Framework Dashboard.
We have an Service Instance tracking algorithm that ensures Service Instances are not double-counted, as well as removes Service Instances from billing if they are less than 5 days old, across either Serverless Framework V.4 and Serverless Framework Dashboard.
Credits are monthly credit limits, which means they do not last longer than the current month. In other words, they do not roll over.
Checkout via Credit Card and AWS Marketplace are both available. The AWS Marketplace option is great if you want to add your Serverless Subscription to your AWS bill.
The Serverless Framework Dashboard Billing page is a great place to start when considering both checkout options. Additionally, you can go directly to our listing in the AWS Marketplace.
If you need to create an Annual Subscription via AWS Marketplace, you must create an AWS Marketplace Private Offer. To do this, start in the Serverless Framework Dashboard. Create an Org, go to the Settings > Billing Page, enter the Credits you need, and check the Annual Subscription toggle to see the Private Offer option appear below. Click that button and we will follow up with you shortly with the Private Offer (typically 10 minutes to a couple of hours since we must do this manually). Please note, the Private Offer will be sent to the Owner's email your Serverless Framework Dashboard Org.
If you need to create an Annual Subscription via AWS Marketplace, you must create an AWS Marketplace Private Offer.
Start in the Serverless Framework Dashboard. Create an Org, go to the Settings > Billing Page, enter the Credits you need, and check the Annual Subscription toggle to see the Private Offer option appear below. Click that button and we will follow up with you shortly with the Private Offer (typically 10 minutes to a couple of hours since we must do this manually). Please note, the Private Offer will be sent to the Owner's email your Serverless Framework Dashboard Org.
No. There are no fees for Team Members in Serverless Framework CLI or the Dashboard. You can invite as many people as you'd like to your Serverless Framework Organization (managed in the Dashboard), for no additional cost.
We offer more discounts than most. Here's a list of them:
You can automatically sign up for all of these options in the Serverless Framework Dashboard. If you have any issues, please reach out to us at [email protected]
We offer a generous discount to both Small Businesses and Non-Profits. Please note that it is referred to as the "Small Business Discount" in our product and documentation, though it applies to Non-Profits as well. To qualify for the discount your organization must either be a Non-Profit, or a Small Business that meets all of the following criteria:
You can automatically sign up for the Small Business Discount in the Serverless Framework Dashboard. It's based on the honor system and you don't need any approval from us. If you have any issues, please reach out to us at [email protected]
Yes, you can combine any of the packages. For example, if you need 25 Credits, you can use two 15 Credit bundles for a total of 30 Credits. Or, if you need 64 Credits, you can combine one 50 Credit bundle with one 15 Credit bundle for a total of 65 Credits.
Please note, Credits are monthly credit limits. Credits do not roll over to subsequent months.
Yes. Annual and Multi-year Subscriptions are available and include discounted pricing. Further, all Annual and Multi-Year Subscriptions are paid monthly, not up-front.
If you are interested in an Annual Subscription and paying via Credit Card, you can select an Annual Subscription within the Serverless Framework Dashboard. You will be charged monthly, not up-front for the whole year in advance.
If you are interested in an Annual Subscription and paying via AWS Marketplace, please create an AWS Marketplace Private Offer. You can do this via the Serverless Framework Dashboard's Billing Page.
If you are interested in a Multi-year Subscription, you must pay via an AWS Marketplace Private Offer. You can do this via the Serverless Framework Dashboard's Billing Page.
A Trace is a payload which includes the request/response details, detailed spans, errors and performance information for each AWS Lambda invocation. You can access and query Traces in Serverless Dashboard via the Trace Explorer.
A Metric is a single numerical payload which captures the AWS Lambda Invocation duration, invocation, max memory, initialization duration, and custom metrics instrumented in your AWS Lambda handler. You can access metrics in Serverless Dashboard via the Global Metrics View, the Trace Explorer and within the Metrics views of your Serverless Framework Services.
Serverless Dashboard supports Traces & Metrics on any Lambda function, even if it was not deployed using the Serverless Framework, CloudFormation, or Serverless Dashboard.
Credits are now the sole payment method for Traces and Metrics. You can see how many Traces and Metrics a Credit is worth above.
Subscriptions for the Serverless Framework V.4 are managed in Serverless Framework Dashboard, but you are not required to use Serverless Framework Dashboard as a result. As a user of the Serverless Framework V.4 you can either authenticate with the Serverless Framework Dashboard (if you wish to use Dashboard), or you can create and distribute License Keys managed in Serverless Framework Dashboard to your team or business units. In either case, using the Serverless Framework Dashboard for deployments is optional.
You can add additional Credit bundles at any time to regain access to Service Instances, Traces and Metrics, and it will immediately enable you to access these again.
If you are using the AWS Marketplace, then the charges will be processed by AWS on the monthly schedule managed by AWS.
If you are using credit-card based pricing in Serverless Dashboard, then your credit card will be charged at the end of the billing cycle, which is the end of the calendar month. You will be charged for whatever credits you have reserved on your subscription.
To switch your subscription from your credit card to AWS Marketplace, or to a credit card from AWS Marketplace, please reach out to our support within the Serverless Framework Dashboard to help you with this, or contact us at [email protected]
Yes. You can cancel or downgrade at any time. The cancellation will take effect immediately. Please note that you will be auto-charged for any remaining balance immediately upon cancellation.
In the Serverless Framework V.4 CLI, to not have Service Instances tracked, you will need to remove the project from your AWS account via the "serverless remove" command.
In Serverless Framework Dashboard, to not have Service Instances tracked, in the List view which shows all Applications, Services and Instances, you can click on individual Services Instances to view and delete them. Within the view of a Service Instance, at the top right, there are three dots. Click those and select "Delete Instance" from the menu.
In the List view, you can also click the dots on the Service container (which holds its Instances) to delete the Service and all of its Instances.
Be sure to do this within 5 days of the new billing period. However, exceptions will be given at the beginning of this new pricing model. Reach out to us via [email protected] so we can help you.
Serverless Framework Dashboard provides automatic smart trace sampling at high volumes to reduce Credit usage. Dashboard also provides complete control over instrumentation so you can disable Traces, Metrics, or sampling if needed, on a per-Lambda basis.