Console pricing update

JayJanuary 23, 2025

Starting Feb 1, we’ll be rolling out a new pricing model for the Console. Currently the pricing is based on the number of times the Lambda functions in your apps are invoked. Moving forward, it’ll be based on the number of active resources in your apps.

Why the change?

When SST was first released, there was a big focus on serverless and Lambda functions. The Issues feature was also the focal point of the Console. So it made sense to tie the pricing to the number of Lambda function invocations in your apps.

Over the last few months, we added the ability to Autodeploy your apps. And added broader support for container services. So a Lambda specific metric doesn’t really make sense anymore.

We think the number of active resources will be more representative of your usage.

How does it work?

At the start of every month, or billing cycle, the Console will keep track of the stages that are updated across your workspace, add up the resources in those stages, and apply the following rate.

Resources	Rate per resource
First 2000	$0.086
2000+	$0.032

Free Tier: Workspaces with 350 active resources or fewer.

Examples

So for example, if you have the following number of active resources in your workspace:

Resources	Cost per month
350	You are in the free tier, so you’ll be charged $0.
500	You are above the free tier, so you’ll be charged $0.086 x 500 = $43.
2500	You are in a higher tier, so $0.086 x 2000 + $0.032 x (2500 - 2000) = $188.

The count of the active resources in your workspace resets at the start of every billing cycle.

FAQ

Do I need to use the Console to use SST?

You don’t need the Console to use SST. It compliments the CLI and has some features that help with managing your apps in production.

That said, it is completely free to get started. You can create an account and invite your team, without having to add a credit card.
I’m still trying out the Console. Can I continue using it?

You can continue using the Console as a part of the free tier. If you go over the free tier, you won’t be able to access the production or deployed stages.

However, you can continue to access your personal stages. Just make sure you have sst dev running locally. Otherwise the Console won’t be able to detect that it’s a personal stage.
What is an active resource?

Resources are what SST creates in your cloud provider. This includes the resources created by both SST’s built-in components, like Function, Nextjs, Bucket, and the ones created by any other Terraform/Pulumi provider.

Some components, like Nextjs and StaticSite, create multiple resources. In general, the more complex the component, the more resources it’ll create.

You can see a full list of resources if you go to an app in your Console and navigate to a stage in it.

For some context, the Console is itself a pretty large SST app and it has around 320 resources.

A resource is considered active if the stage it belongs to has been updated during the billing cycle. However, if the only update to a stage was to remove it, the resources in that stage will not be counted as active.
Does this apply to SST v2 and v3 apps?

Yes, it applies to any kind of SST app.
What if I’m on the old plan?

If you are on the old plan, you don’t have to switch and you won’t be automatically switched over either.

You can go to the workspace settings and check out how much you’ll be billed based on both the plans. To switch over, you can cancel your current plan and then subscribe to the new plan.

At some point in the future, we’ll remove the old plan. But there’s no specific timeline for it yet.
Are there any volume pricing options?

Yes you can contact us and we can figure out a pricing plan that works for you.

Learn more about the new pricing in our docs.

If you’ve got any questions about the new pricing, or about the Console in general, feel free to get in touch.