Make your data work for you.
Not the other way around.
Logverz is a cutting-edge, self-serve data platform,
that changes the log analysis's logic, pace, and costs.
Intuitive permission management
Instant report generation
hours spent preparing data
unnecessary log ingestion
NO MORE clumsily moving datasets
Different by design.
After 20 minutes of deployment + approx. 40 minutes of environment validation time, Logverz is able to achieve the same impactful results that companies can only produce after half-year-long data lake projects.
Built on top of AWS. Radically simplifies and de-risks the log analysis by doing the actual log collection and the analysis in the users’ cloud environment without moving large datasets across to other tools.
Reliable source-available tool offering faster deployment, better security, transparency and freedom from lock-in.
Free forever for generic use, and licence fees only apply for service provider and development purposes.
Allows users to do extremely flexible self-serve ETL, intuitive permission management and instant report generation.
Serverless, needs practically no maintenance, and is on demand, so users only pay for AWS resources.
Logverz is designed for resilient teams.
Our unique solution goes beyond traditional dedicated servers and key/index systems.
Its distributed system leverages Amazon S3 for storage and lambda functions to collect and filter CSV or JSON data (such as web server logs or CloudTrail) and put matching data on the SQL database for further analysis.
The two-tier system is perfect for analysis.
It combines the speed and flexibility of distributed computing to reduce large datasets with the maturity and ease of SQL-based solutions for in-depth data analysis.
Single-page web application
The client uses a single-page web application accessible to API gateway. Requests are authenticated via JSON web tokens and authorised by custom logic.
Log collection begins by starting a controller which scans S3 and invokes lambdas that filter the data and insert SQL.
Data in SQL is retrieved
via SQL proxy and sent by “hardened” relay in DMZ. This ensures minimal web exposure with internal access only.