Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Laravel Settings Laravel Package

qcod/laravel-settings

Store application settings as key/value pairs in your Laravel database with zero-query performance via caching. Easy get/set/has/remove APIs, helper and facade access, optional migrations publishing, and support for grouping settings (default group included).

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Enables dynamic configuration changes without code deployments, supporting rapid experimentation (e.g., feature flags, UI tweaks, A/B testing)
  • Reduces technical debt by eliminating hardcoded values in config files, improving maintainability and reducing deployment friction for minor updates
  • Critical for multi-tenant SaaS architectures where tenant-specific settings must be managed independently without redeployments
  • Validates "buy vs build" decision: avoids reinventing lightweight settings management, freeing engineering bandwidth for core product features
  • Supports roadmap priorities like self-service admin panels or tenant customization capabilities without custom backend development

When to Consider This Package

Adopt when:

  • You need runtime-configurable settings (e.g., site-wide toggles, dynamic branding) with minimal setup
  • Your app has admin panels or multi-tenant requirements where settings must be updated without code changes
  • Caching for high-performance lookups is needed but complex settings management (e.g., versioning, audit trails) isn't required
  • You prioritize simplicity and Laravel-native integration over enterprise-grade governance features

Look elsewhere if:

  • Your settings require complex schemas, granular permissions, or version-controlled history (e.g., enterprise config management tools)
  • All configuration is static and better managed via environment variables or .env files
  • Your app is small-scale with no need for runtime adjustments (e.g., internal tools with infrequent config changes)

How to Pitch It (Stakeholders)

Executives: "This package lets non-technical teams adjust application behavior in real-time—like changing promotional banners, enabling features, or tuning UX elements—without waiting for engineering cycles. It accelerates experimentation, reduces deployment overhead, and directly supports revenue-generating initiatives like A/B testing or tenant customization, all with zero cost and minimal risk."

Engineering: "It’s a battle-tested, lightweight solution that integrates seamlessly with Laravel’s ecosystem. With a clean API, built-in caching, and database persistence, it eliminates the need to build custom settings management from scratch. Developers spend minutes—not weeks—setting it up, and it scales effortlessly for admin panels or multi-tenant workflows while keeping codebase complexity low."

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
davejamesmiller/laravel-breadcrumbs
artisanry/parsedown
christhompsontldr/phpsdk
enqueue/dsn
bunny/bunny
enqueue/test
enqueue/null
enqueue/amqp-tools
milesj/emojibase
bower-asset/punycode
bower-asset/inputmask
bower-asset/jquery
bower-asset/yii2-pjax
laravel/nova
spatie/laravel-mailcoach
spatie/laravel-superseeder
laravel/liferaft
nst/json-test-suite
danielmiessler/sec-lists
jackalope/jackalope-transport