Laravel Skyline, compared
Four tools, one dashboard path, and a great deal of confusion about which of them replaces what. Start
here: the table below says where each one sits relative to laravel/horizon,
because most of the wrong choices in this space are made by comparing tools that operate at different
layers.
What each one actually is
| Tool | Relationship to Horizon | Licence |
|---|---|---|
| Laravel Skyline | Forks and replaces the package | Annual subscription |
| Laravel Horizon | Skyline replaces the package | Free, MIT |
| Deck | Runs alongside Horizon | Free, MIT (optional paid Deck Cloud) |
| Horizon New Dawn | Replaces the Horizon interface | Free, MIT (pre-1.0) |
Read that column carefully before anything else. Deck runs beside Horizon and keeps history in your database; New Dawn swaps out Horizon's interface and leaves the workers alone; Skyline becomes your Horizon install and can change what the workers themselves do. Only one of those three is a like-for-like alternative to the others.
The comparisons
Skyline replaces the package
Laravel Skyline vs Laravel Horizon
Skyline is a fork of Horizon. Everything Horizon does still happens; the difference is what you can do about it.
Read the comparison →
Runs alongside Horizon
Laravel Skyline vs Deck
Deck records what your jobs did, in your database. Skyline changes what your queues do, in Redis. They answer different questions.
Read the comparison →
Replaces the Horizon interface
Laravel Skyline vs Horizon New Dawn
New Dawn replaces Horizon's interface and leaves the workers alone. Skyline replaces the package, workers included.
Read the comparison →
Every claim on these pages is checkable against the other project's own README or documentation, and we concede the points they win — there are several. If you find something out of date, tell us and we will fix it: these pages are only worth having if they are worth trusting.