Skip to main content
Version: 0.10

Velum Edge

Velum Edge builds and maintains an inventory of what you run: endpoints, subnets, applications, users and licences. It collects that inventory through sensors you deploy inside your network, which read the security and IT tools you already operate and probe the network directly, then correlates what every source reports into one record per real thing.

It is multi-tenant: your Organization holds one or more tenants, each with its own isolated inventory, sensors, integrations, scans and reports, and users are given access tenant by tenant through roles.

New here?

Start with the Quickstart to get a tenant collecting data, then read Core concepts for the model the rest of these docs assume. Inside the console, the getting-started guide walks you through the same steps.

What the platform does​

CapabilityWhat it means in practice
Five asset typesSeparate lists for Endpoints, Subnets, Applications, Users and Licenses, each with its own fields, search, bulk edit, import and export. See Assets and Asset types.
SensorsA collector you run inside your network. Every integration run and every network scan happens on a sensor, which connects out to the console over HTTPS. See Sensors.
IntegrationsConnections to tools you already run (EDR, directories, cloud, vulnerability scanners, network detection) plus an active network scanner. See Integrations.
ScanningA scan template says what to collect through one integration and how to treat the results; you run it on demand or on a cron schedule, then review the changes it proposes. See Scanning.
CorrelationRecords from different sources that describe the same thing are matched to one asset. Where a record matches more than one, the run waits for you to decide.
WizardFinds duplicate assets, name conflicts and invalid names in the inventory so you can merge, fix or exclude them. See Wizard.
DashboardsCharts over the tenant's assets, scoped by search and filters, with drill-down into the inventory. See Dashboards.
ReportsOn-demand exports: a CSV asset list, or an Excel report built from a template. See Reports.
ModulesOptional screens switched on per tenant: Coverage, Decommissioning, License Optimization and Vulnerabilities. See Modules.
AdministrationTenants, users, global and tenant roles, and Organization settings, under System management. See Organization.
APIThe REST API the console itself uses, available with a session or a personal API token. See API overview.

How to read these docs​

  • Getting started: first tenant, first sensor, first integration, first scan.
  • Console: finding your way around, dashboards and notifications.
  • Platform guide: one page per area of the console: assets, sensors, integrations, scanning, the wizard and reports.
  • Modules: the optional, per-tenant modules.
  • Administration: tenants, users, roles, account security and your profile.
  • API reference: wire conventions, authentication and limits.
  • Release notes: what changed in each release.

Versions​

This documentation is versioned alongside the product. Use the version selector in the top-right to switch; you are currently reading the docs for the release shown there.