Skip to content
Logmetry

About

Telemetry and automation engineers. We solve business problems.

Logmetry designs and builds telemetry pipelines that sit in front of your SIEM, never in place of it, with a full raw copy in your own account and everything as code in your repository. The founders lead every project, and senior engineers build to their design.

The people behind the work

Together, the founders understand the most complex hybrid estates and telemetry at enterprise scale: Zbigniew the logs, telemetry and security on every vendor platform, Christopher the AI-native side and the custom builds. Delivered as code in your repository, or on the platforms you already run, as you choose.

Zbigniew Gajuk

Co-founder, Chief Observability and Security Architect

Zbigniew ran observability for a Fortune 500 healthcare and life-sciences organization as its director of observability and telemetry, and owned the business problems and the technical ones. He understands every log source an enterprise runs: what each one means, what it is worth, and how to combine and enrich them. He led the observability redesign and the Cribl implementation there, which changed how the organization controlled the value of its telemetry and where it lands, and began its control of what the pipeline ingests. That rests on 26 years running monitoring, observability and security on every generation of platform, from HP OpenView, Nagios and SolarWinds through Splunk, Microsoft Sentinel and CrowdStrike, Datadog, Dynatrace and Grafana to Cribl and OpenTelemetry. Zbigniew leads the engineers who build, runs every architecture review personally, and is your named security contact.

Christopher Gajuk

Co-founder, Director of Operations, Sales and Go-to-Market

Christopher leads operations, sales and go-to-market, is your point of contact and escalation point, and helps Zbigniew lead the team. An AI agent and automation expert, he understands how AI agents reason and what they need to read: the runbooks and skills they follow, the token cost of every field, the observability of the agents and the steps to remediation. He has set up and migrated SIEMs in an enterprise estate, hands-on with Splunk, CrowdStrike, Datadog and Dynatrace and the pipelines in front of them, and decides with Zbigniew what to enrich and what to drop. He understands custom, in-house builds as well as vendor platforms, everything as code with CI/CD: the deployment, the tests and the runbooks land in your repository, so your team can operate what we hand over, and the exit is designed into every build.

Senior engineers in telemetry engineering, pipeline design and agentic AI do the build, under the founders, following their design and instructions. The founders understand every change they make, and review it.

Your team: key personnel, day two and the escalation path →

The posture, stated plainly

We sell design and build, not platforms. Step one is a pipeline in front of your SIEM: your SIEM stays, a full raw copy stays in your own account, and the pipeline subscription is in your name. Where a commercial engine is the right tool, we say which one and why, and the honest pros and cons come with it.

Everything we build ships as code in repositories you own from day one, written so your administrators can operate it. We work alongside your staff rather than around them, and we make ourselves as replaceable as we make your vendors, which is why clients keep us.

The boundary

Logmetry is a control layer in front of your SIEM and your monitoring platforms, never a replacement for either.

What we build

  • A pipeline in front of your SIEM, deciding what each destination receives
  • A full raw copy and a clean lake, in your own storage
  • Everything as code, in repositories you own from day one
  • Later, when you want it: governed AI triage, open collection, monitoring you own

What we never do

  • Sell you a detection platform
  • Write your detection content
  • Run your security operations center
  • Replace your SIEM or your monitoring platforms

Work that falls outside those lines we say so about, and point you at the people who do it properly.

See your architecture drawn, with the costs, before you spend anything.

Our lead architects draw your SIEM feed from your diagrams: where the cost sits, what step one would change, and where it would not pay. If it pays, the next step is a two-week proof on your noisiest source.

Free. No system access. No obligation. You keep the drawing.

What you get

  • Your architecture today, drawn
  • The waste map
  • Costs before and after, with estimates
  • Your target architecture
  • Options for your business problem

What it costsNothing