SST deploys the BoxLite control plane to AWS and configures its Cloudflare edge. The package is
organized by operational domain; each command enters one domain facade and sst.config.ts loads
the stack facade.
npm command -> domain CLI -> deployment facade -> SST -> stack/deployStack()
-> foundation -> observability -> API -> edge -> runners
- Architecture — resource graph and source layout
- Deployment — prerequisites, bootstrap, preview, deploy, artifact modes, routine commands, and troubleshooting
- Security — credentials, policy enforcement, and protected resources
- Networking — VPC layout and traffic flows
- ClickHouse — backend selection and private UI access
Use the repository make targets for validation:
make test:apps:infra # type-checks what needs no `sst install`, then runs the suite
make test:apps:infra-config # installs the SST platform, then type-checks the whole packageNever apply a preview merely to validate configuration. All deploys require an explicit stage and
run through deployment/sst.ts, which loads provider credentials, enforces scope and Runner
policies, cleans Pulumi event logs, and performs post-deploy verification.