All Your Logs in One Place. Zero Loss, Signed Archive.
izLog collects logs from your servers, firewalls, applications and databases in one platform, searches them in seconds, raises real-time alerts, and stores them in a signed + timestamped, immutable archive for as long as you need. Enterprise-grade, multi-tenant, and entirely on your premises.
An Enterprise Alternative to Graylog — Built In-House
izLog is a product we built from the ground up and control end to end. Collection, processing, indexing, alerting and archiving run independently: even if the search cluster goes down entirely, the log flow and archive pipeline keep running. Every log is durably written to a replicated queue before the source is acknowledged — which is why nothing is lost.
The Journey of a Log
Every stage is independent and resilient. If one layer slows down, data is not lost; it is buffered and resumes where it left off once the layer recovers.
Receive
Accepted over Syslog (UDP/TCP/TLS) and HTTP; secured instantly with minimal processing.
Durable Queue
Written to a replicated queue before acknowledgement (acks=all). The log is safe before the source is told "received".
Process
Parsing, normalization and enrichment — the raw log is always preserved.
Index
Written to OpenSearch for search; if search fails it is buffered, never lost.
Alert
Threshold / absence / match rules over the stream; email, Telegram, Teams, webhook notifications.
Archive
Long-term retention as signed, timestamped, immutable segments.
Key Features
Everything you expect from an enterprise log platform — and more.
Zero-Loss Collection
Every log is durably written to a replicated queue before the source is acknowledged. Even if the search layer fails, collection and archiving keep running.
Signed & Timestamped Archive
SHA-256 + hash chain + Ed25519 digital signature + RFC 3161 timestamp. With WORM (Object Lock), once written no one — not even an admin — can alter or delete it.
Agentless Remote Collection
Without installing agents; pull Windows Event (WinRM), IIS (SMB), Linux file (SSH/SFTP) and database (MSSQL/PostgreSQL/MySQL) logs with zero loss.
Parser Studio
Ready-made parsers (FortiGate, Windows, Nginx, …) plus a visual studio to define your own log format with no technical expertise required.
Alerting & Notifications
Threshold breaches, missing expected logs (absence), pattern matches and aggregation rules. SMTP, Telegram, Microsoft Teams and webhook channels.
Powerful Search
Graylog-style filter bar, field-table detail and GeoIP. Search across millions of logs in seconds.
RBAC & Audit Trail
Multi-tenant architecture, role-based access and per-source/device authorization. Every critical admin action is written to an audit log.
Historical Export
Bulk export by date/device is read directly from the archive — signature and timestamp included — without ever touching the search cluster.
Collect Logs From Any Source
Almost every system on your network can talk to izLog.
Syslog
UDP / TCP / TLS — firewalls, switches, routers, Linux servers.
Windows & AD
Agentless Windows Event and Active Directory / logon logs via WinRM.
IIS
IIS web server access logs over SMB.
Linux Files
Remote file-based log collection over SSH / SFTP.
Databases
MSSQL, PostgreSQL, MySQL — checkpointed, loss-free SQL collection.
HTTP & Apps
Direct ingestion from applications and custom sources over REST.
Compliance & Evidence Integrity
The combination of signing, timestamping and immutable (WORM) storage turns your logs from merely "kept records" into records whose integrity can be proven and that carry legal weight.
Legal Retention
Retain access and transaction records for the required period, with integrity provable via timestamps.
Data Protection
Keep access trails to personal data with an audit log; who accessed what, and when, is documented.
Immutable Evidence
Archive written with Object Lock cannot be deleted or altered until retention expires — the signature verifies every segment.
Trusted Timestamp
RFC 3161 timestamps independently prove when each archive segment was created.
Enterprise Robustness
Designed for high-volume, mission-critical environments.
Durable Backbone
Kafka / Redpanda based, replicated queue with 7+ days of buffer.
Scalable Search
Automatic rollover with index lifecycle management (ISM) on OpenSearch.
Open-Format Archive
JSONL + zstd; independent of the search engine, portable and long-lived.
Secure Secret Management
Passwords and keys encrypted with AES-256-GCM; the signing key is never stored in the database.
Let us build your centralized log infrastructure
Talk to our team for an izLog deployment and pricing sized to your needs. We support you with installation, source integration and retention policies.
Frequently Asked Questions
Where is my izLog data stored?
Entirely on your own infrastructure (on-premise) or on your dedicated server. Logs and the archive stay on disks under your control; your data does not leave your environment.
Will I lose logs if the search server goes down?
No. Logs are first written durably to a replicated queue. Even if the search layer (OpenSearch) fails completely, collection and archiving keep running; once the layer recovers, the buffered logs are indexed.
How do I prove the archive was not tampered with?
Each archive segment is hashed with SHA-256, linked into a hash chain, signed with Ed25519 and given an RFC 3161 timestamp. Object Lock prevents any change during the retention period. Signature verification proves integrity mathematically.
Which sources can I collect logs from?
Syslog (UDP/TCP/TLS), HTTP, agentless Windows Event (WinRM), IIS (SMB), Linux files (SSH/SFTP) and databases (MSSQL/PostgreSQL/MySQL). Beyond the ready-made parsers, you can define your own format with Parser Studio.