sst looks very promising. Another IaC tool in what has become a very competitive space. But with a meaningfully different approach.
sst closes the gap between your application logic and infrastructure code. Much more so than Terraform/OpenTofu. Similar to Pulumi.
Your entire application (in theory) is defined in a single sst.config.ts file in your project root.
Frontend/backend frameworks, SaaS tie-ins like Stripe or Slack, and cloud infra on all major providers.
Part of how they've done this is by using Pulumi under the hood for many of the providers.
If a provider isn't natively supported by Pulumi, it uses a Terraform provider instead and is bridged through Pulumi, back to sst.
It's installed like any other project dependency (pnpm add sst) and the accompanying CLI handles deployment for you (pnpm exec sst deploy).
Naturally, the similarities between sst and CDKTF/Pulumi draw comparisons.
But sst is better thought of as an abstraction above CDKTF/Pulumi rather than a direct alternative.
For developers looking for a first foray into IaC without diving too far into DevOps/CloudOps, sst is worth a shot.