Logdy 0.17 on Ubuntu 24.04

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

Logdy is a self-hosted, web-based real-time log viewer and tailer for DevOps engineers, SREs and small platform teams who need fast, visual log inspection without deploying a heavy centralized logging stack. It follows a log source, a file you point it at, a program's standard output, journald, or a socket, and serves a clean browser interface that streams every line live, with sortable columns, full text search and composable filters so you can slice a noisy log down to exactly the events you care about. Structured JSON logs are parsed into real columns automatically, and low-code TypeScript parsers let you shape and colour arbitrary formats, so tailing a file in a terminal becomes a fast, visual, shareable experience. It is a single Go binary that holds logs in an in-memory buffer, so it stays lightweight, starts instantly and needs no database or external services. The current release available is Logdy 0.17.

Who this is for: an SRE debugging a failed deployment on a single EC2 instance can filter structured application logs in real time, isolating error events from thousands of lines a minute without shipping data to an external platform. A small team monitoring service output gets instant visibility without provisioning databases, configuring Elasticsearch clusters or tuning Java heap sizes, just launch the image and open your browser.

This image delivers Logdy fully installed and reverse proxied behind nginx, so a working log viewer is running within minutes of launch, with no manual package installation, no dependency troubleshooting and no proxy configuration required. To show the interface working the moment the instance boots, the image ships a small demo generator that appends structured log lines to a demo file that Logdy follows, so the columns, search and filters are populated on first boot, this is demo data only, and the paired guide shows you how to switch Logdy to your own file, journald or socket in a single step.

Why this beats a bare deployment: unlike installing Logdy from source or running a multi-component stack such as ELK or Loki plus Grafana, this image is configured to be secure by default.

• Loopback-only binding: Logdy never listens on a public interface.
• No default password: a unique credential is generated on each machine's first boot, stored only as a hash for nginx, with the plaintext written once to a root-only file, and never baked into the image.
• nginx reverse proxy: ready for your TLS certificate with no additional configuration.
• WebSocket protection: the entire interface, including the live log stream, is behind HTTP Basic authentication.
• Health endpoint only: a single static endpoint is left open for liveness checks.
• systemd managed: automatic restarts and clean logging out of the box.

Features include live tailing of files, standard output, journald and sockets, automatic parsing of structured JSON into columns, full text search and multi condition filtering, low-code TypeScript parsers for custom formats, and a single self contained binary with an in-memory buffer for instant startup.

Getting started: launch the image, retrieve your generated credential from the root-only file, open your browser and you are viewing live logs. The paired deployment guide walks you through switching Logdy from the demo log to your own sources, configuring TLS termination and writing custom parsers.

This is a repackaged open source software product with additional charges for cloudimg support services. Logdy is distributed under the Apache License 2.0. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.