Logflare/logflare

Health v2 · maintenance only

Adoption not part of the score

1004 stars · 94 forks observed · 2026-09-03

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Logflare is a centralized structured log ingestion and querying service that streams log events into BigQuery (or its own backend) with automatic schema management, plus a browser-based tailing and dashboard UI. It is part of Supabase and can be self-hosted or used via the hosted logflare.app service.

Use cases

• centralize logs from cloudflare, vercel, elixir and javascript apps
• stream logs to my own bigquery tables without managing schemas
• tail application logs in the browser
• avoid surprise logging bills with predictable bigquery storage costs
• ingest opentelemetry traces and metrics
• query log events with a simple query language and build dashboards
• self-host a log ingestion and querying engine

When to choose

• you want cheap, long-term structured log storage in a columnar database like BigQuery
• you want bring-your-own-backend control over storage costs and data residency
• your stack includes Cloudflare, Vercel, Elixir/Erlang, or JavaScript (pino/winston)
• you want log management and analytics dashboards in one tool

When to avoid

• you need a turnkey log aggregator with local storage and no external cloud dependency
• you rely heavily on OpenTelemetry ingestion, which is still alpha-stage
• you need Elasticsearch/Lucene-style full-text search features
• you don't want any dependency on Google Cloud/BigQuery and can't self-host

Facets

service · maturity active

logging monitoring analytics etl streaming self-hosted monitoring analytics big-data developer-tools self-hosted cloud self-hosted browser log-management bigquery structured-logging observability bring-your-own-backend opentelemetry elixir supabase log-ingestion log-tailing devops web-server docker nodejs

Member repositories

For agents

markdown · JSON · MCP: product_card(name="Logflare/logflare")