Flare has got you covered in local development and production applications.
The ecosystem exists of 2 major components, seamlessly integrated.
Production grade error tracking
Flare is the online service you're looking at. Flare collects all your errors from staging and production projects and lets you work in a team to fix them. Try Flare now.
On this page
Open source error page for Laravel
Ignition is a free and shareable error page that ships by default with Laravel 6 and up, or can be installed manually from 5.5.
Its polished interface is built to keep you focused on finding a solution.
Learn everything about Ignition.
Teams & projects
Flare's organization is straight forward. You set up a team, invite members, and add your web applications to start tracking errors.
No feature limits
There is absolutely no limit on the amount of projects or members you add to a team. All features are available in all plans.
You can be a member of multiple teams, running on different plans. The project switcher lists all your projects, with an indication of the team it belongs to.
As team owner you'll assign admins that have total control, and members that can see
all projects and work with errors.
Do you have a outside contributor on one specific project? Add him as a guest.
Errors & occurrences
Flare tracks errors from your web applications, both locally and in production. Multiple occurrences of the same error will be bundled—with lots of options for in-depth investigation.
Multiple occurrences of the same error will be presented as a visual stack in the project overview, listing the amount of users impacted.
Errors can be resolved, deleted or snoozed (for a number of times or a period). You'll see exactly which team member has done what.
Searching and grouping
You can sift through all occurrences with an easy search syntax, highlight common properties in sub-stacks, or just browse occurrences one by one.
Flare indicates a solution for common errors in the projects overview, and will present proposed solutions and links to relevant documentation.
The stack trace has some fine details: collapsed vendor frames, references to original files (not cached view files) and a beatiful code viewer.
Options to investigate are plenty. Every occurrence has info on the request, app, user, and context. The debug tab displays all extra data: logs, dumps, glows (Flare breadcrumbs) and queries.
What if you want to get some external advice, outside your team and guests?
You can publish every single occurrence in Flare to a unique URL, available to share.
Don't want to publish user data for an occurrence? Select which slices of data can see the light.
For every project, see which team member has shared what. As an admin, you'll be able to revoke shares as well.
Be the first to know when something bad happens in one of your applications.
You can configure notifications on three levels: your personal defaults, team defaults, and custom project settings.
Have one project report in Slack, and another in your mailbox. Currently we support email, rich Slack notifications, SMS (via Nexmo) and webhooks.
Flare can notify by occurrence (first time, every time, or something in between) and by event (e.g. someone resolved or snoozed an error).