Central Logging

Just $187, once, really?

Yes. No monthly fees, no annual fees, no per-user fees, no support contracts, no upsells. You don't rent Central Logging like SaaS, you buy it and it's yours.

What exactly do I get?

A statically linked, self-contained executable. It runs an HTTPS server with auto-issued TLS certificates, a web UI for searching logs, a REST API for ingesting them, plus Linux and BSD agents for shipping system and service logs.

Is my log data secure?

Your data lives on your server, behind your firewall, on disks you own. We never see it. The web UI is served over auto-issued TLS, and ingest tokens authenticate every log source. There is no telemetry or call-home.

What about retention and storage?

You decide. Logs are written to SQLite databases on local disk in an open, readable format. Set a retention window in the UI, or let logs accumulate for as long as you have disk. Backups are just files.

What log sources are supported?

Anything that can make an HTTP POST. Linux and BSD agents tail systemd, syslog, files, and journald out of the box. Apps in any language can ship logs in one line of code via the REST API.

Does it scale?

Surprisingly well. It concurrently ingests logs and batch-writes to SQLite databases with WAL enabled. Central Logging is designed for small businesses doing under 10GB per day. If you have petabytes, this is not for you.

How does this compare to Loki, ELK, or SigNoz?

Those are powerful but multi-component systems that need real operations work. Loki plus Promtail plus Grafana plus object storage, or Elasticsearch plus Logstash plus Kibana, or several Docker containers with a database. Central Logging is one file, designed for teams that don't want to run a logging stack.

What happens if my disk fills up?

Central Logging will alert you long before that. Disk-usage thresholds are one of the built-in alert rules. You can also configure retention to auto-prune older logs.