Configuration

Kinoder validates backend configuration at startup. Production credentials belong in protected deployment secrets, never committed files.

Configuration areas

• Application: public URL, service identity, logs, and CORS.
• Data: PostgreSQL, Redis, migrations, queues, and workers.
• Storage: local MinIO or S3-compatible storage, signed access, and retention.
• Identity: cookies, sessions, passwords, MFA encryption, and email.
• Billing: Stripe, webhooks, token-ledger integrity, packages, and storage plans.
• AI: credentials, models, route order, fallback, timeouts, and positive Kino Credit rates.
• Rendering: Chromium, FFmpeg, runtime URL, cancellation, and output checks.
• Social: OAuth applications, scopes, callbacks, and publishing modes.
• MCP: HTTPS URL, feature switch, OAuth scopes, and revocation.

IMAGE PLACEHOLDER - Configuration map Replace with Browser -> Caddy -> Frontend/API -> PostgreSQL, Redis, and Object Storage, with Worker -> external providers. Recommended size: 1800 x 1100 px.

A zero-priced provider route is unavailable unless an administrator explicitly enables the matching free-generation policy. Credentials alone do not make a capability commercially approved.