# LogDeck

> LogDeck is a free, open-source (GPL-3.0), self-hosted log viewer, alerting tool, and control panel for Docker and Podman containers. It keeps container logs after restarts and removal, alerts when containers break, and lets you fix them from a browser, a CLI, or an AI agent.

- Server: one Docker image, `amoabakelvin/logdeck`, listening on port 8080 inside the container. Mount the Docker or Podman socket, and mount `/data` as a volume: it holds the config, the SQLite log store, and alert history.
- Log history: every container's logs are stored on the LogDeck host and stay searchable after the container restarts, is rebuilt, or is removed.
- Alerts: rules on container deaths, OOM kills, failing health checks, and log patterns, sent to a webhook (Slack and Discord work as-is), ntfy, Gotify, or Telegram.
- CLI and MCP: the `logdeck` CLI and `logdeck mcp` use the server's HTTP API with scoped `ldk_` API tokens. A read token can only read; an admin token can act.
- Not included: deploying apps, multiple users or SSO, Docker Swarm, and Kubernetes.

Every page below is also served as HTML without the `.md` suffix.

## Get started

- [Getting started](https://logdeck.dev/docs/getting-started.md): What LogDeck is, what it is not, and the quickest way to run a self-hosted instance with Docker Compose.
- [Installation](https://logdeck.dev/docs/installation.md): Install the LogDeck server with Docker Compose or docker run, mount the Docker or Podman socket, and update or troubleshoot it.
- [Features](https://logdeck.dev/docs/features.md): Every LogDeck feature: live and stored container logs, alerting, stats, multi-host, Compose stack actions, a web terminal, the CLI, and MCP.

## Guides

- [Log history](https://logdeck.dev/docs/log-history.md): How LogDeck stores container logs in SQLite so history survives restarts, rebuilds, and removal, plus retention and the history API.
- [Alerting](https://logdeck.dev/docs/alerting.md): Alert on container deaths, OOM kills, failing health checks, and log patterns, with thresholds and cooldowns, to webhooks, ntfy, Gotify, or Telegram.
- [CLI reference](https://logdeck.dev/docs/cli.md): The logdeck CLI: install it, log in with contexts and API tokens, then read, follow, and grep logs and manage containers from the terminal.
- [MCP server](https://logdeck.dev/docs/mcp.md): Run logdeck mcp so Claude, Cursor, or any MCP client can read your containers, logs, and stats, and act on them with an admin token.

## Reference

- [Configuration](https://logdeck.dev/docs/configuration.md): Every LogDeck setting: the /data directory, DOCKER_HOSTS, authentication, API token scopes, log retention, Coolify sync, read-only mode, and reverse proxies.

## Compare

- [LogDeck vs Dozzle](https://logdeck.dev/compare/dozzle.md): A feature-by-feature comparison of LogDeck and Dozzle, two self-hosted Docker log viewers, including where Dozzle is the better pick.

## Optional

- [Full documentation](https://logdeck.dev/llms-full.txt): Every page above in one markdown file.
- [Live demo](https://logdeck.dev/demo): The LogDeck UI running in the browser on simulated data.
- [GitHub repository](https://github.com/AmoabaKelvin/logdeck): Source code, issues, and releases.
- [Docker Hub image](https://hub.docker.com/r/amoabakelvin/logdeck): The amoabakelvin/logdeck server image.