Open-Source Observability · mr-karan

logchef

Logchef is a lightweight, single-binary log analytics platform built on ClickHouse for high-performance log storage and querying. It provides a modern web UI, CLI, natural-language AI query assistance, real-time alerting, OIDC+RBAC, and schema-agnostic exploration without migrations.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/mr-karan/logchef

758

GitHub stars

Forks

Primary language

AGPL-3.0

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	mr-karan/logchef
Owner	mr-karan
Primary language	Go
License	AGPL-3.0 — OSI-approved
Stars	758
Forks	48
Open issues	10
Latest release	v1.7.0 (2026-07-06)
Last updated	2026-07-08
Source	https://github.com/mr-karan/logchef

What logchef is

Go-based log analytics frontend for ClickHouse with pluggable metadata stores (SQLite or Postgres), supporting LogchefQL and raw SQL queries. Includes Prometheus metrics, MCP integration for AI assistants, email/webhook alerting, and multi-platform binary distributions.

Quickstart

Get the logchef source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/mr-karan/logchef.git2cd logchef3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Development and staging log exploration

Teams needing fast, interactive log filtering without operational overhead. Single binary deployment with zero config (SQLite) makes adoption quick for internal tools.

Multi-tenant or team-based log access control

OIDC + RBAC built-in enable SSO integration and role-based access out of the box, suitable for SaaS or shared infrastructure environments.

Schema-flexible log ingestion and querying

Schema-agnostic design allows pointing at any ClickHouse table without migrations, ideal for heterogeneous logging setups or evolving log schemas.

Implementation considerations

ClickHouse dependency: logchef is a frontend; you must deploy and manage ClickHouse separately. Ensure ClickHouse version compatibility and network accessibility.
Metadata storage choice: SQLite is zero-config for single-instance; Postgres is required for multi-replica HA. Plan accordingly for production scale.
AGPL compliance: If modifying or deploying as a service, ensure legal review and commit to source disclosure. Consider commercial licensing if required.
AI query assistant: Feature availability and cost depend on external LLM integration. Not specified in data; verify setup and costs.
Single-binary deployment: Simplifies rollout but plan for version management, configuration updates, and log rotation in production.

When to avoid it — and what to weigh

Proprietary or restrictive IP requirements — AGPL-3.0 requires source disclosure for networked modifications. Closed-source or proprietary derivative use is not permitted without license review.
No existing ClickHouse infrastructure — Logchef is a UI and query layer; it requires ClickHouse as backend. Organizations without ClickHouse or unwilling to adopt it should evaluate alternatives.
Minimal operational overhead or hand-off deployment — While single-binary, production HA requires Postgres metadata store and multi-replica ClickHouse setup. Teams preferring fully managed SaaS may find operational burden significant.
Compliance with strong proprietary software mandates — AGPL-3.0 copyleft terms may conflict with enterprise policies requiring only permissive or commercial licenses.

License & commercial use

Logchef is licensed under AGPL-3.0 (GNU Affero General Public License v3.0), a copyleft license requiring source code disclosure for any networked use or modification. Commercial, proprietary, or closed-source derivative use is not permitted under AGPL-3.0.

AGPL-3.0 is NOT a permissive license. Internal use and deployment are allowed, but offering logchef as a service or modifying it for external customers triggers source disclosure obligations. Commercial licenses may be available from the author; Requires review with legal counsel before production use in B2B or SaaS contexts.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Active
Documentation	Strong
License clarity	Clear
Deployment complexity	Moderate
DEV.co fit	Good
Assessment confidence	High

Security considerations

OIDC + RBAC provide authentication and authorization controls. No security audit or CVE history provided in data. Network exposure (web UI, API) requires standard hardening (TLS, rate limiting, network isolation). Review AGPL source disclosure implications for sensitive deployments. Metadata store (SQLite or Postgres) should be secured according to your infrastructure standards. No specific security posture claims made here; conduct independent assessment.

Alternatives to consider

Grafana Loki

Open-source log aggregation with Prometheus-native integration, lower resource overhead, and more permissive license (AGPL but more widely adopted). Best for metric-centric observability.

Datadog Logs or New Relic Log Management

Fully managed SaaS with no operational overhead, built-in alerting, and compliance certifications. Best for teams prioritizing outsourced log management and avoiding AGPL.

Elasticsearch (via Kibana)

Mature, widely adopted log search and analytics with rich visualizations. SSPL license and significant operational overhead. Best for large-scale, mission-critical logging.

Software development agency

Build on logchef with DEV.co software developers

Review AGPL-3.0 license terms with legal counsel, assess ClickHouse infrastructure readiness, and test the demo or Docker quickstart. Contact us to discuss architecture fit and operational planning.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

logr mtail logbook

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability API Development DevOps & Infrastructure Custom Software Development Talk to DEV.co

logchef FAQ

Do I need ClickHouse already deployed?

Yes, logchef is a UI and query layer for ClickHouse. You must deploy ClickHouse separately as the log storage backend.

Can I use logchef commercially or in a SaaS product?

AGPL-3.0 permits internal use, but offering logchef as a service or modifying it for customers requires source disclosure. Consult legal counsel; commercial licensing may be negotiated with the author.

What is the operational overhead?

Single-binary deployment is simple, but production HA requires Postgres for metadata, multi-replica ClickHouse, OIDC provider setup, and alerting infrastructure. Not zero-ops at scale.

Is the AI query assistant included or an add-on?

Listed as a feature, but integration details, LLM provider, and costs are not specified in the data. Requires documentation review.

Work with a software development agency

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If logchef is part of your open-source observability roadmap, our team can implement, customize, migrate, and maintain it.

Ready to evaluate Logchef for your team?

Review AGPL-3.0 license terms with legal counsel, assess ClickHouse infrastructure readiness, and test the demo or Docker quickstart. Contact us to discuss architecture fit and operational planning.

Talk to DEV.co Schedule a Consultation