Template Gallery

Upload → queue → worker → DynamoDB. The end-to-end reference.

Fan-out app events to an SNS topic, warehouse them in Aurora Serverless v2, and enrich via a third-party API. Covers the eventing + relational-warehouse + external-API trio.

The kitchen sink: Clerk auth, Stripe payments, DynamoDB CRUD, SES email, S3 uploads, and a daily cron — everything wired.

Streaming Claude chat (claude-opus-4-8) with history in DynamoDB. The flagship AI starter.

Drop-in Clerk auth + Stripe + MongoDB. The easiest full SaaS starter.

AWS-native auth (Cognito user pool) + a DynamoDB table.

A bare Next.js app on AWS — add resources as you go.

Next.js + S3 with presigned uploads.

Posts in DynamoDB, media in S3.

Content store, asset bucket, async reindex worker, admin secret.

Courses + progress tables, video bucket, transcode worker.

Listings, images, order queue + fulfillment worker, Stripe secret.

RDS Postgres (VPC auto-generated), transactional email, Stripe secret.

Clerk auth + Stripe payments (webhook) + MongoDB + uploads.

EventBridge bus: the app publishes events, a worker subscribes and logs them.

HTTP API Gateway with a Stripe webhook route handler that logs to DynamoDB.

Uploads to S3 trigger a worker (bucket.notify) that processes and logs to DynamoDB.

A Router front-door (custom domain) serving a static docs site at /docs and a bucket at /assets.

Leads table + a weekly report cron.

A Next.js app starts a durable Step Functions execution (Validate → Process → Done) for each order, with each step a Lambda. Orders persist in DynamoDB. Survives retries and long-running waits.

Live WebSocket pub/sub over AWS IoT: a custom authorizer guards every connection, the Next.js app publishes messages, and a subscriber Lambda processes them. History persists in DynamoDB.

A Next.js app kicks off a one-off Fargate Task (heavy batch work — video transcode, report build) with task.run(), and the task writes results to S3. No idle cost: the container only runs when invoked.

A long-running container on ECS Fargate behind a load balancer, talking to Postgres and a Redis cache. SST generates the Cluster, the VPC (with fck-nat), and a starter Dockerfile. `sst dev` runs the container locally.

A managed GraphQL API with AppSync: a starter schema, a Lambda resolver that reads/writes a DynamoDB table, and a Next.js app that queries it through a typed gql() helper.

Self-hosted auth with OpenAuth (sst.aws.Auth): the issuer runs on Lambda with auto-provisioned DynamoDB storage, and the Next.js app gets the full login/callback/verify flow. Your auth, your data — no third-party auth bill.

A read-heavy API: Postgres as the source of truth, ElastiCache Redis (cluster-mode, TLS) as the cache. Both share one auto-generated VPC; fck-nat keeps Lambdas online.

Blob, Postgres, queue + consumer, cron, Stripe webhook, Resend.

Next.js blog on Vercel: Neon Postgres for posts, Vercel Blob for images.

Storefront with Postgres catalog, Blob product images, an order queue + consumer, a Stripe webhook, and Resend receipts.

Multi-tenant SaaS: Postgres data, Upstash Redis cache, transactional email, and a daily digest cron.

A fast marketing site with a Resend contact form and a weekly newsletter cron. Zero-config deploy.

Upload to Vercel Blob, enqueue a resize job, and process it in a push-mode queue consumer.

Listings in Postgres, company logos in Blob, an expiry cron, and Resend alerts.

Postgres for durable data plus Upstash Redis for presence and live counters.

Receive a signed webhook, enqueue it, and process events in a consumer; an event log in Postgres.

Subscribers in Postgres, a scheduled send cron, and Resend delivery.

A Vercel Queue + push-mode consumer for async work, with Upstash Redis for locks/dedupe.

Content in Postgres, media in Blob, and an Upstash Redis read cache for fast delivery.

A JSON API with Postgres storage, Upstash Redis rate-limiting, and a partner webhook.

Instant feature flags from Edge Config (read at the edge with no DB round-trip), data in Postgres.

Calls an external weather API through a typed fetch helper, with an Upstash Redis response cache.

A SaaS with Web Analytics + Speed Insights wired into the layout, Postgres data, and email.

A typed proxy to an external AI provider (your code calls it — the builder makes no AI calls), with Redis rate-limiting and model config in Edge Config.

Short links in Upstash Redis, click analytics in Postgres, and Web Analytics on the redirect.

A cron pings an external health API on a schedule and emails on failure; Speed Insights on the dashboard.

Streaming AI chat through the Vercel AI Gateway (you run it — the builder makes no AI calls), with chat history in Postgres and Upstash Redis rate-limiting.

Dynamic Open Graph images at the edge (next/og) for shareable cards, with media in Blob and Web Analytics.

Stripe webhook kicks off a durable Vercel Workflow that charges, waits, and ships — with an order queue, Postgres, and Resend receipts. Survives deploys and crashes.

Feature flags backed by Edge Config (flip flags with no redeploy), the Flags Explorer endpoint, Postgres data, and background tracking via after().

An abuse-resistant JSON API: WAF rate-limiting (checkRateLimit), Postgres storage, Upstash Redis, and a partner webhook.

Upload to Blob, kick off a durable Workflow that extracts + summarizes via the AI Gateway, queue the heavy steps, and store results in Postgres.

Edge Middleware geo-routes visitors, Feature Flags (backed by Edge Config) drive a progressive rollout, dynamic OG images, and full Web Analytics + Speed Insights.

A streaming AI Gateway chat protected by BotID and WAF rate-limiting, with history in Postgres — abuse-resistant by construction.

An AI agent (AI Gateway) writes code, runs it in an ephemeral Sandbox microVM, orchestrates multi-step runs with a durable Workflow, stores artifacts in Blob, and rate-limits execution.