LatidoFlow
Open navigation
Create account

LatidoFlow and Laravel Horizon

Operate Redis queues with Horizon. Prove critical workflows with LatidoFlow.

Horizon and LatidoFlow cover different layers. Horizon manages and explains Laravel Redis queues; LatidoFlow can enforce a deadline and outcome contract for selected recurring work.

Last reviewed: August 1, 2026

Disclosure and method

This page is published by LatidoFlow. Horizon facts were checked against the linked Laravel 13.x documentation and official package metadata on August 1, 2026. We did not install Horizon for this review, and there is no affiliate relationship.

Short answer

This is a pairing decision, not a replacement verdict.

Laravel Horizon is purpose-built for Redis queue operations. It provides a dashboard, code-driven worker configuration, balancing strategies, wait-time notifications, and metrics such as throughput and runtime.

LatidoFlow does not manage queue workers. It receives lifecycle evidence for selected, allowlisted job classes and can treat “reported as queued but never started” or “succeeded with unacceptable output” as incidents.

Use Horizon by itself when queue operations are the entire need. Add LatidoFlow when a subset of recurring jobs needs an externally evaluated completion contract or customer-facing status impact. No native Horizon-to-LatidoFlow integration is claimed.

Layer-by-layer comparison

Different control planes, with deliberate overlap at job health

An empty cell would hide the distinction, so each row states the boundary directly.

Decision area LatidoFlow Laravel Horizon
Primary role External acceptance and incident layer for recurring jobs, heartbeats, and HTTP uptime. Dashboard and worker-management layer for Laravel queues powered by Redis.
Queue visibility Receives lifecycle events for explicitly allowlisted job classes and can detect when a job reported as queued misses its start SLA. Shows queue and job throughput, runtime, wait time, failures, and job details within the Horizon dashboard.
Worker control Does not configure, scale, pause, or balance Laravel queue workers. Stores worker configuration in code and supports auto, simple, or no-balancing strategies.
Outcome proof Can reject a nominal success when reported numeric metrics fail configured assertions. The reviewed documentation covers queue operations and metrics; it does not document LatidoFlow-style business-output assertions.
Alerts Creates incidents from missed heartbeats, lifecycle acceptance failures, output failures, and uptime failures, then records delivery attempts. Can route mail, Slack, or SMS notifications when queue wait time exceeds configured thresholds.
Public communication Can publish component health and on-page incident updates to a public status page. The reviewed Horizon documentation describes an authorized operations dashboard, not a public customer status page.
Deployment Runs as a separate service receiving monitored signals. Installed and operated with the Laravel application; requires Redis and is not currently compatible with Redis Cluster.
Software price and activation A free workspace is available. Paid self-service activation is not complete; plan limits cover monitor capacity and evidence retention. The official package is MIT licensed with no package license fee; teams operate its Redis, workers, dashboard access, and metric snapshots.
Installation boundary Direct HTTP ingestion is established. The repository Laravel package has not been verified as a current public clean install. Horizon is an official Composer package documented and distributed by Laravel.

Use Horizon alone when

Redis queue operations are the requirement

  • You need to configure and balance queue workers from version-controlled Laravel configuration.
  • Throughput, runtime, failures, and job or queue wait time are the primary diagnostic signals.
  • Your team can operate the package, Redis dependency, protected dashboard, and scheduled metric snapshots.

Use LatidoFlow alone when

You do not need a queue control dashboard

  • A heartbeat or direct HTTP lifecycle signal is enough to prove a recurring process ran.
  • Output assertions, incidents, uptime checks, and a status surface matter more than queue balancing.
  • The monitored work may include services that are not backed by Laravel Redis queues.

Use both when

Critical jobs need operational depth and acceptance proof

  • Horizon should run and explain the queue while LatidoFlow independently evaluates selected business workflows.
  • A queue wait alert and a job start-SLA incident answer different operational questions.
  • Customer-visible component health should reflect more than the HTTP endpoint alone.

Practical pairing

Give each layer one job.

This architecture is a suggested operating pattern, not a claimed product integration.

  1. 1

    Operate the queue with Horizon

    Configure Redis workers, supervisors, balancing, retry behavior, and queue wait thresholds in the application.

  2. 2

    Define acceptance in LatidoFlow

    Allowlist only the business-critical job classes that need queued, started, succeeded, or failed lifecycle evidence.

  3. 3

    Validate the result

    Attach finite numeric metrics to success events when exit status alone cannot prove the expected business outcome.

  4. 4

    Route the incident

    Use the LatidoFlow incident and status surface for a missed start, missing completion, failed output rule, or related uptime failure.

Cost and ownership

Horizon has no package license fee, but it is not zero-operation.

The official Horizon package is MIT licensed. Your team still runs Redis, secures dashboard access, operates worker processes, handles deployments, and schedules metric snapshots. LatidoFlow is separately priced by its product plans and runs outside that queue control plane.

Boundaries to confirm

Neither product covers every monitoring layer.

Horizon requires Redis and the Laravel 13.x documentation says it is not currently compatible with Redis Cluster. LatidoFlow does not manage queue workers or inspect Redis internals; its lifecycle path covers only explicitly allowlisted job classes and its public status page does not currently send subscriber email updates. Paid self-service activation is incomplete, and the repository Laravel package has not been verified as a public clean install; direct HTTP ingestion remains available.

Official sources

Keep exploring

Laravel queue monitoring Review LatidoFlow lifecycle signals and their current limits. LatidoFlow vs Laravel Nightwatch Compare completion proof with broad Laravel telemetry. Job dispatched, never started Inspect the reproducible start-SLA failure scenario.

Keep Horizon in control. Add proof only where it matters.

Start with one allowlisted business-critical job and verify whether its queue lifecycle and output evidence improve incident decisions.

Create account Read the docs