Build full-stack apps on your own infrastructure.
At v4.13.1, SST has been under continuous development since August 2020 — nearly six years. The v4 lineage represents a full architectural rewrite (Go CLI + Pulumi/OpenTofu platform layer replacing the prior CDK-based model), and reaching v4.13 with stable cadenced releases demonstrates post-rewrite stabilization. 175 open issues is proportionate to the project scope and star count; triage signals healthy lifecycle management rather than neglect.
No README was retrievable in this appraisal context, which is a direct signal gap. However, the dependency manifest reveals a www workspace with docs:generate and docs:dev scripts, confirming a dedicated documentation site (sst.dev). The score is penalized for the missing in-repo README but tempered by the evidence of an external docs pipeline. External docs are known to be extensive, with guides, component references, and examples — but this appraisal cannot verify current state from available data alone.
The monorepo structure is clean: www, platform, and sdk/js workspaces managed via Bun workspaces. The build pipeline separates concerns clearly — build:platform (TypeScript/Pulumi constructs), build:cli (Go binary), build:sdk (JS SDK). TypeScript typechecks are split per workspace. Go tests exist (test:cli runs go test ./...). The google-protobuf version override suggests deliberate dependency management. The Go+TypeScript polyglot choice is architecturally intentional: performance-critical CLI in Go, cloud component DSL in TypeScript.
Last commit: 2026-05-11 — the day before this appraisal. Latest release: 2026-05-05, one week prior. This is an extremely active project. The weekly release cadence at v4.13 indicates sustained feature and fix throughput well beyond a typical active open source project.
25,965 stars and 2,081 forks place this firmly in the top tier of developer tooling repos. As SST is a canonical framework in the AWS full-stack deployment space with downstream dependents spanning thousands of production applications, community signal is unambiguous. Star-to-fork ratio (~12.5:1) suggests more consumers than contributors, typical for a framework of this maturity.
Overall: 4.3/5
Category: Full-Stack Cloud Deployment Known alternatives in vault: None — this category is not currently represented in the vault. Differentiation: SST occupies a distinct niche: TypeScript-native, component-model IaC targeting full-stack application developers rather than infrastructure engineers. Compared to raw Pulumi or AWS CDK, SST abstracts cloud primitives into application-level constructs (APIs, sites, queues, etc.) and provides Live Lambda Development for local debugging. Its Go CLI provides fast, dependency-free execution. Alternatives like Terraform or raw Pulumi offer more flexibility; CDK offers AWS-native parity — but none match SST's developer-experience focus for full-stack TypeScript teams. Gap or crowd: Clear gap — no cloud deployment or IaC tooling exists in the vault. Adding SST would establish a new category with zero crowding.
Score: 3/5
Harvestable: TypeScript component-model patterns for wrapping cloud resources as typed constructs; Go CLI architecture for fast infra tooling; monorepo workspace orchestration patterns using Bun; SST's sdk/js client patterns for interacting with deployed resources at runtime.
Integration path: SST could serve as the deployment substrate for PAI system cloud components — Lambda functions for agent hooks, SQS queues for async skill dispatch, S3/DynamoDB for knowledge vault persistence, and API Gateway endpoints for external tool interfaces. The sdk/js package enables runtime interaction with SST-deployed resources from within PAI agent code. Not a direct cognitive or knowledge tool, but a plausible infrastructure layer.
Overlap with existing: No overlap — none of the 23 existing vault repos address cloud deployment or IaC.
Adoption cost: Significant — integrating SST as PAI deployment infrastructure requires adopting its component model, understanding its Pulumi backend, and restructuring any existing cloud provisioning. This is a workflow-level commitment, not a library import.
This appraisal is rated medium confidence due to the absent README. The repo is almost certainly the canonical SST framework (Serverless Stack, now simply SST) — the star count, fork count, release cadence, and dependency manifest structure are consistent with the known public project. The anomalyco org name is unusual relative to the expected sst-dev or serverless-stack org and warrants verification before vault inclusion; this could be a prominent fork rather than upstream. If confirmed as canonical or a maintained fork tracking upstream closely, the standalone score should be treated as reliable. PAI fit is moderate — SST is a powerful deployment tool but functions as infrastructure plumbing rather than a cognitive or agent-facing component, limiting its direct integration value relative to the vault's AI-oriented composition.