Collaborating in Slack to solve your exceptions just got a lot better with unfurling. We'll also do a bit of a code dive into how to integrate Slack unfurling into a Laravel application.

We created a new structure for external integrations like GitHub and Jira which allows us to add these kinds of integrations a lot quicker.

Errors will inevitably occur in your application. There is no way around it. If you notice them while working locally, you can fix them immediately. However, if your application is already live, it gets more tricky because you are not the only person triggering errors anymore. This is where error tracking software like Flare comes in handy.

Earn money by referring users to Flare

This will make it easier for newcomers to get familiar with Flare

Today we're introducing the error activity feed and notes.

Picture this: a bunch of developers, most of them back-enders, are given a Figma design file to turn into the new homepage for Flare. We set out to build our brand-new marketing site with a sprinkle of animations. Here is how we crafted them.

Here's how you can implement our log in flow in your Laravel app

Secret secrets are no fun, secret secrets hurt someone... unless they're managed right in your Laravel deployment! Say goodbye to plaintext perils and .env file follies. For Flare we explored some alternative solutions like config servers, the env:encrypt command and git-secret to keep your production environment variables safe and sound. Using git-secret's with user-specific access control and PGP encryption, managing environment variables becomes a breeze.

We now show the arguments used with each function or method call, in this blogpost we go through the implementation of it.

Today, we're adding AI-powered solutions to Flare. This means we can suggest a solution for almost any error: the AI will likely suggest a helpful suggestion for most errors.

These past months, we've been busy redesigning our entire service. We're very proud to launch it today.

Debugging errors can leak sensitive information, let's see how we can solve this using PHP 8.2

SSR Inertia and response cache: the ultimate performance and SEO combo!

Good things are coming!

We're still working on our redesign and are close to release. Today we started tackling an issue where the performance of the error page was too slow for us. In the end, we needed to change the structure of the error occurrences table, which is a lot harder than it seems.

The new version of Flare has a lot of graphs, but how do we calculate the data

We're introducing Flare Roulette™ today. Let's make bug-fixing great again!

We're redesigning Flare, but our application became really slow. Let's find out why and fix it!

We're giving our entire service a new coat of paint

Since the early days, Laravel has had an excellent validator available, but sometimes it doesn't work as expected, especially with nested arrays.

We now support the most popular payment methods in Belgium and The Netherlands

According to the React maintainers, React developers reach for the useEffect hook too quickly. It is far from the only hook with many naive usages.

Creating a Flare subscription within the EU was never easier

Here's a rundown of all the things we improved in Flare in the past year.

Introducing the Ignition and Flare Livewire tab

Flare gets a lot of errors, but how to group them?

From now on, when something goes wrong in a queued job, Flare can tell you a lot more about what's going on

As of today, Flare can notify you via Telegram. In this blog post, you'll see that we didn't only provide basic support but also went all the way with notification actions.

We've just launched a new feature that will make it easier for users of your app to report specific errors.

We've recently added a support form bubble form to our app. In this post we'll explain what it is, why we added it, and how you can add one to your app.

If you've read our blog or docs the last few weeks, some things might look a little bit different. We now highlight our code blocks using Shiki.

A static analyzer helps you to find bugs in your code without even running it, let's take a look what it can find in the Flare codebase.

Flare runs on a few different servers that each produce their own logs. In this post, you'll learn how we can combine multiple logs in a single stream.

We've now have a completely renewed billing experience powered by the latest version of Laravel Spark. In this blog post, we'll share why and how we performed this migration.

Our search capabilities have been vastly improved under the hood.

Like most SaaS companies, the Flare back-office features a neat dashboard showing some of our key metrics. Using Laravel Nova it's pretty easy to aggregate data per model like the total number of errors or the active subscriptions per week. Behind the scenes these dashboard tiles and graphs use simple database queries. For example, the number of active subscriptions is a simple `SELECT COUNT(*)` query on the `subscriptions` table. But how do we query new subscriptions per week?

We've added a nice addition to your UI.

From now on, you can control the exceptions and errors sent to Flare

You can now retrieve all projects and errors using our new API.

When you now check "Select all", all errors of a project can be selected.

Like many others SaaS applications, you can try out Flare using a trial period. Of course, not everybody that tries out Flare will convert. After the trial period is over, some people will not use the service anymore. In this post you'll learn how we clean up the data of inactive teams and users

Our projects overview has been vastly improved.

Our email notifications got more powerfull.

In some cases, such as a login page, these request fields may contain a password that you don't want to send to Flare. Here's how you can censor certain values.

There's a new "type" property that gets displayed on each error in our UI.

Here's a peak at the actual source code of Flare.