Migrating from Flare to Quiet Guard
Flare asks you to remove Ignition before it installs. Our package never touches it: you keep your local error page. Here is the mapping, and what the move costs you.
Identifiers read on August 23, 2026 from the official Flare 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, and Flare also does performance monitoring. 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
- Projects and seats follow the plan, from one each on Free to unlimited on Studio: you pay for event volume and nothing else
The move, in three steps
Install alongside, not instead
Both packages coexist. Install ours, leave yours in place, and compare what each reports for a few days.
Carry the configuration across
Two variables instead of one, because you choose the server that receives. Everything else has a default.
Remove the old one
Uninstall the package, delete its config file and its key. If you removed Ignition to install Flare, you can put it back: our package does not replace it.
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 Flare | On Quiet Guard | |
|---|---|---|
| Error retention | 30 days, on every plan | 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 Flare | On Quiet Guard |
|---|---|
spatie/laravel-flare |
quiet-guard/laravel-monitor
|
FLARE_KEY |
MONITOR_URL
|
config/flare.php |
config/monitor.php
|
php artisan vendor:publish --provider='Spatie\LaravelFlare\FlareServiceProvider' |
php artisan vendor:publish --tag=monitor-config
|
composer remove spatie/laravel-ignition |
No equivalent, and none needed |
php artisan flare:test |
No equivalent yet |
No card required. Up and running in minutes.