Integrations Matrix
This page is the fastest technical summary for buyers who want to know what the starter already covers and where they should expect to make product-specific decisions.
| Area | Current starter position | Where it lives | What buyers still decide |
|---|---|---|---|
| Authentication | Convex Auth is the default auth layer, with Google OAuth and email OTP support already modeled | packages/backend/convex/auth.ts, provider modules under packages/backend/convex/providers/* | Which providers to enable, credential setup, and product-specific account lifecycle rules |
| Billing | Polar is the billing provider, with organization-owned subscriptions and webhook flow already modeled | packages/backend/convex/org/billing/*, packages/backend/convex/http.ts, packages/backend/convex/lib/billingPlans.ts | Product pricing, plan structure, trial rules, and entitlement decisions |
| Permissions | Roles and fine-grained permissions already exist as separate concerns | packages/permissions, packages/backend/convex/org/access/* | Which additional permission keys your product needs |
| Capabilities | Product-area gating is already separated from raw permissions | packages/capabilities | Which features are gated by plan, flag, or role bundle |
| Email auth and account mail | Email OTP and password-reset flows already have provider wiring | packages/backend/convex/providers/*, shared branding in packages/config | Provider credentials, sender identity, and product email tone |
| Webhooks | Product webhook handling is already a first-class integration concern in the backend/docs surface | backend webhook surfaces plus docs/dev/integrations/webhooks.md | Which product-specific events you expose or consume |
| Custom domains | The repo already treats custom-domain routing as a supported concern | docs/dev/integrations/custom-domains.md and related routing/env setup | Whether custom domains are part of your launch scope |
| API keys | API-key workflows already exist as a documented integration area | docs/dev/integrations/api-keys.md and backend access controls | Whether external API access is part of your product and how broad it should be |
| Marketing-to-product handoff | Marketing, product, and docs are split into separate apps from the start | apps/marketing, apps/app, apps/docs | How much of the current marketing shape you keep or replace |
How To Read This Matrix
- If the starter already has a position, you are buying time and architectural clarity.
- If the last column is heavy for your product, expect a product-first or architecture-preserving fork rather than a fast branded fork.