Introduction

Quiet Guard is a standalone Laravel application that gives small teams a single cockpit for the health of their production apps. It centralises exceptions and application logs, alerts the team when something breaks, scans dependencies for known vulnerabilities, and follows a project's GitHub activity, all in one Laravel-first, EU-hosted tool.

The unique combination

Most tools do one thing. Quiet Guard brings four signals together in the same place, correlated around your projects:

• Exceptions: every error your app throws, grouped into deduplicated issues with full occurrences, stack traces and release context.
• Application logs: your Log:: lines, shipped in batches and searchable next to the exceptions they explain.
• Dependency security: a snapshot of your composer.lock checked against Packagist security advisories, with findings raised the moment a vulnerable package lands.
• GitHub activity: synced commits, pull requests and branches, so an exception's release can be mapped back to the exact commit that shipped it.

That combination is the point: an error, the logs around it, the dependency that may have caused it, and the commit that introduced it, one screen, one team.

Laravel-first and privacy-friendly

• Built for Laravel. The server is Laravel 13 + Filament 5; the reference client is a Composer package that drops into any Laravel app. Framework-agnostic clients (PHP core, Symfony, WordPress) reuse the same neutral ingestion API.
• EU-hosted. Positioned as a privacy-friendly, GDPR-conscious alternative to US-hosted error trackers.
• Zero-knowledge options. Sensitive content can be encrypted at rest with a key only your team holds, and DB/file backups can be stored as opaque blobs the server can never read. See Encrypted storage and Encrypted backups.

Who it's for

Quiet Guard targets Laravel agencies, freelancers and small teams who want the visibility of Sentry/Bugsnag/Flare without per-seat pricing or a US data home. Billing is by event volume per team, projects are unlimited, and the number of seats follows the plan: one on Free, three on Indie, unlimited on Studio.

How it's structured

The server is multi-tenant: the Team is the tenant. Each team owns its projects, and every project authenticates its monitored application with a per-project API key. A platform-neutral ingestion API (/api/v1/ingest for exceptions, /api/v1/logs for logs, /api/v1/dependencies for the lock file) accepts data from any of the client packages.

The dashboard end users work in is served at /app: it is the tenant (team) surface, and everything below happens there.

This documentation covers the server itself. Looking for how to send data from your app? Head to the Laravel SDK, PHP Core, Symfony Bundle or WordPress Plugin sections, depending on your stack, or read the Ingestion API reference if you are integrating a client by hand.

Next: Getting started walks you through creating a team, a project and your first API key.