Change anything without redeploying.
Feature flags, tenant-specific settings, and admin-managed parameters — configuration changes take effect instantly, with full auditability.
Change anything without redeploying
Hard-coded configuration creates bottlenecks: every settings change requires a developer, a PR, and a deployment. This module puts configuration in the hands of admins — securely, instantly, and with full auditability.
Features
From global defaults to per-tenant whitelabeling.
Dynamic configuration
A key-value settings store with typed values (string, number, boolean, JSON); hierarchical overrides — system defaults, tenant settings, user preferences; live updates that take effect immediately without a server restart; and validation rules that prevent invalid configuration values.
Feature flags
Boolean and percentage-based flags for gradual rollouts; user segment targeting to enable features for specific roles, tenants, or user groups; A/B testing support that serves different experiences to different segments; and kill switches to instantly disable problematic features.
Tenant-specific settings
Per-tenant configuration so each tenant can customize their experience; whitelabel settings for branding, colors, logos, and domain configuration per tenant; plan-based features that tie feature availability to subscription plans; and an admin UI where tenant admins manage their own settings within allowed boundaries.
Admin interface
A settings dashboard to browse, search, and edit all configuration; change history with a full audit trail of who changed what and when; import/export to back up and restore configuration as JSON or YAML; and environment comparison to diff settings between staging and production.
Technical Details
| Component | Implementation |
|---|---|
| Backend | Django models with caching, DRF API |
| Frontend | React admin panel with form generation for typed settings |
| Caching | Redis-backed cache with invalidation on change |
| Audit | Integrates with Audit Log module |
Integration Time
Typically 2–5 days for the core settings engine. Feature flags and tenant-specific settings are included, with time depending on admin UX and permission requirements.
Pairs Well With
Multi-Tenant SaaS — tenant-scoped configuration.
Auth, SSO & RBAC — permission-controlled settings access.
Audit Log — track every configuration change.
Frequently asked questions
How long does integration take?
Typically 2–5 days for the core settings engine. Feature flags and tenant-specific settings are included, with time depending on admin UX and permission requirements.
Do setting changes require a redeploy?
No. Values live in a key-value store with a Redis-backed cache and invalidation on change, so updates take effect immediately without a server restart.
Can features be rolled out gradually?
Yes — boolean and percentage-based flags support gradual rollouts, with user segment targeting by role, tenant, or user group, A/B testing support, and kill switches to instantly disable problematic features.
Can tenants customize their own settings?
Yes — per-tenant configuration includes whitelabel branding, colors, logos, and domains, plus plan-based feature availability, with tenant admins managing their own settings within allowed boundaries. Change history tracks who changed what and when.
One of eight modules in the Mibrex Accelerator.
Settings Engine pairs well with Multi-Tenant SaaS for tenant-scoped configuration, Auth, SSO & RBAC for permission-controlled settings access, and Audit Log for tracking every configuration change.
Explore the Accelerator ModulesPut configuration in the right hands.
Book a discovery call — we’ll show you what your admins could control without a deployment, and how quickly the engine drops in.