Sansdaemon Laravel Package

Product Decisions This Supports

• Deployment-target strategy: Lets the product run queue-backed and scheduled features (emails, reports, webhooks, cleanup jobs) on hosts where a persistent queue:work daemon or Supervisor is unavailable — shared hosting, low-cost PaaS, restricted corporate VMs. This directly informs whether "no-daemon" hosting can be a supported tier.
• Feature scope decisions: If we adopt this, product can commit to features that depend on asynchronous processing even in constrained deployments, without forcing a hosting upgrade for every customer.
• Build vs. buy: Replaces a custom cron-triggered queue runner / bespoke "fake daemon" glue that would otherwise be maintained in-house. Adopt the package rather than reinvent the trigger and worker lifecycle.
• Roadmap planning: v1.3.2 adds Laravel 13 support, which means the package can be carried forward on the next framework upgrade — a signal for planning rather than a feature change.
• Use cases to target: MVP launches on budget hosting, scheduled digests and CRM syncs on cron-only servers, and internal tools deployed where ops refuses to run long-lived processes.

When to Consider This Package

Consider adopting when:

• The deployment target cannot run persistent workers (shared hosting, some managed platforms, certain locked-down enterprise environments).
• Cron is available and an acceptable processing trigger; slightly delayed or batch-style queue processing is tolerable.
• You want a lightweight, dependency-minimal bridge rather than new infrastructure.
• You need a short-term path to ship queue-backed features while a proper worker infrastructure decision is pending.

Look elsewhere when:

• You control the server and can run Supervisor/systemd with Redis, SQS, or a managed queue — native queue:work workers are the correct, higher-throughput choice.
• The product needs low-latency, high-volume, or near-real-time job processing; cron/request-triggered processing will not meet SLAs.
• You require strong delivery guarantees, advanced retry/backoff semantics, or complex job orchestration.
• The workload is long-running or resource-heavy; a daemonless model risks request timeouts and overlapping runs.

How to Pitch It (Stakeholders)

For executives: "This is a small, actively maintained add-on that lets our Laravel application process background jobs and scheduled tasks without running a long-lived server process. Release v1.3.2 confirms the maintainer is keeping pace with the framework — it adds Laravel 13 support with no breaking changes — which lowers our upgrade risk. Commercially, it unlocks launching on cheaper, simpler hosting and widens the deployment options we can support. It is a tactical enabler, not a substitute for real queue infrastructure once volume grows."

For engineering: "The package provides a daemonless path to execute queued work, typically driven by cron or request hooks instead of a supervised worker. v1.3.2 is a maintenance release: Laravel 13 compatibility plus a README version badge. No breaking changes, no migration steps, and no new runtime dependencies implied. Safe to pin and evaluate against our deployment matrix; adopt where daemons are unavailable, and keep native workers for production-scale throughput."