Security data pipeline for Windows

A complete security data pipeline in every Windows agent

DPLens is a distributed pipeline at the edge for SOCs and MSSPs. Your data is processed, masked and reduced on your own machines before it leaves, and sent only where you choose, with no central processing server to run. DPLens Manager manages the agents centrally, with full support for multi-tenant environments, and there is no ingestion pricing.

  • Windows x64
  • A complete pipeline in every agent
  • No central processing server
  • DPLens Manager included
  • No ingestion pricing

Distributed pipeline at the edge

Five things that define the platform

The work moves to the edge, so the centre only has to manage, and the price stops following volume. See how a distributed pipeline compares with a central tier.

01

No central processing server

The processing runs in the agents, so there is no processing tier to size, host, patch, scale or make highly available.

02

A complete pipeline in every agent

Every agent runs the full pipeline on your own machines, with no vendor cloud or control plane. Data is processed, masked and reduced before it leaves, and sent only where you choose. See the stages.

03

A highly optimised agent

Performance is what makes the edge possible: the agent is efficient enough to leave room for a complete pipeline. In our lab benchmark, it delivered more than 30× the throughput of the popular free and paid Windows agents we tested, at about a tenth of the CPU per event. Lab figures, not a guarantee: measure it on your own servers, with your own pipeline rules.

04

Central management, included

Manage centrally. Process at the edge. DPLens Manager is included in every subscription. See DPLens Manager.

05

No ingestion pricing

Licensed per agent and per network source, so your data volume never sets the DPLens price. Reducing what reaches your SIEM is a separate saving, wherever your SIEM prices by volume. See pricing.

Architecture

One agent per Windows host, managed centrally

DPLens is a UK-built, self-hosted, distributed security data pipeline at the edge for SOCs and MSSPs, delivered as a log collection agent for Windows. Each machine runs one signed agent as a Windows service. Reduction happens on your own machines before data leaves, so the SIEM only receives what you chose to send.

DPLens ManagerCentral configuration, fleet health, deployment and upgrades. Event data never reaches it.
Firewalls, switches and appliancesSend syslog and NetFlow to the agent's receivers
Every Windows host
DPLens agent one signed Windows service
Collect On the host
  • Windows Event Log
  • Log files
  • File integrity
From your network
  • Syslog receiver
  • NetFlow and IPFIX receiver
Process
  1. Filter
  2. Parse and normalise
  3. Aggregate
  4. Optimise
  5. Enrich
  6. Mask
  7. Rate limit
Deliver To one destination or several at once
Destinations you chooseYour SIEM, data lake or collector receives only what you chose to send
How data moves through one DPLens agent Collection, all seven processing stages and delivery run inside the agent, on your own machine. DPLens Manager manages the DPLens agent, and event data never reaches it. Each Windows host runs one DPLens agent. The agent collects Windows Event Log, log files and file integrity on the host, and receives syslog and NetFlow or IPFIX from firewalls, switches and appliances. It then processes events through seven stages in order: filter, parse and normalise, aggregate, optimise, enrich, mask and rate limit. It delivers directly from the host to the destinations you choose.

01

Self-contained

One signed installer is all a host needs. There is nothing else to install or patch alongside it, and no internet access is required.

02

Configuration as code

Define a configuration once, review it, keep it in source control and apply it across your fleet. Credentials are kept out of it.

03

Rolled out your way

Deploy and upgrade with DPLens Manager, or with the tools you already use: Group Policy, Intune, Configuration Manager or an RMM, plus golden images and VDI. See deployment.

Sources

Collect the security data you already rely on

Every source runs through the same pipeline, so your Windows logs, files and network data are all processed before they leave. Collection resumes exactly where it stopped after a restart, upgrade or pause, so nothing is read twice or skipped.

Each enabled syslog or NetFlow receiver is one network source for pricing, however many devices send to it: one syslog receiver taking events from 500 firewalls is one network source. See pricing.

Pipeline

What happens between collection and delivery?

Seven processing stages, always in this order: filter, parse, aggregate, optimise, enrich, mask, rate limit. Run several pipelines, each delivering to several destinations at once. Every drop, mask, aggregation and failover is counted and attributed to the rule that caused it.

Filter

Keep or drop events with rules that test values, text, patterns, numbers, lists and network ranges, combined however you need. Example: keep Event IDs 4624, 4625, 4634, 4688 and 4720, and drop those whose target user name ends in $ (machine accounts).

keep / drop rules filter by any field counted drops
Filter Filter drops events you never want to pay to store — 9.2M directory-object reads become none. ×
Action
Drop matching events Keep only matching
Conditions
Match All of the following ⌄
EventID is one of ⌄
4662 — Operation on a directory object ×
4663 — Attempt to access an object ×
e.g. 4662, 4663
×
Type a value and press Enter.
ProcessName is ⌄ e.g. Security ×
+ Add condition
Drop where EventID in 4662, 4663
Paste a sample event
Test with a sample
← Filter Cancel Add rule

Destinations

Send your data wherever you choose

DPLens works with the SIEM you already run, so your analysts keep working where they work today. Processed data goes straight from each agent to the destinations you choose, and you can change them as your needs change.

Send to more than one

One pipeline can deliver the same processed events to several destinations at once, such as a hot SIEM and a low-cost archive.

Move at your own pace

Run your current destination and a new one side by side while you migrate, then retire the old one when you are ready.

Ride out an outage

On syslog, Snare, JSON and Splunk destinations, delivery fails over to your next address and events queue on disk until the receiver recovers. Any drop is counted.

Formats and transports are in the destination documentation.

DPLens Manager

Manage centrally. Process at the edge.

DPLens Manager manages your agents and does not process your data, because the pipeline stays in every agent, and event data never reaches it. If Manager is unavailable, deployed agents keep collecting and delivering on their last configuration. It is included in every DPLens subscription, and gives you central configuration, fleet health monitoring, and deployment and upgrades for your DPLens agents, on your own infrastructure.

Central configuration

Manage the configuration of your DPLens agents centrally, rather than machine by machine.

Fleet health monitoring

Watch the health of every DPLens agent across your estate.

Deployment and upgrades

Deploy DPLens agents and keep them up to date across the fleet.

Self-hosted and air-gap capable

DPLens Manager runs on your infrastructure, including in air-gapped networks, with no vendor cloud involved.

Does DPLens support multi-tenant environments?

Yes. Whether you run one estate or many customers' estates, DPLens Manager has full support for multi-tenant environments. See DPLens Manager in a demo.

How this plays out for your team: DPLens for SOCs and DPLens for MSSPs.

Operations

A console on every host, and health you can alert on

Alongside DPLens Manager, each agent serves its own web console for hands-on inspection. It is reachable from the local machine until you allow other networks.

Overview

Events a second, a per-stage funnel of what each rule removed, estimated GB a day out, losses by cause and what the reduction is worth at your cost per gigabyte.

Recommendations

A local scan of the machine's roles, services, disks and audit policy suggests what is worth collecting. Nothing is sent anywhere.

Live stream

Events as they leave, encoded exactly as the destination receives them, in masked form. A test event proves the path end to end.

Staged changes

Edits are validated and applied as one set, and a set that comes back unhealthy offers one-click roll back.

Health and audit

Components report Healthy, Degraded, Restarting or Quarantined, and a failing source is isolated so the rest keeps running. A tamper-evident audit trail records every change.

Backup and upgrades

Back up the configuration and licence, and working state rebuilds itself. In-place upgrades keep configuration, licence, credentials, collection positions, queued events and the audit trail.

Requirements

What does DPLens run on, and what should I provision?

DPLens runs on the Windows machines you already have, with nothing else to install first.

Windows x64

Windows Server 2025, 2022, 2019 and 2016, and Windows 11 and 10. Server Core is supported.

Nothing else to install

One signed installer, with no .NET, Java or database to install first and no internet access required.

What to provision

Allow 150 MB of memory, 30 MB for the program and 1 GB of working state, plus any disk cache you size for your destinations. CPU is low at idle and scales with your event rate.

Full requirements

Network, permission and sizing details are in the requirements documentation.

Performance

Performance is what makes the edge possible

A pipeline only belongs at the edge if your hosts can carry it. The DPLens agent is highly optimised, and that is what allows a complete pipeline to run on the hosts you already have, with no new processing infrastructure to add. In our lab benchmark, DPLens delivered more than 30× the throughput of the popular free and paid Windows agents we tested, at about a tenth of the CPU per event, with no events lost.

30×+the throughput of the popular free and paid Windows agents we tested
~1/10of their CPU per event
~26,000events delivered per second on one 8-core server
0events lost
Lab benchmark results, medians
MeasureDPLensPopular free and paid Windows agents tested
Events delivered per second25,956–27,515601–855
Box CPU per event103–112 µs1,127–1,834 µs
Events lostNoneNone
How we measured
  • DPLens release build against popular free and paid Windows agents, which we do not name.
  • One 8-core Xeon E5-2430 v2 machine, the same for every agent.
  • The same Windows Event Log channel of 11,364,792 records, read into the same loopback receiver.
  • Each agent in its native wire format; DPLens in Snare, Splunk S2S and NDJSON.
  • Three 60-second repetitions per agent, reported as medians.

Lab figures, not a guarantee: real throughput depends on your hardware, sources and pipeline rules. Request an evaluation licence and measure DPLens on your own servers, with your own pipeline rules, or contact us to discuss the benchmark.

Where it fits

Who is DPLens for, and where do I start?

DPLens is built for SOCs and MSSPs running Windows estates. The pipeline runs in each agent, so what you remove never reaches your SIEM's meter and there is no central processing server to build or run. Read how a distributed pipeline compares with a central tier.

Most teams come in through a job they have today, such as replacing a log agent or cutting SIEM ingest. See the solutions, SIEM integrations, comparisons with other agents and pipelines, the savings calculator, the Trust Centre and the licensing model.

Secure by design

An agent you can defend in a security review.

Signed and verifiableEvery release is signed and ships with checksums and a software bill of materials, so you can verify it before it reaches a server.
Nothing calls homeNo telemetry, no licence server and no automatic updates. Your data goes only where you send it.
Secure engineeringBuilt and tested to modern secure-development practice, for software that runs on your most sensitive servers.
Least privilegeRuns with only the access it needs, with administration kept apart from collection.

FAQ

Questions buyers ask

What is DPLens?

DPLens is a UK-built, self-hosted, distributed security data pipeline at the edge for SOCs and MSSPs, delivered as a log collection agent for Windows. It processes, masks and reduces event logs, files, file integrity, syslog and NetFlow on your own machines, then delivers to Splunk, OpenTelemetry (OTLP) or any syslog or JSON SIEM.

Does DPLens work with the SIEM we already run?

Yes. DPLens collects, reduces and delivers log data to the SIEM you already run: Splunk natively, over cooked S2S or HEC, and any SIEM that accepts syslog or JSON, including IBM QRadar, Securonix, Devo and Secureworks Taegis. It also sends to any pipeline built on an OpenTelemetry Collector.

Which systems does DPLens run on?

DPLens runs on Windows Server 2025, 2022, 2019 and 2016, and Windows 11 and 10, on x64, including Server Core. Its syslog receiver also brings in events from Linux hosts and network devices.

Which destinations can DPLens send to?

DPLens sends to five destination types: syslog, Snare, JSON collectors, Splunk and OpenTelemetry. That covers any SIEM that accepts syslog or JSON, and any pipeline built on an OpenTelemetry Collector.

How fast is DPLens?

In our lab benchmark, DPLens delivered more than 30× the throughput of the popular free and paid Windows agents we tested, at about a tenth of the CPU per event, with no events lost. See how we measured, then measure it on your own servers, with your own pipeline rules.

Do I need a central processing server to run DPLens?

No. Processing happens in each agent. DPLens Manager, included in every subscription, handles central configuration, fleet health monitoring, and deployment and upgrades. See how a distributed pipeline works.

Is there central management?

Yes. DPLens Manager, included in every subscription, provides central configuration, fleet health monitoring, and deployment and upgrades for your DPLens agents. It is self-hosted and air-gap capable. Each agent also has its own console for local inspection.

Does DPLens charge by data volume?

No. DPLens has no ingestion pricing: it is licensed per agent and per network source. See pricing.

See it on your own logs

Try DPLens on one Windows server before you talk to anyone.

Book a demo, or request an evaluation licence and install it on a test host. The documentation covers everything from requirements to Group Policy rollout.