The Problem With Per-Event Monitoring Billing
Most hosted Laravel monitoring tools share the same pricing model: you pay by event volume, and retention is gated behind higher tiers. That works fine when traffic correlates with revenue, but for ERPs, internal tools, content sites, and agency client apps, it creates a mismatch. More traffic means a bigger bill, with no corresponding increase in what you can afford to pay.
Retention compounds the problem. Some of the hardest production bugs are not outright failures — they are successful requests that produced the wrong business outcome. Those issues often surface weeks or months after the fact, when a customer reports them. At that point you need the full history: requests, jobs, queries, logs. When history is a pricing tier, keeping more of it means paying more.
What NightOwl Does Differently
NightOwl builds on the official laravel/nightwatch package and redirects its telemetry into a PostgreSQL database you control. Because the data lives on your own infrastructure, retention becomes a storage decision rather than a billing one. Pricing stays flat regardless of traffic volume.
Pricing Tiers
- Hobby — $5/month, single app
- Agency — $69/month, unlimited client apps, no per-event fees
- Self-hosted license — ingestion pipeline and dashboard both run on your own infrastructure, for teams with strict data-residency or GDPR requirements
There is a 14-day free trial available at usenightowl.com.
How the Pipeline Works
Setup is intentionally minimal. You install the NightOwl agent (an open-source package) alongside laravel/nightwatch, point the telemetry destination at your Postgres instance, and the dashboard reads from there.
composer require lemed99/nightowl-agent
Because telemetry is consumed by a handful of engineers rather than millions of end users, it rarely needs cloud-scale infrastructure. The pipeline is designed to be efficient: benchmarks show a single PostgreSQL instance handling 13,400+ payloads per second. Real-world usage reported by NightOwl users ranges from ~300k requests per day up to ~8M requests per day on the same architecture.
Who It Is Built For
- Agencies managing multiple client Laravel apps who want one flat monthly cost
- ERP and internal tool teams where event volume is high but does not map to revenue
- Teams under GDPR or data-residency contracts that cannot send telemetry to third-party cloud services
- Any team that needs months of retention without paying a premium for it
Maturity and Transparency
NightOwl is a new tool. Development started in late 2025 for internal use and the public release came in May 2026. The agent package is open source on GitHub, and there is a live demo you can browse before signing up.
Key Takeaways
- Telemetry is stored in your own PostgreSQL database — no third-party data custody
- Pricing is flat and traffic-independent, from $5 to $69/month
- Retention is bounded by disk space, not a billing tier
- Built on top of the official
laravel/nightwatchpackage - A self-hosted license is available for full on-premises deployments
- The ingestion pipeline is benchmarked at 13,400+ payloads/second on a single instance
- Open-source agent; live demo available
Source: Laravel monitoring that doesn't bill you by your traffic — Laravel News
