Tomato Hr Module Laravel Package

Product Decisions This Supports

• Build vs. buy for internal HR admin. The module is a starting point for the CRUD-heavy back office of an HR function (employee records, departments, job titles/positions, and related lookups). The decision it informs is whether to spend sprint capacity hand-building those Filament resources or fork an existing module and extend it.
• Roadmap sequencing for an admin panel. If HR is on the roadmap, this determines whether HR ships as a thin "records + org structure" slice first, with payroll, attendance, leave workflows, and performance management deferred to later phases.
• Ecosystem commitment. Adopting it implies adopting the TomatoPHP/Filament stack (tomato-admin conventions, Splade/Tailwind admin UI, Filament version coupling). Treat it as a platform decision, not a single-package decision.
• Use-case fit. Best suited to internal back-office tooling, SMB HR admin, multi-tenant SaaS where HR is one module among many, and POC/demo builds. Poorly suited to anything where payroll accuracy or regulatory compliance is the core value.
• Scope gap analysis. The decision input is what the module gives you out of the box versus what you must build: payroll and tax, leave accrual rules, document/contract management, org charting, reporting, SSO, audit trails, and integrations with existing HRIS or identity providers.
• Release-signal caution. v1.0.0 is the initial public release and the changelog is empty, so the actual feature surface, test coverage, and migration stability must be verified from source in a timeboxed spike before it is treated as a dependency.

When to Consider This Package

Consider it when:

• The team is already on Laravel + Filament and comfortable with third-party Filament plugins.
• You need HR record-keeping and org structure quickly — internal admin, not a customer-facing payroll product.
• You are willing to fork and own the code; the license and structure make this a realistic path.
• You want a prototype or demo of an HR module without building schema and resources from zero.
• You accept young-package risk: expect thin documentation, limited release history, and no support contract.

Look elsewhere when:

• You need payroll, tax withholding, benefits administration, or statutory compliance — these are regulated domains where an unproven community module is the wrong foundation.
• You require SLAs, security attestations, or vendor accountability (SOC 2, DPA, pen-test reports).
• You are not on Filament, or you are pinned to a Filament/Laravel version the module does not track.
• You need a published roadmap, semantic-versioning guarantees, or measurable maintenance activity. An empty v1.0.0 changelog gives no signal on any of these.
• Your HR data is highly sensitive at scale and you need audited access control, field-level encryption, and retention policies the module does not appear to ship.

How to Pitch It (Stakeholders)

For executives: This is an open-source HR admin module for our Laravel stack. It gives us employee and department management screens essentially for free, which shortens time-to-demo and avoids a from-scratch build of routine CRUD. Cost is near zero; the real cost is ownership — we would fork it, harden it, and maintain it ourselves. It is not a payroll or compliance product and should not be positioned as one. Recommendation: approve a short evaluation, not a production commitment.

For engineering: It is a Filament plugin with migrations, models, and admin resources layered on tomato-admin conventions. Before adopting, run a one-to-two day spike: confirm Laravel/Filament version compatibility, review migrations for destructive or non-portable choices, check test coverage, and identify the extension points we would need for our own policies and authorization. Assume we will vendor or fork it, wrap it in our own access-control and audit layer, and add tests around anything that touches employee data.

Ask: Timeboxed spike plus a security and maintenance review. Decision gate: adopt as a forked internal module if the spike passes; otherwise build the equivalent resources in-house, which is a known and bounded effort.