Product Decisions This Supports
- Build vs. buy for AI usage metering. The package sits on top of Laravel Swarm / Laravel AI 1.x and provides usage accounting — i.e. the metering layer behind quotas, plan limits, overage billing, and cost attribution. That is a recurring, undifferentiated build for most teams; adopting it removes an entire instrumentation workstream from the roadmap.
- Feature gating and monetization design. Per-tenant/per-user usage records are the prerequisite for tiered plans, credit packs, fair-use policies, and "AI credits" style pricing. Choosing this package is effectively a decision to make usage data a first-class product primitive early, rather than retrofitting it after launch.
- Platform commitment on the AI layer. v0.4.0 explicitly tracks Laravel Swarm v0.28 and Laravel AI 1.x, with a CI control that rejects a v0.27 core on the v0.28 lane. For a PM, that's evidence the maintainer is deliberately keeping pace with the upstream official stack rather than drifting — relevant when deciding whether Laravel AI is a safe 12–18 month bet for agent features.
- Scoping and sequencing. Because the integration surface is narrow and no runtime/schema/accounting semantics changed in this release, AI features can be scoped without carving out a separate "metering platform" epic. Work lands in product features, not infrastructure.
- Risk register maintenance. The 0.x version line and fast-moving upstream (
^0.19 through ^0.28 supported) is a standing dependency-management item. This release does not change that risk profile, but it does confirm active maintenance.
When to Consider This Package
Adopt when:
- You are on Laravel and are using — or have concretely committed to — Laravel Swarm / Laravel AI 1.x for agent or LLM-backed features.
- You need per-user, per-tenant, or per-workspace token/call accounting, quota enforcement, or cost visibility, and you do not want to build and maintain that yourself.
- You need PHP 8.4/8.5 and a current Laravel runtime — the newly added native lanes cover exactly this, which previously may have been a blocker.
- You value upstream-tracking discipline: eight dependency profiles, including a negative control that fails the build if an incompatible core is paired with the v0.28 lane.
Look elsewhere when:
- You are not on Laravel, or you are on a different AI abstraction (direct SDKs, a provider gateway, LangChain-style tooling). The value here is the Laravel/Swarm integration, not the accounting model.
- You need vendor-neutral metering across multiple frameworks or languages — an observability/LLM-gateway vendor will fit better.
- You require enterprise support, SLAs, or a stable public API guarantee. This is a 0.x package; the semver contract is not yet in force, and the wide supported range exists precisely because upstream is still moving.
- Your usage accounting must be authoritative for invoicing today. The package's own release notes scope this version as compatibility-only; validate accounting fidelity against your billing requirements before depending on it for revenue.
How to Pitch It (Stakeholders)
For executives (one paragraph): This is a small, focused Laravel add-on that handles usage accounting for our AI features — the plumbing behind per-customer limits, credits, and cost control. Adopting it means we can price and cap AI usage without building a metering system ourselves, and the newest release simply keeps us aligned with Laravel's official AI stack. There is no migration cost and no behavior change in this version: it adds support for Laravel Swarm v0.28 and PHP 8.4/8.5, while continuing to support every core version from 0.19 through 0.28. The main caveat is maturity — it is pre-1.0 software, so we pin the version and treat upstream upgrades as planned work rather than automatic.
For engineering (the short version): v0.4.0 is a compatibility release, not a feature release. It admits core ^0.28 and adds PHP 8.4/8.5 lanes built on the frozen v0.28 core candidate 269f749 with official Laravel AI 1.x, bringing the matrix to eight dependency profiles. All ^0.19–^0.27 ranges are retained, so nothing is forced. The release explicitly states no runtime, schema, or usage-accounting changes — treat the upgrade as low risk, but still validate against your existing usage-accounting assertions because the lane composition changed. Worth noting as a positive signal: the new lane includes a discriminating control that rejects a v0.27 core on the v0.28 lane, which means the compatibility claim is tested negatively, not just asserted.
Recommendation: Proceed with adoption if Laravel AI/Swarm is the chosen stack; pin to 0.4.x, keep the dependency matrix in CI, and re-evaluate the maturity question at 1.0.