// the take
LogTide is a self-hosted observability and SIEM platform that unifies logs, traces, and metrics with uptime monitoring, log parsing pipelines, custom dashboards, and a Sigma-rules-based detection engine. It's built open-core — self-host via Docker/Helm or pay for the hosted cloud version — aimed at teams that want an ELK/Datadog alternative they fully control, mainly for GDPR reasons.
Pluggable storage layer (TimescaleDB, ClickHouse, or MongoDB) behind a 'reservoir' abstraction, so you pick the engine based on scale instead of being locked into one. Detection rules use the established Sigma YAML format with MITRE ATT&CK mapping rather than a bespoke rule language, so existing Sigma rule sets port in directly. SDK coverage is genuinely broad — Node, Python, Go, PHP, Kotlin/Java, .NET, browser — with framework-specific middleware rather than a generic client wrapped per language. Native OTLP support for logs/traces/metrics means you're not locked into a proprietary ingestion format if you migrate off it later.
AGPLv3 plus a mandatory CLA for contributions is the classic open-core setup — read the license closely if you're running this as a service for others, and expect some features gated to the paid cloud tier given the capabilities/entitlements/metering modules already in the backend. The default Docker Compose stack is 5 containers (Postgres, Redis, backend, worker, frontend) with ClickHouse/MongoDB/syslog as separate opt-in profiles — a lot to operate yourself compared to a single Datadog agent or ELK stack. The scope is enormous for a project at 458 stars — logs, traces, metrics, SIEM, uptime monitoring, and incident management all in one tool — and matching the depth of dedicated tools in each category with a small team is a stretch; there's no benchmark backing the 'sub-100ms' or 'massive scale' claims. The Fluent Bit/syslog profile silently rejects every forwarded log with a 401 if you forget to set a project write key first, an easy way to lose data on initial setup.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →