offline & local-first
Some logs can't leave the building
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.
No account to open a file · no telemetry SDK · no licence phone-home to read a log
Ninety seconds to prove us wrong.
A privacy claim is only worth making if the product still works while you are checking it. Here is the procedure. If any step fails, the claim on this page is false and you should not buy the software.
- 01
Cut the connection
Turn off Wi-Fi and unplug the cable, or — better, because it isolates the application rather than the machine — add an outbound block rule for Logier in Little Snitch, LuLu, or Windows Defender Firewall.
- 02
Open a log file
From the Explorer, straight off your own disk. Note that you were not asked to sign in, create an account, or wait for anything to load. There is no licence phone-home standing between you and the file.
- 03
Let it detect the format
The parser registry runs locally as pattern matching. Nothing about the file — not a hash, not a sample, not the filename — is sent anywhere to work out what it is.
- 04
Search, filter, and cluster it
Full-text search, level toggles, service filters, time ranges, and the clustering that collapses repeated errors into counts. All computed in memory from the file you just opened.
- 05
Read the timeline and the findings
The chart buckets your entries by minute; the findings panel runs five detectors over them. Neither fetches a baseline, a model, or any reference data — the baseline is your own file.
- 06
Now check the ledger
Open Activity Monitor's Network tab, Resource Monitor, or your firewall's log, and look at what Logier actually attempted while you did all of that. That number is the claim, and it is the one worth checking rather than taking.
Nothing on screen degrades while the network is gone, which is the point — and it is also how you can tell the difference between software that happens not to upload today and software that was never built to.
With the cable pulled, this is all of it.
Not a degraded offline mode with a banner asking you to reconnect. The same application, doing the same work, because the work was never remote.
- 01
Opening and parsing any file
Format detection is local pattern matching, including the heuristic fallback for formats no named parser recognises.
- 02
Search, filters, and clustering
Everything that narrows a file down is computed in memory on your machine, from the bytes you opened.
- 03
Timeline and anomaly detection
Both derive from the file itself. No baseline, model, or reference data is fetched from anywhere — the file is its own control group.
- 04
No account to read a log
You do not sign in to open a file. The app does not need to reach a server for you to do the work.
For most people this is a preference. For some it is the requirement.
- 01
Regulated environments
Health, finance and public-sector work, where sending production logs to a third-party processor is a compliance question you would rather not have to answer in writing.
- 02
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. A tool that degrades without a network is simply not installable.
- 03
Customer log bundles
Support and field engineering, where a customer sends you an archive containing their data and your obligation is that it goes nowhere else.
- 04
Ordinary disconnection
Aeroplanes, trains, sites with no coverage — and the plain preference for a debugging session that doesn't depend on a network round trip.
the honest limit
Local-first is an architecture, not a certificate.
Everything on this page is a statement about how the software is built and what you can observe it doing. None of it is a third-party audit, a SOC 2 report, or an assurance that your organisation’s policy permits this tool. If you work somewhere that requires formal certification for anything touching regulated data, that is a conversation with your security team, and it applies to every tool you evaluate rather than just this one.
The three features that doreach the network — the AI explanation, Live Mode, and cloud file open/save — are opt-in and individually invoked, and each is enumerated with what it sends on the secure-by-default page. An honest offline claim has to name its exceptions.
faq
Common questions
keep reading
Related capabilities
- 01
Secure by default
The complete outbound ledger — every request the app is capable of making, what triggers it, and what it carries.
- 02
AI log analyzer
The one feature that can reach the network, and how to run it entirely on-device instead.
- 03
Unknown log format analyzer
Proprietary software usually means sensitive logs. Nothing is sent anywhere to identify a format.
- 04
Logier vs. cloud platforms
When a pipeline is genuinely the right architecture, and when it's a compliance problem you didn't need.
Read it where it already lives.
No upload, no account, no pipeline — and a procedure on this page to check that for yourself.