Log Drop turns server logs into a living soundscape. Every kind of event plays its own instrument, so a healthy fleet sounds like gentle rain and an incident sounds like a storm. You will hear it from the next room.
Monitoring is a screen you have to stare at. Log Drop is ambient: it plays quietly in the background and gets loud only when something is actually wrong.
A healthy system is a pleasant, quiet patter. Density, not volume: normal traffic stays in the background so your ears keep their sensitivity for what matters.
Thunder is not every error, it is a sudden jump in error rate. One unmistakable rumble means the situation changed, whether or not anyone was watching a graph.
The first time your system emits a kind of event it has never emitted, you hear a bell. New behavior, cron jobs, attackers: you learn instantly, and never as a machine gun.
Your hub, your machines, your browser. Three steps.
One command on any always-on machine you own. The hub stores events, runs the detectors, and serves the listening client.
Collectors connect over SSH and stream logs from every box you run. If you can SSH to it, you can hear it.
Open the client in a browser and leave it playing. Weather for your infrastructure, mixed live from your actual logs.
A sonification engine built for real operations, not a gimmick
Each event class gets a synthesized instrument with its own timbre. HTTP falls as rain, heavy jobs land as thuds, hammering failures knock like a woodpecker. All of it tunable.
A rate-jump detector watches the error landscape. Quiet during a slow leak, enormous the moment the sky opens. Severity you can feel, calibrated by rate of change.
Unknown event patterns are fingerprinted and rung once, never repeated in a panic. The bell is how a brand-new kind of thing introduces itself.
Pull any window of history back through the soundscape at any speed, with silence compressed. Re-listen to the 3am storm at breakfast, at 100x, filtered to one server.
Decide which log patterns matter and what they should sound like. Rules hot-reload live, and every proposed change waits for a human yes.
Optional AI names unknown event clusters, proposes mappings, and retunes instruments from a description. It uses your own API key, stored in your hub, and never sees unredacted text.
Sound packs remix the entire soundscape. Ship with three, switch anytime.
The classic. Resonant raindrops, soft wood thrush, distant thunder. Steady state is a rainforest afternoon.
Wooden and warm. Claves, marimba, a membrane drum for the heavy stuff. Traffic becomes gentle percussion.
Synthwave for your servers. Glassy FM bells, square-wave blips, a zap that drops in pitch when the 5xx land.
Built this way from the first commit, not bolted on later
The hub and collectors run on your own machines. Your log data is stored in your database and sent nowhere. There is no Log Drop cloud to send it to.
Anything that ever leaves the hub, such as an optional AI request, is stripped of emails, IPs, and hostnames first, and it only goes to the provider your own key points at.
The whole product works with zero accounts, zero subscriptions, and zero API keys. AI features are optional extras that hide until you bring a key.
Buy it once. Listen for years. No meter running.
The complete soundscape for a single server. Not a trial: the real product, free forever on one machine.
Everything unlocked for every server you run, with a long runway of updates included.
Launching soon · check back or say hello
The things everyone asks first
Node.js on one always-on machine for the hub, SSH access to the servers you want to hear, and a browser. That is the whole stack.
No. The hub and its collectors run on your infrastructure and store events in a local database. There is no vendor endpoint to phone home to.
No. The core product is fully keyless. If you want the AI copilot, you bring your own provider key, it stays in your hub, and every request is budgeted and redacted before it leaves.
Node services via pm2 today, collected over SSH from any box you can reach. More sources, including nginx, MySQL, and journald, are on the roadmap.
It is in active development and being tested on real infrastructure right now. Email us and you will hear about the launch before the thunder does.
Log Drop is by bk & hallie at Odditory. Want to know the moment it ships, or trade notes on log sonification? Say hello.