Fully featured

Flare has got you covered in both local development and production applications.
The ecosystem exists of 2 major components, seamlessly integrated.

Flare

Error tracking with… flair

Flare is the online service you're looking at. Flare collects all your errors from both local and production projects and lets you work in team to fix them.

More on Flare

Ignition

Error page for Laravel

Ignition is a free and shareable error page that ships with Laravel 6 and up. Its polished interface is built to keep you focused on finding a solution.

More on 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.

Cross-team

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.

Simple roles

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.

Error bundles

Multiple occurrences of the same error will be presented as a visual stack in the project overview, listing the amount of users impacted.

Actions

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.

Solutions

Flare indicates a solution for common errors in the projects overview, and will present proposed solutions and links to relevant documentation.

Stack trace

The stack trace has some fine details: collapsed vendor frames, references to original files (not cached view files) and a beatiful code viewer.

Debug

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.


Sharing

What if you want to get some external advice, outside your team and guests?

Public shares

You can publish every single occurrence in Flare to a unique URL, available to share.

Privacy

Don't want to publish user data for an occurrence? Select which slices of data can see the light.

Managing shares

For every project, see which team member has shared what. As an admin, you'll be able to revoke shares as well.


Notifications

Be the first to know when something bad happens in one of your applications.

Fine-grained control

You can configure notifications on three levels: your personal defaults, team defaults, and custom project settings.

4 channels

Have one project report in Slack, and another in your mailbox. Currently we support email, rich Slack notifications, SMS (via Nexmo) and webhooks.

Events

Flare can notify by occurrence (first time, every time, or something in between) and by event (e.g. someone resolved or snoozed an error).

Made for Laravel

Ignition is a beautiful, customizable error page for Laravel projects, focussed on simplicity and readability.

Pre-installed

Ignition is pre-installed in Laravel from version 6 and up. In older versions (5.5+), Ignition can be installed with Composer.

Familiar

A clean error card, a nifty stack trace and clean code viewer: when working with either Ignition or Flare, the error layout feels familiar.

Connected

Jump from an error to the Telescope dashboard, or use an API key from Flare to start tracking your Ignition errors.


Solutions

Sometimes it's just an oversight… and Ignition will let you know.

Solution cards

For common Laravel problems, possible solutions are presented below the error. Things you can try, or documentation you should take a look at.

Runnable fixes

The best part: if it's easily fixed, you can just run the solution from inside Ignition. Who hasn't forgotten to copy an .env.example file before?

Add your own solutions

Open source developers can add custom solutions to their own packages via a provided interface to assist their users even further.


Debugging

The Ignition error page will let you have a look at every detail, from every possible angle.

Lots of goodies

The default debug tabs can display Laravel app data, Blade view data, SQL queries, Git commit information and many other useful details.

Correct an error

Jump straight from the stack trace to the exact line number in PHPstorm, Visual Studio Code, Sublime or Atom.

Add custom tabs

Developers can add custom tabs to make the errors their own. A CodeMirror tab, a Tinker tab, you name it.


Sharing local errors

Have a little help from your friends, and share an error from your development environment.

Free for all

You don't need a Flare subscription to publish errors to the world. The service is totally free.

What to show

It's up to you how much you'd want to give away. When you hit "Share", you can always select which tabs will be shown or hidden.

Keep control

When a share is succesfully published, you'll get two links: one to share, and one to administer and eventually take down the public URL.

Get started in 3 simple steps:

1 Register for the trial
2 Add your project
3 Install an application key

Let's get started

This should only take a few minutes. No credit card needed.