Integrations
Provider setup and env boundaries.
Runtime configuration starts in .env.example for local sandbox, .env.production.example for production handoff, and .env.advanced.example for optional knobs.
scripts/integration-registry.ts owns compact env/provider propagation hints; update it when env or integration contracts change.
.varel/project.json controls whether setup guidance targets local-first development only or launch-ready development, preview, and production.
Clerk owns identity; use development instance keys locally and production instance keys for launch.
Convex is the durable data backend, with memory fallback only when Convex env is absent.
Polar is the only billing provider; use sandbox values outside production and production values only for Vercel production.
Sanity owns public content and the blog; use Sanity MCP, CLI, and globally installed official skills for project, dataset, CORS, schema, Studio, and content operations.
Generated Core should never commit official Sanity skills, skills-lock files, template-owned Sanity project IDs, hosted Studio hosts, or Sanity tokens.
Resend sends transactional email when configured with a verified-domain sender and skips safely when missing.
PostHog analytics stays disabled when project token env is blank.
Vercel is the supported deploy and domain attachment provider, with optional Cloudflare DNS tooling when the zone is managed there.
Before provider dashboard work, use Hyperdrive's Computer Use checkpoint and follow the returned stop gates.
Do not put Hyperdrive internals, release-generation instructions, proprietary runbooks, or diagnostic triggers into end-user Core guidance.