Configuration Files
The config files in packages/config that drive a deployment.
A deployment is shaped almost entirely by a handful of typed config files in
packages/config/src. Edit these (plus environment variables) rather than
hunting through application code.
Overview
| File | Drives |
|---|---|
plugin.ts | Identity — name, slug, domain, company, description |
branding.ts | Theme — colors, logos, CSS tokens |
pricing.ts | Plans and their limits |
providers.ts | Active auth / billing / email providers |
services.ts | Storage, analytics, monitoring, jobs, i18n flags |
connector.ts | Admin Module connection settings |
plugin.ts
branding.ts
Colors, logos, and CSS custom-property tokens that theme the whole UI without touching component code. The primary color also drives accents and the navigation progress bar.
pricing.ts
Defines every plan and its entitlements. Plans sync to the database and back the billing flow:
providers.ts
Selects the active provider for each pluggable subsystem. Switch a provider by changing one value — adapters live behind a shared interface.
See Providers for the full switching guide.
services.ts
Central, config-driven flags for the cross-cutting platform services. Analytics and monitoring are off unless their keys are present:
| Service | Gate |
|---|---|
| Storage | STORAGE_ACCESS_KEY_ID + STORAGE_BUCKET set |
| Analytics (GA4) | NEXT_PUBLIC_GA_MEASUREMENT_ID set |
| Monitoring (Sentry) | SENTRY_DSN / NEXT_PUBLIC_SENTRY_DSN set |
| Jobs (QStash) | QSTASH_TOKEN set |
| i18n | Locales listed in i18nConfig |
connector.ts
Settings for the Admin Module connection:
Non-secret switches live in these files; secrets always come from environment variables. See Environment Variables.