LogoTrendingDevTools
icon of SST

SST

Open-source framework for defining, developing, and deploying full-stack applications and cloud infrastructure from code in your own account.

Visit Website

Introduction

Best for

SST is best for JavaScript/TypeScript developers and small-to-medium product teams that want to ship a full-stack application while keeping the underlying cloud account and infrastructure under their control. It is a particularly practical fit when a project combines a frontend framework with APIs, functions, containers, storage, databases, scheduled jobs, or third-party infrastructure and the team would rather express that topology in one versioned configuration file than assemble it manually in a provider console. The official documentation demonstrates Next.js, Remix, Astro, SvelteKit, and SolidStart components, as well as AWS containers, Lambda functions, Postgres, S3 buckets, cron jobs, and Stripe products. SST is less of a point-and-click hosted PaaS than a developer-oriented infrastructure and application framework: you still need cloud credentials and pay the underlying providers.

What it does

An SST project starts with sst.config.ts, where components describe both application pieces and the infrastructure they need. A basic Next.js component can set a domain; a Function defines a Lambda handler; Postgres, Bucket, Cron, Cluster, and Service model backend resources. SST creates the required resources in the connected cloud account, with built-in components for AWS and Cloudflare and access to components from more than 150 Pulumi/Terraform providers. That lets a team use SST’s higher-level building blocks while retaining lower-level configuration through component options and transforms.

The day-to-day workflow is centered on the CLI. Install sst locally with npm, pnpm, Bun, or Yarn (or install the CLI globally for non-JavaScript projects), initialize a project, and run sst dev. The dev command watches infrastructure changes, runs functions live, can tunnel to VPC resources, and starts frontend and container services alongside the application. Resource linking avoids hard-coded connection details: link a bucket or database to a service, then read the generated values through SST’s Resource SDK. When the app is ready, sst deploy --stage production creates a named environment; separate stage names can represent development or pull requests.

The official Next.js walkthrough shows a concrete path: initialize SST in a create-next-app project, add an S3 bucket, link it to the Next.js component, use a generated pre-signed URL for uploads, and deploy either serverlessly through OpenNext or in a Docker container. The optional Console adds a web dashboard for resources, updates, logs, issue alerts, local logs, and git-push autodeploy. It supports apps deployed to AWS, while the framework itself also documents Cloudflare and other providers. This makes SST suitable for teams that want application code, infrastructure, and environment setup reviewed together, provided they are comfortable owning cloud operations.

Alternatives

  • Pulumi — Pulumi is the broader infrastructure-as-code platform, supporting multiple programming languages and cloud infrastructure; SST is a more application-oriented layer with framework components, resource linking, and an integrated local dev mode.
  • Vercel — Vercel is a hosted cloud platform for building, previewing, and deploying web and AI apps; SST instead provisions resources in your own cloud account and is designed to cover backend infrastructure as well as the frontend.
  • Render — Render is a managed PaaS for deploying apps, APIs, workers, cron jobs, and Postgres from Git; SST uses infrastructure-as-code and provider resources, giving teams more control but more cloud-account responsibility.

Pricing

The SST framework and CLI are open source and free to use; the official repository lists the MIT license. The optional SST Console pricing documentation describes a workspace-based model for active resources: workspaces with 350 active resources or fewer are in the free tier; the first 2,000 resources above that threshold are listed at $0.086 per resource and resources beyond 2,000 at $0.032 per resource. An active resource comes from a stage at least two weeks old that was updated during the month. These Console charges are separate from the cloud-provider costs created by deploying the application. The Console currently supports apps deployed to AWS.

FAQ

1. Is SST a hosted cloud provider? No. SST is a framework for building full-stack apps on your own infrastructure. Its components create resources in your cloud account; the optional Console is a separate web dashboard.

2. Which providers does SST support? The docs state that SST supports more than 150 providers. It has built-in components for AWS and Cloudflare and can use components from Pulumi/Terraform providers, including a documented Vercel example.

3. What does sst dev do? It watches and deploys infrastructure changes, runs functions live, can create a VPC tunnel, and starts frontend and container services in development mode with the infrastructure linked.

4. Can SST deploy Next.js applications? Yes. The official guide documents both a serverless OpenNext deployment and a Docker-container deployment, including an S3 upload example linked to the Next.js app.

5. Do I need the Console to use SST? No. The official FAQ says SST itself is open source and free to use, while the Console is optional and includes a free tier.

ℹ️

Affiliate Disclosure: TrendingDevTools may earn a commission if you sign up through links on this page, at no extra cost to you.

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates