lognivoGet Lognivo
// Docker & Compose / macOS

See what your containers are telling you.

Your API, queue and reverse proxy do different jobs. Give their logs separate panels and keep the request in context without juggling terminal windows.

Find your planRead the practical guide ↗
The Lognivo Mac app with separate API, worker and error log panels
The Lognivo workspace. Screenshot with sample local logs.
// FROM SOURCE TO SIGNAL

A workflow you can return to.

01

Choose local or remote Docker

Use a working Docker engine on your Mac, or a Docker host reached over SSH. Your account needs access to the engine. Lognivo reads streams that Docker makes available.

02

Follow containers and Compose services

Select a container or Compose service and bring stdout and stderr into your workspace. Keep application file logs next to container output when both are involved in a failure.

03

Keep output readable

Pause noisy output, search for a message and switch reading order per panel. Bounded history keeps a long-running stream from becoming an unbounded desktop buffer.

// A CLOSER LOOK

Small controls. More room for the log.

Search, severity filters, reading order and pause stay with their panel. As you resize, secondary actions move into the options menu.

Detail of Lognivo’s search field, panel controls and coloured log levels
Detail from the app · sample log data

Before you connect.

Does Lognivo change Docker retention?

No. Docker logging drivers and retention settings determine what is stored. Lognivo displays the output available to your account.

Does it support Kubernetes?

Native Kubernetes integration is not part of this release. Docker, Compose, local files and SSH are supported source workflows.

Explore all features and FAQs

Keep the rest of your stack in view.

Multiple logs ↗SSH logs ↗WordPress ↗Laravel & PHP ↗Linux & systemd ↗

Make room for the whole story.

macOS 14+ · Apple silicon & Intel

Get Lognivo for Mac