Security boundaries you can inspect
The kit centralizes identity, tenant policy, write authority, realtime scope, and safe errors. Provider configuration and production certification remain explicit deployment responsibilities.
What the repository enforces
Trusted server identity
Clerk supplies session identity; server services resolve memberships and roles instead of trusting browser-supplied tenant claims.
One write authority
Shared Zod contracts, tenant policy, and PostgreSQL transactions own browser-initiated writes. Database and provider secrets stay server-side.
Authorized realtime
Electric uses fixed server-owned tables, columns, and tenant predicates through a same-origin authenticated proxy.
Safe, traceable failures
Stable error codes and support references keep public copy safe while Sentry, audit history, processes, and the Control Center retain operational context.
Sub-processors
The template integrates the following services. A product owner must select regions, retention, agreements, and credentials that fit their deployment.
- Clerk — authentication
- PostgreSQL + ElectricSQL — database + real-time sync
- Stripe — payments
- Resend — transactional email
- PostHog — consent-aware product analytics
- Sentry — error monitoring
- Railway — hosting
Reporting a vulnerability
Follow the repository security policy or email [email protected]. Replace the placeholder company address before publishing a derived product.
Compliance
The kit includes consent controls and durable export and deletion workflows. Those product mechanisms do not constitute legal or provider certification. Each deployment still needs its own legal, security, privacy, and production review.