New: vulnerability scanning and Live queries in the agent

One agent. Every server. Full control.

One install on every Linux and Windows machine for logs, vulnerability scanning and Live queries, with server groups and a control plane in the EU. The LogPulse agent builds on Vector, the standard collector, so you keep the runtime you know without managing every host by hand.

Latest version v0.9.4 · Linux and Windows · Read the docs

Run the whole fleet from one place.

One install, server groups you can reason about and an EU control plane, wrapped around Vector: the collector you already trust.

Install once

One command. Every box reporting in.

One command puts the agent on a Linux or Windows host. It registers itself, joins its group and starts shipping, with no per-machine config to babysit.

bash
$ curl -fsSL https://logpulse.io/install.sh | sh
✓ agent installed
✓ registered to group: web-tier
web-01connected
web-02connected
db-01connected
Groups, not filesets

Manage tiers, not config files.

Group servers by what they are, pick their inputs from a catalogue, and roll a change to the whole tier at once, from one EU-hosted control plane.

Fleetcontrol plane
web-tier· 12 agentshealthy
nginxjournald
db-tier· 4 agentshealthy
postgresql
edge· 6 agents1 updating
syslogfile
Standard runtime

The collector you trust, finally easy to run.

The agent wraps Vector, the open, standard collector, so you keep the runtime and VRL you know and skip the fleet-management headache.

Runtime
LogPulse control planeEU-hosted
Vector· the standard collector
VRL transformsyour sourcesyour sinks
keep the runtime you trust, skip the management

Built for teams running a mix of Linux and Windows servers

If you run Ubuntu, Debian, RHEL, Kubernetes nodes and Windows Servers side by side, you know the pattern: every collector has its own packaging, every host needs its own API key and adding a log source means logging in to every machine. With LogPulse you install the agent once, attach it to a group and every config change rolls out on the next poll.

Built into the agent

See which machines are actually vulnerable

The agent scans for vulnerabilities itself. It reports the installed software of every server and workstation and runs signed sensors from the Intelligence Hub. LogPulse matches that every hour against known and exploited CVEs, so you see per host which flaws are really open, with the evidence. You do not need Trivy, Grype or another scanner for it.

Sensor result per hostExample
CVE-2024-3094
xz-utils / liblzma (backdoor)
  • web-01Vulnerable
  • web-02Not vulnerable
  • win-app-03Insufficient privilege

Evidence per host: package and file version as the agent read them.

Software inventory per host

The agent reports which software runs: dpkg, rpm and apk on Linux, installed programs, updates and the build number on Windows. LogPulse matches it every hour against the advisories of the distributions and Microsoft, so a backported fix does not linger as a vulnerability.

More than 200 signed sensors

High-impact CVEs get a sensor in the Intelligence Hub: a fixed question about a package version, file, registry key, process or port that returns hard evidence. New sensors reach your agents by themselves and the agent only runs signed ones.

Read-only, no scripts

Sensors only read. There is no script layer and no shell, with fixed limits on time, CPU and files touched. The host keeps an allowlist the server cannot change.

From CVE to proven mitigation

Results feed the same chain as your detection rules: exposure in the Intelligence Hub, a mitigation with a deadline, a ticket in your ITSM and a check afterwards. So "mitigated" shows the flaw is really closed.

Works without root or administrator

Sensors also work when the agent runs without root or administrator rights. What it may not read, it reports as insufficient privilege instead of guessing, so you know where your blind spots are.

European sovereign

Inventory and results go to your own LogPulse environment at a European cloud provider. No CVE database runs on your hosts and nothing goes to a scanner outside the EU.

Software inventory and sensors are on every plan, Free included, and need agent 0.9.1 or later. You find the results per host on the Agents page and per CVE in the Detection Hub. LogPulse does not roll out patches: it shows what is open and proves when it is closed.

How vulnerability scanning worksWant to see it on your own hosts? Book a demo

Live queries

Ask your whole fleet a question

Is Remote Desktop off everywhere? Which hosts listen on port 3389? What does PasswordAuthentication say in sshd_config? Ask your agents and see the answer per host within seconds. Schedule the question and every change lands in an index, ready for an alert.

Live queryExample
Is Remote Desktop off?
Registry value fDenyTSConnections is 1
  • win-app-011As expected
  • win-app-020Not as expected
  • win-dc-011As expected
  • win-kiosk-04–Could not check

The agent answers with the value it read, LogPulse compares it with what you expect.

Answers in seconds

The question goes straight to the agents over their open connection. Per host you see the value found, or whether it matches what you expect.

Templates to start from

Ready-made questions for security, configuration, software and workloads fill the form in one click. Or ask your own about installed software, a registry value, a setting in a config file, a file or a process.

Ports and firewall rules

See every listening port per host and the rules of Windows Firewall, ufw or firewalld. A port that opens or a block rule that disappears becomes a change event you can alert on.

Scheduled queries

Keep a query running every hour, six hours or day. Every change, and once a day the full answer, goes to an index of your choice. Part of Pro and Business.

No scripts, no shell

Live queries use the same read-only building blocks as the sensors. There is no PowerShell, WMI or shell, and paths or keys that look like secrets are refused.

Honest about blind spots

An agent without root or administrator rights answers "Could not check" where it may not read, never "Not found". So a missing answer never looks like a safe one.

Live queries are on every plan and need agent 0.9.3 or later. You find them on the Agents page, tab Live queries.

Read the Live queries docs

How it works

1. Install with one command

Run the install script with a short-lived enrollment token: curl on Linux, PowerShell on Windows. It fetches the bundled Vector binary, verifies the checksum, registers the host with the control plane and stores a credential per agent.

2. Drop it in a group

Assign the agent to a server group from the UI: prod-edge, staging, db-cluster, whatever you call them. Moving an agent between groups is a one-row update, not a reinstall.

3. Inputs flow automatically

Attach syslog, journald, file, docker or kubernetes inputs to a group. The agent polls every 30 seconds, rewrites its Vector config, and SIGHUPs the runtime: zero log loss, no manual restart.

Download the agent

The latest version for Linux and Windows. The install script is the easiest route; the command with your own token is on the Agents page in LogPulse.

Latest versionv0.9.4

Linux

curl -fsSL https://get.logpulse.io | sudo sh

For x86_64 and ARM64 with systemd. The script picks the right architecture.

Windows (PowerShell as administrator)

irm https://get.logpulse.io/install.ps1 | iex

For Windows x64 and ARM64 (ARM64 on Windows 11). The script picks the right architecture. Installs the LogPulseAgent service and reads the Windows Event Log and IIS logs.

Manual download

Rolling out yourself, for example with Ansible, Intune or an image? Download the package for your platform.

Linux
Windows

Every package has a SHA-256 checksum and a cosign signature (keyless, from GitHub Actions). The install script always checks the checksum, and the signature whenever cosign is on the host. Downloading by hand? Then verify them yourself.

Need a fixed version? Set this for the install script: LOGPULSE_VERSION=v0.9.4

More than collection: parsing and data modeling included

The LogPulse agent doesn't just ship raw lines. We parse each vendor's format and map it onto a shared data model (authentication, firewall, dns, endpoint, security-event) so the same LPQL query works across every source. Below are a handful of the built-in templates; more roll out continuously.

OpenSSH

Authentication

SSH login attempts from syslog: source IP, port, user and success/failure extracted from every Accepted and Failed line.

authentication

Linux auditd

Audit

Linux audit records routed automatically: USER_LOGIN to authentication, SYSCALL/EXECVE to endpoint, everything else to security-event.

authenticationendpointsecurity-event

Fortinet FortiGate

Firewall

FortiGate firewall, UTM and event logs split into traffic and security-event records: source/destination IPs, ports, action and policy ID.

firewallsecurity-event

Palo Alto PAN-OS

Firewall

PAN-OS CSV decoded into firewall (TRAFFIC) and security-event (THREAT) records, including source user, app-id and zone pairs.

firewallsecurity-event

pfSense / OPNsense

Firewall

filterlog CSV parsed into pass/block decisions with full 5-tuple, interface and direction, ready for firewall data-model queries.

firewall

UniFi gateway

Firewall

fleetPage.templates.items.unifi-firewall.description

firewall

dnsmasq

DNS

DNS queries and blocks from UniFi gateways, OpenWRT and Pi-hole: domain, record type and client IP normalised to the dns data model.

dns

Plus sudo, PAM, iptables/ufw, hostapd and Cisco ASA, with more added continuously. Every parser maps onto the same data model so cross-vendor dashboards just work.

Why a fleet model

One command, every host

One install script for the major Linux distros and one for Windows. No package repositories to add, no fleet-wide secrets to rotate.

Logical server groups

Group hosts the way you already think about them. Attach inputs to groups, not individual hosts.

Control plane in the EU

Enrollment, config polling and heartbeats go through api.logpulse.io at Scaleway in Amsterdam, a European cloud provider. The management path does not cross the US.

Per-agent credentials

Each host gets its own token. Revoke one agent without rotating the rest, audit who shipped what, and move agents between groups without re-enrolling.

Frequently asked questions

Which systems does the LogPulse agent run on?
Linux (x86_64 and ARM64, systemd distributions such as Ubuntu, Debian, RHEL, Rocky and Alma) and Windows x64 and ARM64 (Windows 11). On Linux it reads syslog, journald, files, Docker and Kubernetes; on Windows the Windows Event Log and IIS logs.
Does the agent need to run as root or administrator?
The installer runs once as root or administrator to create the service. From version 0.9.1 the agent can then run without those rights (restricted mode): it only reads what its own user may read, and you upgrade it by running the install script again.
How do I check that a download really comes from LogPulse?
Every package has a SHA-256 checksum and a cosign signature, signed keyless from GitHub Actions. The install script always checks the checksum, and the signature whenever cosign is on the host.
How do I upgrade the agent?
Run the install script again: it fetches the latest version and keeps your configuration and group. In standard mode you can also upgrade from LogPulse. For a fixed version, set LOGPULSE_VERSION for the script.
Does the agent scan for vulnerabilities itself?
Yes. From version 0.9.1 the agent reports the installed software of every host and runs more than 200 signed sensors from the Intelligence Hub. LogPulse matches that every hour against known and exploited CVEs (NVD, CISA KEV, EPSS and the advisories of the distributions and Microsoft). You do not need a separate scanner for servers and workstations. For container images you can still send the JSON output of Trivy, Grype or Snyk.
What can I ask with Live queries?
Anything the agent can read without a script: installed software and versions, a registry value, a setting in a config file, a file, a running process, listening ports and firewall rules from Windows Firewall, ufw or firewalld. You see the answer per host within seconds, or schedule the query so every change lands in an index. Live queries need agent 0.9.3 or later; scheduled queries are part of Pro and Business.
Where do the agent's logs and data go?
To your own LogPulse environment. The shared cloud runs at Scaleway in Amsterdam; a dedicated environment runs in the region you choose. Every agent has its own token, so you can revoke one without touching the rest.

Get logs flowing in under five minutes

Free to start. 1 GB/day, 7-day retention, no credit card. Install the agent on one host today, scale to the whole fleet whenever you're ready.

Create your free account
1 GB/day · 7-day retention · No credit card