Weave 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

Platform Laravel Package

norialabs/platform

norialabs/platform is a modular Laravel foundation for multi-tenant SaaS applications, bundling tenancy, authentication, billing, and admin tooling into one extensible package with sensible defaults, clean architecture, and test-friendly conventions.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Supports decisions around destructive vs. non-destructive rebuilds: when a rebuild no longer defines an entity, the package can retire it while archiving associated data instead of hard-deleting it.
  • Helps PMs define data lifecycle and retention policy for configuration/definition-driven systems: active records, retired records, and archived records become explicit states.
  • Informs roadmap for rebuild/sync workflows: teams can plan safer imports, tenant migrations, and schema-definition updates without losing historical context.
  • Useful for build vs. buy when the product needs repeatable rebuild semantics with audit/history expectations; this package now covers a lifecycle concern that would otherwise require custom archival logic.

When to Consider This Package

  • Consider it when your Laravel application has rebuildable definitions—catalogs, configuration, tenant settings, platform metadata—and a rebuild may remove definitions that previously held data.
  • Consider it when archiving rather than deleting matters for audit, compliance, customer recovery, or operational troubleshooting.
  • Look elsewhere if your domain is mostly simple CRUD with no rebuild process, or if you already have a mature archival/retention subsystem.
  • Validate the exact archival model before adoption: where archived data lives, how it is queried/restored, retention duration, and whether retirement is reversible.

How to Pitch It (Stakeholders)

  • Executive summary: v0.1.13 makes rebuilds safer by retiring definitions that are no longer part of a rebuild and archiving what they held, reducing the risk of irreversible data loss during platform/configuration updates.
  • For engineering: this is a lifecycle-safety feature for rebuild workflows—less custom cleanup code, clearer handling of stale definitions, and a path to audit-friendly retirement instead of hard deletes.
  • For product/ops: it supports safer migrations and configuration changes, but the team should confirm archive visibility, restore procedures, and retention expectations before relying on it in production.
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.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console