Laravel monitoring

Laravel monitoring that tells one story, not five.

Most teams glue together an uptime checker, an error tracker, a cron monitor and a security scanner. nopanic puts them in one timeline, so the outage, the exception behind it and the line of code that caused it show up together.

Uptime and response checks every minute

nopanic requests every site every 60 seconds, follows redirects, and supports basic auth and custom headers for staging and protected apps. You hear about downtime before your client does.

Exceptions with the context to fix them

Install the nopanic/laravel package and every exception arrives grouped, with its stack trace, request and the release it appeared in. Assign, snooze or resolve it, and share a read-only link with the client.

Scheduled tasks that cannot fail quietly

The package syncs your Laravel scheduler, so a command that stops running or runs late raises an alert. Jobs outside Laravel report in with a simple ping url.

Certificates, security and status in the same view

Expiring SSL certificates, vulnerable code and public status pages live next to uptime and errors. One dashboard per client, one portfolio view for the whole agency.

Frequently asked questions

How is nopanic different from Laravel Nightwatch, Sentry or Oh Dear?

Those tools each cover one part of the picture. nopanic combines uptime, errors, debugging, scheduled tasks and security in one platform, organised per client, and stores everything in the EU.

Which Laravel versions are supported?

The nopanic/laravel package supports every Laravel version that still receives security fixes. Uptime, SSL and ping monitoring work for any site, Laravel or not.

Can I move over from Oh Dear?

Yes. nopanic imports your sites and status pages from Oh Dear, so you can switch without setting everything up again.

All of this for every client site, in one place.

Monitoring, errors, debugging and security for every Laravel app you run. Hosted and processed in the EU.