Laravel Belvedere Laravel Package

Product Decisions This Supports

• Build vs. buy for queue observability: Belvedere addresses a specific gap: Horizon-style visibility for Laravel’s database queue driver, which Horizon does not cover because it is Redis-focused. For teams already using database queues, this can reduce the need to build an internal dashboard for job throughput, failures, and queue health.
• Queue backend strategy: Helps evaluate whether to stay on database queues longer, especially for small-to-mid deployments, rather than migrating to Redis solely to gain operational visibility. It lowers one adoption barrier for database-backed queues.
• Operational readiness and support: The stated compatibility with Laravel 12/13 and MySQL 8.4/9.7, MariaDB 11.8, PostgreSQL 17, and SQLite is useful for roadmap and platform-support decisions. It suggests cross-database intent, but v0.1.0 should be treated as early-stage until validated in your environment.
• Feature prioritization: If your product or internal platform relies on database queues, this supports prioritizing failed-job triage, queue monitoring, and basic observability over custom admin tooling.
• Use cases: Appropriate for local/staging visibility, small production deployments, Laravel apps avoiding Redis, and teams that need a lightweight dashboard for database queue operations. Less suitable as the sole observability layer for high-throughput production queues without additional monitoring.

When to Consider This Package

• Consider it when you are on Laravel 12 or 13, use the database queue driver, and need Horizon-like operational visibility without adopting Redis.
• Consider it for early evaluation / pilot use if your database is one of the tested versions: MySQL 8.4 or 9.7, MariaDB 11.8, PostgreSQL 17, or SQLite.
• Consider it when the primary need is queue and failed-job visibility for internal teams, not full APM, alerting, auditing, or enterprise support.
• Look elsewhere if you use Redis queues and can use Horizon, need a mature production-grade observability platform, require vendor SLAs, or depend on Laravel/PHP/database versions outside the tested matrix.
• Treat v0.1.0 as pre-1.0: expect possible breaking changes, limited long-term support guarantees, and the need for engineering validation before production adoption.
• Look elsewhere if you need deep metrics retention, alerting integrations, multi-tenant access control, compliance features, or high-scale queue analytics.

How to Pitch It (Stakeholders)

Belvedere is a new, early-stage Laravel package that adds a Horizon-style dashboard for Laravel’s database queue driver. It fills a real visibility gap for teams using database queues instead of Redis: instead of building internal queue-monitoring tooling, teams can evaluate a package designed for job and failed-job visibility. The first release targets Laravel 12/13 and has been tested across MySQL, MariaDB, PostgreSQL, and SQLite. For engineering, the recommendation is a contained pilot in non-critical or staging environments first, with production adoption gated on compatibility validation, security review, and tolerance for pre-1.0 API changes. For leadership, the value is reduced operational blind spots and potentially avoiding a premature Redis migration just to get queue observability; the risk is package immaturity and limited production track record at v0.1.0.