Build full-stack apps on your own infrastructure.
| Rating | Summary | |
|---|---|---|
| Quality | decent (14/24) | Excellent health and engineering signals drag a zero documentation score that is a data artifact — SST has a full docs site; real quality is closer to excellent. |
| PAI Relevance | WATCH (0.63) | Fills a genuine deployment infrastructure gap in PAI but requires full cloud provider setup and framework-level adoption that sits outside PAI's current Cloudflare-native, modular pattern. |
The standalone score of 14 materially understates actual quality. SST has a dedicated docs site (docs.sst.dev), active daily releases, and a large community; the 0/8 documentation score is entirely a consequence of the missing README in the evidence dataset. A re-appraisal with README content would likely push standalone_score to 20–21.
14/24 — maintained / undocumented / high-discipline
Failed:
Passed:
Failed:
Passed: (none — all probes require README content, which is absent from evidence)
Failed: (none)
Passed:
| Dimension | Score | Assessment |
|---|---|---|
| Harvest Value | 1 | SST's Pulumi-backed multi-provider component model (AWS, Cloudflare, Vercel unified under one TypeScript config) has architectural interest for PAI's cloud deployment patterns, but no directly novel algorithm applicable to a named PAI subsystem like ISA, Loop, or Delegation. |
| Integration Readiness | 1 | TypeScript SDK is bun-installable and the Go CLI is subprocess-friendly, but SST is a full deployment framework requiring cloud provider accounts, project scaffolding, and persistent state — not a drop-in library for a PAI skill or hook. |
| Overlap Risk | 0 | No existing PAI skill or tool covers full-stack IaC deployment orchestration; StacksUp manages tool subscriptions and PAIUpgrade handles self-upgrade but neither provisions cloud resources. |
| Gap Fill | 1 | PAI has no IaC framework for deploying multi-service applications; SST would address this for active projects like Conservancy (SvelteKit/Cloudflare Pages) or Aphoria, though PAI's Cloudflare-native setup limits how much SST adds over native Wrangler for those specific targets. |
Composite: 0.63
The Conservancy (SvelteKit + Cloudflare Pages) shares SST's exact supported stack: Don't migrate now — SST v4 underwent a full architectural rewrite and the Cloudflare provider is still accumulating post-release fixes. Check the sst/sst changelog once per quarter for Cloudflare component stability signals (breaking-change frequency dropping, issues closing faster than opening). If it stabilizes by Q4 2026, SST becomes a credible alternative to managing Wrangler and Pages deploys separately.
Before any future TypeScript project touches more than one cloud provider: Run npx sst@latest init on a throwaway repo and spend one session with sst dev to understand the live-function hot-reload loop and linked-secrets model. This takes under an hour and produces a concrete baseline for evaluating whether SST's developer experience is worth the framework lock-in — rather than discovering friction mid-migration.
Bookmark for re-evaluation when v4 reaches 12 months of release history (approximately late 2026): SST's 26k stars confirm strong community pull, but the v4 codebase is still absorbing the consequences of swapping its entire execution model. Revisit the open-issue backlog and Discord activity at that point; if multi-cloud component reliability is consistently reported as solid, the watch status upgrades to a genuine integration candidate for TypeScript projects with AWS or Cloudflare backend needs.
Category: Cloud & Infrastructure
In this category: first entry
Standing: SST is the first cloud/infrastructure repo appraised; at 26k stars with an active daily release cadence it would rank as the highest-quality infrastructure entry by adoption and health metrics.
Density: 7/10 — Available: stars, forks, open issues, license, creation date, last-commit date, release tag, dependency manifest (root workspace), language, description. Missing: README content, sub-package manifests (platform/, sdk/js/), CI workflow files, actual dependency graphs for sub-packages, test coverage data.
docs:generate / docs:dev script in the root manifest confirms an integrated docs pipeline. Re-appraisal with README access would likely score 6–7/8 on documentation, pushing standalone_score to 20–21 (excellent).