Lumen Edge
Book a demo

How it works

From scattered signals to one trusted inventory.

Lumen Edge collects from your network and the tools you already own, reconciles every record through a five-stage pipeline, and keeps you in control of what enters the inventory.

Book a demo

Four steps

Up and running in an afternoon.

Deploy a lightweight sensor where your networks are, connect the tools you already own, and let the pipeline do the reconciliation.

  1. 1

    Deploy a sensor

    One per site or segment, on Windows, Linux, macOS or as a container. It connects out; nothing connects in.

  2. 2

    Connect your tools

    Pick integrations from the catalog and add read-only credentials in the console.

  3. 3

    Scan & correlate

    Scheduled scans feed a five-stage pipeline that verifies, cleans, identifies, validates and syncs.

  4. 4

    Act on it

    Dashboards, coverage gaps, approvals, reports and API: the inventory works for every team.

The pipeline

Five stages between a raw record and your inventory.

Every scan and every integration goes through the same path. Nothing reaches the inventory without being checked, matched and explained.

  1. 01

    Verify

    Every scan result is checked before it is trusted: where it came from, which task produced it and whether it is complete.

    Partial or malformed uploads stop here.

  2. 02

    Clean

    Hostnames, domains, MAC addresses, operating systems and versions are normalized, so every tool speaks the same language.

    “ADC01”, “adc01.corp.local” and “ADC01$” become one name.

  3. 03

    Identify

    Ordered, explainable rules (agent ID, hostname and IP, FQDN, directory name) match each record to an existing asset or create a new one.

    Conflicting signals are held back, never guessed.

  4. 04

    Validate

    Proposed changes are checked against your policies. Anything sensitive (a new device, a merge, a removal) can wait for approval.

    You decide what enters the inventory.

  5. 05

    Sync

    Approved changes land in the inventory with full history, and every dashboard, module, report and API consumer sees them at once.

    Each field remembers which source set it, and when.

See the correlation engine in action

Your first week

From kick-off to a tuned inventory.

  1. Day 1 · morning

    Kick-off

    We scope sites, sources and success criteria with your team in a 60-minute session.

  2. Day 1 · afternoon

    First sensor, first tools

    Install a sensor, connect two or three integrations and run the first scans.

  3. Day 2–3

    A correlated inventory

    Records from every source are reconciled. Coverage gaps and unknown devices are already visible.

  4. Week 1

    Tuned for your teams

    Approval policies, custom fields, dashboards and reports, set up together with our engineers.

Built for security teams

Safe to connect, from the first scan.

Lumen Edge is designed to be deployed by people who are careful about what they let into their network. Read about security & trust.

  • Sensors connect outbound over HTTPS, with no inbound ports, no VPN
  • Integrations use read-only credentials you create and can revoke
  • No endpoint agents to roll out, patch or troubleshoot
  • Data isolated per tenant, and all traffic encrypted with TLS
  • Approval queues for anything that changes the inventory
  • Every change is logged with who, what, when and the rule behind it

FAQ

Questions about getting started

How long until we see results?
Most teams see their first correlated assets on the day the sensor is installed. A tuned inventory with approvals and dashboards typically takes about a week.
Do we need to install agents on endpoints?
No. Lumen Edge uses the tools you already run (EDR, directory, MDM, cloud, SIEM) plus active and passive network discovery from a sensor. Nothing is installed on endpoints.
What does the sensor need?
A small virtual machine, server or container per site or segment, with outbound HTTPS to the platform and network reach to what it should scan or query.
What happens when two sources disagree?
The engine follows ordered rules and stops when signals conflict, instead of guessing. The conflict is shown with its reason, so a person can resolve it once and the decision is remembered.
Can we run it fully on-prem or air-gapped?
Yes. The same platform runs as SaaS, on-prem or air-gapped, with manual result upload for isolated sites. See deployment options.

See it on your own data.

In a 30-minute walkthrough we connect to a sample of your environment and show you the inventory it produces.

Book a demo

SaaS or on-prem · no endpoint agents · every module included