Migration guide

Migrating from BugSnag to Quiet Guard

BugSnag hooks in through a Monolog channel you add to your logging stack. Our package auto-discovers itself. Here is the mapping, and what the move costs you.

Identifiers read on August 23, 2026 from the official BugSnag documentation. See the source

What you lose

In this order, because this is the part to read before deciding. Quiet Guard is a narrower tool. If you use even one of these, stay where you are:

There is no performance tracing, and no transaction sampling
There is no profiling
There is no session replay
There is no browser or mobile SDK: capture is server-side, in PHP
There are no source maps, for want of a browser SDK
The product is young, and its integrations amount to three: mail, Slack, webhook

What you gain

What comes in exchange. The lines marked included are on every plan, Free among them; encrypted storage and application logs belong to the paid ones:

The data stays in France, and the host is named in the legal notice
End-to-end encryption as an option: messages and traces are sealed with your team's key and decrypted in your browser
Application logs in the same tool as the exceptions, shown around the incident
Your composer.lock checked against the Packagist advisories, included
Dead man's switch monitoring for scheduled tasks, included
Uptime, SSL expiry and a public status page, included
Unlimited projects, and seats by plan, one on Free, three on Indie, unlimited on Studio: you pay for event volume and nothing else

The move, in three steps

01

Install alongside, not instead

Both packages coexist. Install ours, leave the existing channel in your logging stack, and compare what each reports for a few days.

02

Carry the configuration across

There is less to do on our side: no service provider to register and no channel to add to your logging config. The package is auto-discovered.

03

Remove the old one

Uninstall the package, take the channel out of your logging stack, drop the provider, then the config file and the API key.

What is comparable

Read from the official pages on the date shown, and limited to what they state. A row saying "not stated" means the page consulted does not say, not that the answer is no. See the source

	On BugSnag	On Quiet Guard
Error retention	60 days in the comparison table; 7 days stated in a footnote for the free tier	7 days on Free, 30 on Indie, 90 on Studio
Data hosting	Not stated on the page consulted	France, OVH SAS in Roubaix

The configuration, side by side

The left column was read from the official documentation on the date shown. Check it: it may have moved since.

On BugSnag	On Quiet Guard
`bugsnag/bugsnag-laravel`	`quiet-guard/laravel-monitor`
`BUGSNAG_API_KEY`	`MONITOR_URL MONITOR_KEY`
`config/bugsnag.php`	`config/monitor.php`
`php artisan vendor:publish`	`php artisan vendor:publish --tag=monitor-config`
`config/logging.php (channels.bugsnag)`	No equivalent, and none needed
`bootstrap/providers.php (BugsnagServiceProvider)`	No equivalent, and none needed

Start for free

No card required. Up and running in minutes.

Coming from somewhere else? Sentry Flare