---
title: "Supabase Logs: open source logging server"
description: "Supabase is releasing Supabase Logs for self-hosted users and CLI development, built around Logflare, which processes more than 1 billion log events daily from Supabase services. Logflare is a multi-node, highly available Elixir cluster that ingests events through Vector or native integrations, streams them to BigQuery, and exposes SQL-backed HTTP Endpoints for Studio, Logs Explorer, and usage charts. Endpoints support parameterized queries, in-memory read-through caching, configurable cache warming, and select-only query sandboxing, allowing views over billions of daily events without querying many terabytes on every request. The release changes Logflare’s license to Apache 2.0, replaces closed-source SQL parsing with rust-based sqlparser-rs, and improves environment-based configuration for self-hosting; BigQuery is currently the supported backend, with more planned."
---

# Supabase Logs: open source logging server

[Supabase](https://yomu.fyi/company/supabase) · chasers,ziinc · Apr 10, 2023

**Type:** Announcement

## Summary

Supabase is releasing Supabase Logs for self-hosted users and CLI development, built around Logflare, which processes more than 1 billion log events daily from Supabase services. Logflare is a multi-node, highly available Elixir cluster that ingests events through Vector or native integrations, streams them to BigQuery, and exposes SQL-backed HTTP Endpoints for Studio, Logs Explorer, and usage charts. Endpoints support parameterized queries, in-memory read-through caching, configurable cache warming, and select-only query sandboxing, allowing views over billions of daily events without querying many terabytes on every request. The release changes Logflare’s license to Apache 2.0, replaces closed-source SQL parsing with rust-based sqlparser-rs, and improves environment-based configuration for self-hosting; BigQuery is currently the supported backend, with more planned.

## Context

Supabase needed an open-source, self-hosting-friendly logging and analytics server, while querying many terabytes of ingested logs for every request would be expensive. Changing Logflare’s license also required removing its closed-source SQL parser dependency.

## Approach / What changed

Logflare ingests events from Supabase services through Vector and native integrations, streams them into BigQuery, and exposes parameterized SQL queries through HTTP Endpoints. Endpoints use in-memory read-through caching, configurable proactive cache warming, query sandboxing, and select-only SQL parsing. The project switched to rust-based sqlparser-rs and environment-variable configuration to support Apache 2.0 licensing and self-hosting.

## Takeaways

- Logflare processes more than 1 billion daily log events from the API gateway, Postgres, Storage, Edge Functions, Auth, and Realtime using a multi-node Elixir cluster.
- Endpoints combine parameterized SQL, read-through caching, and active cache warming; an example reduces thousands of requests to five BigQuery queries over a 10-minute interval.
- Logflare is now Apache 2.0 licensed and uses rust-based sqlparser-rs, while BigQuery remains its current supported backend.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Observability](https://yomu.fyi/topic/observability), [Open Source](https://yomu.fyi/topic/open-source), [Performance](https://yomu.fyi/topic/performance)

- Source: [Supabase](https://supabase.com/blog/supabase-logs-self-hosted)
- Source URL: https://supabase.com/blog/supabase-logs-self-hosted
- Ingested by Yomu: 2026-08-29T01:17:08.046Z

[Read original post](https://supabase.com/blog/supabase-logs-self-hosted)