Platform
CivicSurplus
Municipal surplus SaaS
CivicSurplus
Platform Administration
Review CivicSurplus platform identity, production domains, integration readiness, and the environment variables required for future automation. Secret values are never displayed here.
Platform
CivicSurplus
Municipal surplus SaaS
Architecture
Dedicated
One environment per client
Integrations Ready
2 / 5
Based on server environment
Deployment Mode
Production
Render + Cloudflare
Public addresses assigned to the CivicSurplus platform.
This page checks only whether expected variables exist. It never reveals keys, tokens, or secret values.
Primary CivicSurplus control database, authentication, and storage.
Required environment variables
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEYFuture deployment status, service management, logs, and automated client provisioning.
Required environment variables
RENDER_API_KEYFuture dedicated database project creation and lifecycle management for each client.
Required environment variables
SUPABASE_ACCESS_TOKENFuture subscription checkout, invoices, payment status, and account synchronization.
Required environment variables
STRIPE_SECRET_KEYSTRIPE_WEBHOOK_SECRETFuture onboarding, password setup, deployment, support, and billing messages.
Required environment variables
RESEND_API_KEYSecurity rule
Provider credentials belong only in Render server-side environment variables. They must not be committed to GitHub, exposed with a NEXT_PUBLIC_ prefix, or stored as raw values in Supabase tables.