Generated from corpus/lines/software/units/sw.pattern.vercel.md. Do not edit by hand — run python scripts/generate-corpus-docs.py.

sw.pattern.vercel

Status: draft (new; D2)
Sources: Hector D2 2026-07-22

When to use

• Standalone app that fits Vercel (static, frontend, or serverless-friendly).
• No requirement for konstant systemd/socket/nginx on the VPS.
• User explicitly wants Vercel or Conductor asked and user chose Vercel.

Guardrails

• Still: Prototype → promote → GitHub repo → GitHub-first issue tracking.
• Configure secrets in Vercel project env + Bitwarden references; never commit secrets.
• CI may be Vercel Git integration and/or GitHub Actions; steady state is still git-push based.
• Lab catalog (if any) still requires a verified live URL first.
• Document host: vercel on the issue.

Not for

• Socket-activated MCP/API designed for konstant
• Apps that need Tailscale-only admin surfaces on konstant by default

Prohibited

• Using Vercel as silent default when user expected konstant
• Storing Vercel tokens in the repo