Skip to content
Docs

Integrations

Setup order, env rules, and operational boundaries for Clerk, Convex, Polar, Sanity, Resend, PostHog, Vercel, and admin access.

1

Beginner runtime configuration starts in .env.example, production handoff values live in .env.production.example, and optional/internal knobs live in .env.advanced.example.

2

.varel/project.json controls whether setup guidance targets local-first local/development only or launch-ready local/development plus production, with preview optional.

3

Clerk owns identity; use development instance keys locally and production instance keys for launch.

4

Product IDs, webhook secrets, Convex URLs, and Vercel tokens must stay in scoped env, never in code.

5

Polar sandbox belongs in local/preview env; Polar production belongs only in production env.

6

Polar debugging starts from official docs plus pnpm polar:doctor when checkout, benefits, portal access, or GitHub grants are involved.

7

Sanity owns public content and the blog. Use hosted Studio, source-controlled schemas, Sanity MCP/CLI, and official Sanity skills; install those skills globally rather than committing them to your repo.

8

Cal.com powers internal consulting booking links and future customer scheduling guidance; use OAuth for customers and never ask end users for API keys.

9

Resend is optional locally and skips safely when sender env is missing.

10

PostHog stays optional locally and initializes only when the project token is present.

11

ADMIN_EMAILS enables the internal /admin operator dashboard for trusted emails only.