Flare

What Is Flare?

Picture this: a Laravel developer at 11pm, staring at a Sentry dashboard full of PHP errors stripped of context. The stack trace shows a failed Eloquent query, but nothing about which route triggered it, which queued job was running, or what the authenticated user was doing. Adding custom context means writing Sentry-specific instrumentation code across dozens of files. There has to be a better way.

Flare exists because the Spatie team — creators of over 400 open-source Laravel packages — hit this exact frustration repeatedly. They knew what context Laravel developers actually need when debugging production errors. So in 2019, they built an error tracker that captures it automatically.

Headquartered in Antwerp, Belgium, Flare is purpose-built for Laravel and PHP. Not "supports PHP among 30 other languages" — exclusively Laravel and PHP. This narrow focus is simultaneously its greatest strength and its most significant limitation. Every feature, every UI element, every piece of contextual data is designed around how Laravel applications actually work.

Flare's companion product, Ignition, is the open-source error page that ships with every Laravel installation. When your local dev environment throws an exception, Ignition renders the beautiful, context-rich error page you're used to seeing. Flare is the hosted service that brings that same depth of context to production error monitoring. The relationship means Flare understands Laravel's internals at a level no generic error tracker can match.

Key Features

Deep Laravel Context in Every Error

Generic error trackers capture a stack trace and maybe some request headers. Flare captures everything a Laravel developer needs: the full request payload, route parameters, authenticated user details, middleware stack, session data, Git commit hash, and deploy version. For queued jobs, Flare records the job class, payload, connection, and queue name. For Livewire components, it captures component state and method calls. This context arrives automatically — no custom instrumentation required. The difference between debugging with Flare versus a generic tracker is the difference between a medical chart and a list of symptoms.

AI-Powered Error Solutions

Flare analyses each error against its knowledge of Laravel's codebase, common pitfalls, and version-specific quirks. When an error arrives, the AI suggests potential fixes tailored to your specific Laravel version and the exact context of the failure. A "Class not found" error after a Composer update gets different suggestions than the same error in a fresh installation. The suggestions are not always correct, but they're often a useful starting point — particularly for less experienced developers encountering framework-specific errors for the first time.

Error Grouping and Noise Reduction

Production Laravel apps generate repetitive errors. Flare groups identical errors intelligently, tracking occurrence counts, first and last seen timestamps, and affected user counts. You can mark errors as resolved, and Flare will reopen them if they recur after a new deploy. Notification rules let you filter by error severity, occurrence threshold, and environment. This keeps alert fatigue manageable, which matters when you're monitoring multiple Laravel projects from a single dashboard.

Ignition Integration

The seamless handoff between local and production debugging is underappreciated. During development, Ignition shows rich error pages with runnable solutions — click a button to create a missing migration, fix a namespace, or clear a cache. In production, Flare captures the same level of detail remotely. Developers who are already familiar with Ignition's interface adapt to Flare's production dashboard instantly. Zero learning curve for existing Laravel teams.

Team Collaboration

Flare supports team-based error management with assignments, status tracking, and project-level access controls. Errors can be assigned to specific team members, tagged with custom labels, and filtered by status. Slack, Discord, Telegram, and Microsoft Teams notifications keep the right people informed without requiring everyone to watch the dashboard. For agencies managing multiple client Laravel projects, the multi-project dashboard provides a consolidated view.

Pricing

Flare's pricing is refreshingly simple. The free tier covers a single project with limited error volume — enough to evaluate the platform on a staging environment or low-traffic application. Pro starts at EUR 9 per month per project with unlimited errors, AI solutions, and team collaboration. Business at EUR 29 per month per project adds priority support, advanced error grouping, and extended data retention.

Per-project pricing means costs scale linearly. A solo developer with one production Laravel app pays EUR 9 monthly. An agency with ten client projects pays EUR 90. This model is transparent and predictable, unlike volume-based pricing that can spike unexpectedly during traffic surges.

Compared to Sentry's Developer plan (free for one user) and Team plan ($26 per month for the organisation), Flare is cheaper for small teams with few projects but potentially more expensive for larger organisations managing many applications. The trade-off is depth versus breadth: EUR 9 buys Laravel-specific intelligence that Sentry's PHP integration cannot match.

Annual billing reduces the per-month cost. Spatie also offers bundle discounts for teams purchasing multiple Spatie products.

EU Compliance & Privacy

Flare inherits Spatie's Belgian legal domicile. As a Belgian entity (Spatie BVBA) headquartered in Antwerp, Flare operates entirely under EU jurisdiction. All error data is stored and processed in EU-based infrastructure with no data transfers to non-EU countries required.

Error reports can contain sensitive data — user emails, request payloads, session tokens. Flare provides scrubbing tools to strip sensitive fields before data leaves your server. A Data Processing Agreement is available for organisations that require formal GDPR documentation.

For Laravel teams in regulated industries — fintech, healthtech, e-government — Flare's Belgian hosting and EU jurisdiction provide compliance clarity that US-based error trackers require lengthy legal review to achieve.

Who It's Best For

Laravel development teams of any size, from solo developers to agencies managing dozens of client projects. The one-line Composer installation and automatic context capture eliminate setup friction entirely.

Spatie ecosystem users already relying on Spatie packages benefit from a unified vendor relationship and consistent quality expectations across their toolchain.

Budget-conscious small teams where EUR 9 per month per project is a meaningful price advantage over enterprise-priced monitoring platforms with features they'll never use.

EU-regulated Laravel projects in fintech, healthtech, or government where Belgian jurisdiction and EU data hosting simplify compliance conversations with legal and security teams.

The Verdict

Flare makes one bet: that Laravel developers are better served by a tool built specifically for them than by a generic platform that treats PHP as one language among many. That bet pays off handsomely for its target audience. The context capture is exceptional, the AI solutions are genuinely useful, and the pricing respects small-team budgets. The cost of this focus is brutal exclusivity. Non-PHP projects need not apply. Teams with polyglot stacks cannot consolidate their error tracking here. For Laravel-only shops, though, Flare is the most productive error tracking tool available — and it happens to be built in the EU.

Frequently Asked Questions

Does Flare work with plain PHP or only Laravel?

Flare provides basic PHP support, but its core value — automatic context capture, route data, queue job details, Livewire state — requires Laravel. Plain PHP projects would get a significantly reduced feature set. For non-Laravel PHP, a general-purpose error tracker is a better fit.

How does Flare compare to Sentry for Laravel projects?

Flare provides richer Laravel-specific context automatically: route parameters, queue payloads, Livewire component state, and Git deploy data. Sentry offers broader capabilities including performance monitoring, frontend error tracking, and multi-language support. For pure Laravel error tracking, Flare is deeper. For full-stack observability, Sentry covers more ground.

Is Flare maintained by the same team as Spatie packages?

Yes. Flare is built and maintained by Spatie BVBA, the Antwerp-based company behind over 400 open-source Laravel packages. The same team that builds laravel-permission, laravel-medialibrary, and dozens of other widely-used packages maintains Flare.

Can Flare handle high error volumes in production?

Yes. The Pro and Business plans support unlimited errors. Flare's error grouping and deduplication prevent dashboard overload from repetitive errors. Notification rules let you set occurrence thresholds to avoid alert fatigue during incident spikes.

Where is Flare's error data stored?

All error data is stored and processed in EU-based infrastructure. Spatie is a Belgian company operating under EU jurisdiction. No data transfers to non-EU countries are required for the service to function. A Data Processing Agreement is available for GDPR compliance documentation.