A powerful and easy to configure uptime and ssl monitor
1.1k
Stars
179
Forks
1
Open issues
30
Contributors
AI Analysis
Laravel-uptime-monitor is a Laravel package for monitoring website uptime and SSL certificate expiration, sending notifications via Slack, email, Telegram, or other Laravel notification channels when sites go down or certificates expire soon. It serves Laravel applications that need built-in uptime monitoring without external dependencies, and is best suited for developers and DevOps teams managing multiple web properties within a Laravel ecosystem.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Laravel-native uptime and SSL monitor for teams already in the Laravel ecosystem
Laravel-uptime-monitor is a PHP package that monitors website availability and SSL certificate expiration within Laravel applications. It leverages Laravel's native notification system to alert via Slack, email, or custom channels. Built by Spatie, a respected Laravel library publisher, it targets Laravel developers seeking integrated monitoring without external SaaS dependencies. Real-world adoption appears concentrated within the Laravel ecosystem; mainstream adoption data is not publicly available.
Created by Spatie in September 2016, the package emerged as Laravel monitoring needs grew. A standalone version (uptime-monitor-app) was later released for non-Laravel users. The project has remained actively maintained over a decade with periodic updates reflecting ecosystem changes.
The project has accumulated 1,071 stars and 180 forks, indicating moderate adoption within Laravel communities. No meaningful growth in the last 7 days (0 stars gained) suggests a stable, matured project rather than explosive adoption. Growth likely plateaued after capturing its core audience of Laravel developers seeking an integrated monitoring solution.
Adoption not verified. README mentions a standalone app variant and references extensive documentation, suggesting intentional deployment use cases, but no case studies, deployment counts, or enterprise adoption metrics are publicly documented. The modest star count relative to peer Spatie projects (laravel-backup has 6,005 stars) may indicate either specialized niche adoption or limited visibility.
Based on README, the package follows Laravel conventions: configuration-driven setup, event-based notifications, pluggable response checkers for validation, and concurrent HTTP request handling (up to 10 concurrent checks configurable). Appears to use Guzzle for HTTP operations and Laravel's queue/notification system for async work. Likely follows Laravel service provider patterns for configuration and dependency injection.
README includes GitHub Actions workflow badge indicating automated testing infrastructure exists, but specific coverage metrics are not documented in the README excerpt.
Last push on 2026-06-26 (7 days before analysis date) indicates active maintenance. The project maintains CI/CD workflows and continues to accept updates. This signals ongoing support, though the absence of recent star growth suggests a mature, stabilized project rather than rapid development.
ADOPT IF: you are a Laravel team that wants lightweight uptime+SSL monitoring without external SaaS, prefer configuration-over-code setup, and can run checks from a single location. AVOID IF: you need global distributed probing, multi-location redundancy, advanced analytics, UI dashboards, or support for non-HTTP protocols. MONITOR IF: you are evaluating Laravel monitoring tools and need to verify whether Laravel/Pulse or similar first-party tools have addressed this use case in newer Laravel versions.
Independent dimensions
Mainstream potential
3/10
Technical importance
5/10
Adoption evidence
3/10
- Single-location checking: no global distribution of probe endpoints means blind spots in regional connectivity or CDN-edge issues.
- Laravel dependency lock-in: only usable within Laravel applications; teams moving away from Laravel or using polyglot stacks cannot reuse it.
- UI/dashboard gap: the package provides no built-in dashboard; teams need custom interfaces or external tools to visualize historical data and trends.
- Adoption opacity: public real-world usage data is unavailable, making it difficult to assess production reliability or community support depth.
- Comparison to official tools: Laravel/Pulse is first-party and receives more investment; adoption of Pulse may erode demand for third-party monitoring packages.
Laravel-uptime-monitor will likely remain a stable, low-growth maintenance project serving a permanent niche of Laravel teams seeking integrated self-hosted monitoring. It may face gradual pressure from Laravel's first-party offerings (Pulse) and modern observability platforms but will persist as long as Laravel teams value lightweight, configuration-driven tooling.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- PHP
- License
- MIT
- Last updated
- 2w ago
- Created
- 120mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Open pull requests
Top contributors
Recent releases
Similar repos
spatie/laravel-failed-job-monitor
This Laravel package automatically sends notifications (via mail and Slack)...
spatie/laravel-backup
A Laravel package that creates automated backups of your application (files and...
louislam/uptime-kuma
Uptime Kuma is a self-hosted monitoring tool that tracks the availability of...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
1.1k | — | PHP | 8/10 | 2w ago |
|
|
1k | — | PHP | 8/10 | 1mo ago |
|
|
6k | — | PHP | 8/10 | 1w ago |
|
|
1.7k | — | PHP | 8/10 | 3d ago |
|
|
89k | — | JavaScript | 9/10 | 13h ago |
|
|
2k | — | PHP | 7/10 | 4w ago |
Uptime-kuma is a standalone, Docker-deployable monitoring platform (88,667 stars) with no Laravel dependency. It offers a full UI, multi-protocol monitoring, and works for any website. Laravel-uptime-monitor is Laravel-only, config-driven, and integrates with Laravel notifications. Kuma suits polyglot teams; Laravel-uptime-monitor suits Laravel teams avoiding external SaaS.
Pulse (1,698 stars) is Laravel's official application performance monitoring tool focused on application-level metrics and real-time dashboards. Laravel-uptime-monitor focuses on external URL availability and SSL cert checks. They are complementary, not competing.
Laravel-backup (6,005 stars) is a Spatie package with 5.6× more stars, suggesting broader adoption. Both are configuration-driven Laravel monitoring tools. Backup monitoring is a more universal need than uptime monitoring, likely explaining the gap.
Failed-job-monitor (1,047 stars) is nearly identical in adoption and scope to laravel-uptime-monitor. Both are niche monitoring packages for Laravel-specific concerns with similar user bases.
Commercial uptime monitoring services offer global probe networks, advanced analytics, and multi-team collaboration. Laravel-uptime-monitor is self-hosted, single-location, and suited for simple use cases or teams preferring zero external dependencies.
