Requizon vs Laravel Nightwatch

Laravel Nightwatch is Laravel's hosted monitoring service. You install its package, run its agent, and it sends requests, queries, jobs, exceptions, logs and outgoing HTTP requests to a dashboard run by Laravel. Outgoing requests are one page of it. Requizon only does outgoing requests, so this page compares Requizon with that one page, and it is worth saying at the start that the rest of Nightwatch has no counterpart in Requizon at all.

One page of an APM, or a whole tool for one question#

Nightwatch's strength is the trace. Every event belongs to the request, command or scheduled task that caused it, so a slow checkout page opens onto the queries, cache calls and outgoing requests inside it, in order. If your question is "why was this request slow", that is the view you want, and Requizon cannot give it to you.

Requizon starts from the other end. It files every call under the API it went to, then the host, then the path, and keeps hourly statistics for a year. Its question is "how has Stripe been behaving since Tuesday", asked of every dependency at once.

At a glance#

Where the records differ#

Calls that never got a response#

Nightwatch's HTTP client middleware records a call when its response arrives. In laravel/nightwatch 1.30, the current release as we write this, a transfer that ends without a response adds nothing to the outgoing requests page: a timeout, a refused connection, a failed DNS lookup or a TLS error. The source marks recording those as a to-do, so this may change. Until it does, the ConnectionException can still reach Nightwatch as an exception, provided your code lets it be reported rather than catching it.

Requizon hooks Guzzle's on_stats callback, which fires for those transfers too. They are stored as connection_error with the cause, and they count against the API's success rate like any other failure.

Errors inside a 200#

Some APIs answer 200 OK with {"errorCode": 42} in the body. Nightwatch records the status code, so those calls count as successful. Requizon lets you register one callback that reads the decoded body and returns a message when the call failed, and the call is then stored as an application_error. The callback only runs if you register it, since it means reading every successful body.

Grouping below the host#

Nightwatch's list is one row per host, and opening a host lists its individual requests with status and duration. Requizon adds two levels. Several hosts can be one named API (api.stripe.com and files.stripe.com as stripe), and each host breaks down into paths with IDs replaced, so /v1/orders/8134/items and every other order's equivalent share the row /v1/orders/:id/items and its chart.

Sampling#

Outgoing requests in Nightwatch have no sample rate of their own. They are kept when the request, command or scheduled task that made them is sampled, and Nightwatch's documentation recommends starting new applications at a request sample rate of 0.1 or lower. At that rate, the calls your web requests make are a one-in-ten sample. That is fine for spotting a slow host and less fine for "did every webhook to our partner go through". Requizon records every transfer, and it stays cheap at that volume because the dashboard reads hourly rollups rather than the raw rows.

When Nightwatch is the better choice#

• You want one tool, not several. Nightwatch covers exceptions, slow queries, jobs and outgoing requests together, correlated. Requizon is a second dashboard for one part of that.
• You need to know which request made the call. Requizon records the call, not its context. It cannot tell you that the slow Stripe call happened inside POST /checkout.
• You want alerting. Requizon has none. It is a dashboard you look at.
• You would rather not host the data. Requizon's tables live in your database and grow with your traffic, bounded by its pruning. Nightwatch stores nothing on your side.
• You are on Laravel 10 or 11, or not on MySQL. Requizon needs Laravel 12 or later and MySQL 8.0.20+ (or a compatible MariaDB) for its rollup query. Nightwatch has no database requirement in your app.

What each costs, and where the data goes#

Nightwatch bills by event, and every outgoing request is an event, alongside every query, cache call and job in the same traces. As of September 2026 the free plan includes 300,000 events a month with 14 days of history, Pro is $20 a month for 7.5 million events and 30 days, Team is $60 for 30 million and 60 days, and Business is $300 for 180 million and 90 days. Sampling and spending caps are how you keep that bill predictable, which is part of why sampling is the recommended default.

Requizon is a single payment per application, and it has no quota because there is nobody to send the data to. It writes to three tables in your database and serves its dashboard from your app. That matters most when the traffic itself is sensitive, for example calls to a payment or health data provider that your contracts do not let you forward to a third party.

Running both#

Nightwatch and Requizon both register global middleware on Laravel's HTTP client, neither modifies the request, and each records the same call into its own storage. A reasonable split is Nightwatch for the application and Requizon for the history of each dependency. Push Requizon's Guzzle middleware onto any SDK client you have already given Nightwatch::guzzleMiddleware(), and both tools will see those calls as well.