SST

SST is an MIT-licensed infrastructure as code framework for developers deploying full-stack apps to their own AWS or Cloudflare account, written in TypeScript.

SST deploys an application and every cloud resource it needs from one TypeScript file, sst.config.ts. A site, its API, a database, an email sender and DNS records are declared side by side and shipped together. Anomaly Innovations builds SST, launched it in 2021, and also works on opencode, OpenNext and OpenAuth. The framework is open source under the MIT license and runs on Pulumi and Terraform providers underneath. Components are the core of SST. Built-in ones for AWS and Cloudflare cover Next.js, Remix and Astro sites, containers, Lambda functions, Postgres databases, S3 buckets and cron jobs, with defaults that can be configured completely. Components from any Pulumi or Terraform provider extend that, so a Vercel frontend or a PlanetScale database can sit in the same config. Resource linking hands one component to another, letting a container use a bucket without hardcoded names. The sst dev command starts the frontend and container apps together, sst diff previews a change, and Policy Packs block a deploy that breaks a mandatory rule. SST suits developers and small product teams who deploy to their own AWS or Cloudflare account and want infrastructure in the same language as the app. It fits monorepos that hold a frontend, a backend and some functions. Teams with resources created earlier can import them, so SST manages them from then on. The framework installs from npm, and the SST Console is an optional hosted service a team adds when it wants monitoring and deploys from git. Work with SST usually starts with an edit to sst.config.ts, a look at sst diff and a deploy from the terminal. A team hosting a Next.js site on AWS keeps the site, its container API and its email sender in one file, with its DNS on Cloudflare. In the Console, Logs and Issues show what failed after a release, and Updates records each deploy. Autodeploy builds on every git push inside the team's own AWS account, or its VPC when a build needs private resources, and can give branches their own preview environments. The result is one repository where an app's code and the cloud resources it runs on change together.