Migration guide

Migrating from Sentry to Quiet Guard

One Laravel application, two Composer packages, and a line-by-line configuration mapping. Here is what the move changes, and above all what it costs you.

Identifiers read on August 23, 2026 from the official Sentry 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

One precision that half undercuts the first point, and belongs here: Sentry does offer a European region, in Frankfurt. The choice is final, and whichever region you pick, user accounts, organisation settings, access tokens and audit logs stay in the United States. So our argument is France, not Europe.

The move, in three steps

01

Install alongside, not instead

Both packages run together. Install ours, leave yours in place, and compare what each reports for a few days.

02

Carry the configuration across

The table below puts the identifiers side by side. There are fewer on our side, because there is less to set.

03

Remove the old one

Uninstall the package, delete its config file and its environment variables, and unhook it from the exception handler.

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 Sentry	On Quiet Guard
Error retention	30 days on Developer, 90 days on Team and above	7 days on Free, 30 on Indie, 90 on Studio
Data hosting	United States (Iowa) or European Union (Frankfurt), your choice, final	France, OVH SAS in Roubaix, no choice
Alert channels	15 entries in the Notification & Incidents category, including PagerDuty and Opsgenie	Mail, Slack and webhook, plus a bell in the app
Scheduled tasks	Succeeded, failed and missed; run duration is measured	Pending, healthy and overdue; duration is not measured
Uptime probe	1 to 60 minutes, several regions, alerts after three failures	Every 5 minutes, one point, alerts on the first change

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 Sentry	On Quiet Guard
`sentry/sentry-laravel`	`quiet-guard/laravel-monitor`
`SENTRY_LARAVEL_DSN`	`MONITOR_URL MONITOR_KEY`
`config/sentry.php`	`config/monitor.php`
`php artisan sentry:publish`	`php artisan vendor:publish --tag=monitor-config`
`Integration::handles($exceptions)`	No equivalent, and none needed
`SENTRY_TRACES_SAMPLE_RATE`	No equivalent, and none needed

Start for free

No card required. Up and running in minutes.

Coming from somewhere else? BugSnag Flare