offline & local-first
An offline log viewer —
nothing uploaded, no account
Logier is a desktop application, not a client for a hosted service. Pull the network cable and it keeps working, because none of what it does was going over the network in the first place — logs are parsed, clustered, charted, and analysed in memory on your own machine.
with the cable pulled
What works with
no connection
Opening and parsing any file
Format detection runs as local pattern matching, including the heuristic fallback for formats no parser recognises.
Search, filters, and clustering
Everything that narrows a file down is computed in memory on your machine.
Timeline and anomaly detection
Both derive from the file itself. No baseline, model, or reference data is fetched from anywhere.
No account to read a log
You don't sign in to open a file, and the app doesn't need to reach a server for you to work.
Two features do use the network, and both are things you invoke deliberately: Live Mode connects to a streaming endpoint you supply, and the AI analysis sends the excerpt around a selected error to a provider you configured. Point the latter at a local model and even that stays on your machine.
why it matters for logs
Logs are the least sanitized data you own.
Production logs routinely contain session tokens, email addresses, internal hostnames, full request bodies, and stack traces naming internal paths — captured incidentally, by code written under deadline, and never reviewed for what it emits. Uploading that to a third-party ingestion pipeline in order to debug a single crash is a disproportionate transfer of data, and in a regulated environment it may not be an option at all.
who this is for
Where local-first
stops being optional
Regulated environments
Health, finance, and public-sector work where sending production logs to a third-party processor is a compliance question you'd rather not have to answer.
Air-gapped and classified networks
Defence, industrial control, and secure facilities where the machine has no route to the internet at all and never will.
Customer log bundles
Support and field engineering, where a customer sends you a log archive that contains their data and must not be uploaded anywhere.
Working offline
Aeroplanes, trains, sites with no connectivity, and the ordinary case of not wanting a debugging session to depend on a network round trip.
faq
Common questions
keep reading
Related reading
Local-first log privacy
The full data-handling picture, including a side-by-side with cloud log platforms.
AI root cause analysis
Exactly what the excerpt contains, and how to run the whole thing against a local model.
Logier vs. cloud log platforms
When you genuinely need ingestion, alerting and retention — and when a local tool is enough.
Unknown log format analyzer
Proprietary and air-gapped systems tend to emit formats nobody has documented.
Read it where it already is.
No upload, no account, no ingestion step between you and the log file on your disk.