Back in May 2020, we tweeted about one of the most impressive products we had ever used: Logflare, a log ingestion platform.
Really impressed with @logflare_logs. We've been on the front page of #hackernews for 24 hours anticipating the HN hug of death. Looks like we made it through OK and Logflare has been ingesting everything without breaking a sweat https://t.co/RWKHIgmWh6 pic.twitter.com/dQ2xqFTdco— Supabase (@supabase) May 28, 2020
Today, we're ecstatic to announce that Logflare is joining Supabase.
A log platform might seem like a strange acquisition for Supabase - after all, there are no "Firebase Logs".
Logging is one of the most unappreciated parts of a tech stack, often an after-thought. But when leveraged correctly, logs give developers superpowers.
We want to provide the best database developer experience in the world, and so we're making debugging a first-class citizen.
Databases can be a black box when it comes to spotting errors, finding slow queries, and testing performance optimizations.
The full Supabase stack is more than just a database. It includes various tools working together - APIs, Storage, Auth, and CDNs. A broad tech stack needs a unified measurement system to give a birds-eye view of everything happening within your Supabase project.
This is especially true for our enterprise customers, who need to know that their servers are not just operating, but optimized with alerting the instant anything goes wrong.
While it's not immediately apparent, logs are analytics! Especially when a developer can correlate log entries, and enrich them with database data.
Imagine tracing one of your user's network requests from the browser to a database query. Perhaps you'd like to know which of your users are making the most API requests, or downloading the most files, or spending the most time connected to the application?
With granular logs, this becomes possible and paves the way for an incredible developer experience: managing your API versioning, predicting growth, and managing billing costs.
Since that first tweet in May 2020, our platform has generated billions of log entries. During that time, Logflare has been a staple product in our day-to-day operations. There are a few reasons why Logflare is such a great match for Supabase.
- Chase! The founder of Logflare, Chase, is an accomplished founder, incredibly product-focused, and an all-around mensch. With over 10 years of experience in data aggregation, Chase is the type of talented person that every team dreams of working with.
- Elixir. Logflare is built with Elixir, the same as our Realtime Engine. We love Elixir at Supabase, and it's nice to have it power another key part of the Supabase stack.
- Real-time. Logflare isn't just for querying logs, it displays what's happening in realtime, allowing you to debug your systems live.
- Branding. Who doesn't love the vivid green with dark mode? 😎
Why is Logflare joining Supabase?
Supabase + Logs
We still have a lot of technical work to integrate Logflare into Supabase, with plans of fully supporting the existing Vercel and Cloudflare integrations.
In just the past 10 days, we've been working on a few of the new Dashboard features, which you'll be able to see very soon.
Over the next few weeks, we plan to release these features (once we have a chance to polish them up), and you'll be able to query your logs with your favorite language - SQL 😀.
Right now, Logflare works natively with Big Query. But as our track record has proven, we're 100% committed to open source. We're working on the future of a fully open-source version of Logflare, with support for various storage engines.
If you're an existing Logflare user, we'll be migrating everything to Supabase in the coming months. We'll work closely with you to ensure that the transition is seamless, and introduce the same pricing levels that Logflare offers today.
We've worked with Chase on a list of potential questions you might have about the transition. If you have any concerns or questions, you can reach out to email@example.com.