03:12
Two hundred lines in a log file
A payment call times out and a customer sees a white page. Your log fills up with the same error, in a file nobody reads at three in the morning.
QuietGuard Beta, on approval
Know what broke, where, and whether it came back.
Try Quiet Guard
Laravel 11, 12, 13 · PHP 8.2+ · Free during the beta
Highlights.
03:12
One issue, not two hundred
Identical exceptions share a deterministic fingerprint built from the project, the class, the file and the normalised path. The burst lands at the top of the triage as a single issue.
03:13
The alert reaches your channel
Mail, Slack or webhook, for a new issue or a regression, with storm protection so a loop does not wake the whole team.
09:40
You read the trace, you fix it
The frame that threw, the request context and the release it ran on. You deploy the fix; the fingerprint survives the deployment, so the issue does not split in two.
Three weeks later
It comes back, and the issue reopens
A regression does not open a new ticket. It reopens the issue you already know, with its history and its occurrences.
Real screens of Quiet Guard, on a demo project.
Error tracking
Two hundred errors. One issue.
Identical exceptions share a deterministic fingerprint built from the project, the class, the file and the normalised path. The group survives your deployments, and a fixed bug that returns reopens its issue instead of opening a new one.
Diagnosis
The full trace. And its context.
Class, message, file and line, the full stack trace with vendor frames folded, the request context and the release it ran on. Sensitive values are masked on your own server before anything is sent.
Monitoring
Everything else. Watched too.
Error tracking is where it starts. Logs, uptime, heartbeats, dependencies and backups are part of the product, not add-ons to buy later.
When something breaks
- Exceptions
- Every reported exception is captured with its class, message, file, line, full stack trace and request context.
- Application logs
- Opt-in forwarding above the PSR-3 level you choose, buffered and sent in a single call at the end of the request.
- Uptime and SSL
- An HTTP probe every five minutes, latency history, certificate expiry warnings and a public status page.
While nothing does
- Heartbeats
- Scheduled tasks watched as dead man's switches: a cron that stops pinging raises an alert before your client notices.
- Dependencies
- Your composer.lock checked against Packagist advisories, with an alert when a package turns vulnerable.
- Encrypted backups
- A zero-knowledge vault: the dump is encrypted on your server with your team key, and we only ever store the result.
Encryption
Your data. Sealed with your key.
Messages, contexts and traces are sealed with your team key and opened in your browser. Backups are encrypted on your server before they leave it. The trade-off is stated plainly: a lost passphrase makes encrypted backups unrecoverable, for us as well.
- Team key seals messages, contexts and traces
- Zero knowledge backups encrypted before they leave your server
- France where the encrypted result is stored
AI assistants
Ask your assistant. It only reads.
A read-only MCP server lets Claude, Cursor or any MCP client list your projects and issues, read a stack trace, availability and vulnerabilities once you sign in. Nothing writes: no issue is resolved, ignored or assigned. Application logs and request contexts stay out of reach, and a sealed project answers with metadata only.
claude mcp add --transport http quiet-guard https://quietguard.dev/mcpTools
list-projectsget-projectlist-issuesget-issueget-stack-traceget-availabilitylist-vulnerabilities
Installation
Three variables. Then it watches.
Add the Composer package and set three variables. Every reported exception is captured without touching your own logging, and a network error on our side never reaches your app.
$ composer require quiet-guard/laravel-monitor
MONITOR_ENABLED=true
MONITOR_URL=https://quietguard.dev
MONITOR_KEY=lm_xxxxxxxxxxxxxxxxxxxx- Install the package Add the Composer client to the application you want to watch. The service provider and the Monitor facade are auto-discovered.
- Set three variables Take the project key from the dashboard, it is shown once, and drop it into your .env alongside the URL.
- Let capture do the rest An additive reportable() callback sends every reported exception without touching your own logging. A network error on our side never reaches your app.
Sensitive values, passwords, tokens, cookies, authorization headers, and anything shaped like an email, an IBAN or a card number, are masked on your own server, before anything is sent.
Pricing
0 €
The free plan. And everything, during the beta.
The free plan watches one project with 5,000 events a month, 7 days of retention and one member, with uptime, heartbeats, mail alerts and dependency scanning included. While the beta lasts, approved teams get every feature at no cost.
- 1 project
- 5,000 events a month
- 7 days of retention
- 1 member
When you need more
-
Solo
9 € per month, excl. VAT
3 projects · 50,000 events a month · 30 days of retention · logs, Slack, GitHub, MCP
-
Indie
19 € per month, excl. VAT
Unlimited projects · 200,000 events a month · 60 days of retention · 3 members · 5 GB of encrypted backups
-
Studio Recommended
49 € per month, excl. VAT
Unlimited projects and members · 1 million events a month · 90 days of retention · 20 GB of encrypted backups
These prices apply once the beta ends. Yearly billing gives two months free. See every plan
Why Quiet Guard? For all of this.
-
1
issue per error, however many times it happens
-
5min
between two uptime probes, with latency history and a public status page
-
3
variables to install it
-
Cron
scheduled tasks watched: one that stops pinging raises an alert before your client notices
-
20GB
of backups encrypted on your server before they leave it, on the Studio plan
-
0
sensitive value sent: passwords, tokens, IBANs and card numbers are masked on your server
-
France
for hosting, errors and backups alike
-
Packagist
security advisories checked against your composer.lock, with an alert when a package turns vulnerable
-
MCP
a read-only server for your AI assistant
Details
What your application needs, and how the client behaves once it is installed. Every option is covered in the documentation.
- Requires
- Laravel 11, 12 or 13, on PHP 8.2 or later
- Capture
- Additive and fail-safe; synchronous by default, queued if you prefer
- Teams
- Multi-team: each team owns its projects, issues, logs and API keys
- Alerts
- Mail, Slack or webhook, with storm protection and in-app notifications
- Encryption
- Messages, contexts and traces sealed with your team key, opened in your browser
- Trade-off
- A lost passphrase makes encrypted backups unrecoverable, for us as well
- AI assistants
- Read-only MCP server, with OAuth sign-in
Which tool do you need?
QuietMetrics
Privacy-friendly web analytics
Server-side analytics for PHP, with no tracking cookies.
Beta, open- No identifying or tracking cookies
- Server-side tracking: three Composer packages
- One dashboard, nothing to configure
QuietGuard
Monitoring, error tracking and backups
Exceptions, logs, uptime and backups in one cockpit.
Beta, on approval- One error, one issue: deterministic grouping
- Stack trace, request context, release
- Application logs, batched and opt-in
Try Quiet Guard
You are on this page