Software Asset Management · Endpoint Management & Command Center formerly Argus SAM

Argus

Which software, on which device, under which licence? Argus answers on one screen.

Argus inventories every installed and running application on endpoints, produces licence and cost visibility, detects Shadow IT, maps CVE risk onto device inventory and deploys MSI packages remotely. It is also the shared agent and command backbone of the Argus product family.

Argus
Kurulu + Çalışan Dual-layer software inventory
Hash & sürüm Verified software identity
MSI Remote package deployment
CVE Risk mapped to inventory

Product story

Licence audits, software waste and unapproved applications are invisible cost lines in most organizations. Argus grounds inventory in real data collected from individual machines: which version, which hash, how many seats are actually used? Shadow IT policy, CVE risk mapping and remote deployment are layered on the same inventory. The result: software cost and attack surface managed in one console.

Capabilities

Software inventory

Installed and running applications collected with version, hash, publisher and install date.

Licence & finance

Seat usage, contract renewal dates and savings potential from unused licences.

Shadow IT control

Black / whitelist policies detect unapproved applications with warn, block or remove actions.

CVE risk mapping

Known vulnerabilities are mapped to device and software inventory, listing the machines actually affected.

Remote deployment

MSI packages deploy remotely to selected device groups with results and failures reported by the agent.

Family backbone

The Argus agent is the shared telemetry and command channel for Identity, DREMP, SAM and Browser.

Savings analytics

Unused seats, duplicate licences and multi-version costs are reported, supporting decisions before renewal.

Identity alignment

User–device–software relationships align with Argus Identity and AD / Entra data.

What it solves and what it returns

Problems today

  • Licence audits unable to answer “how many seats are actually used?”
  • Unnecessary licence spend every year for unused software
  • Shadow IT and security gaps growing through unapproved apps
  • CVE lists without knowledge of which device is affected
  • Software updates dependent on separate packaging tools
  • Inventory disconnected from finance data

Outcome with the product

  • Measurable savings in software licence cost
  • Shadow IT visibility with enforceable policy
  • CVE risk mapped onto real device inventory
  • Centralized patching and update processes
  • Argus family products managed through one agent

Modules and scope

  • 01 Software inventory & hash database
  • 02 Licence seat & contract management
  • 03 Finance and savings reports
  • 04 Shadow IT policy engine
  • 05 CVE mapping and risk scoring
  • 06 MSI package deployment
  • 07 Endpoint command & plugin areas
  • 08 Role-based administration and audit trail

Architecture and technology

Architectural approach

Argus consists of endpoint agent telemetry, a .NET backend API and the Software Asset Management area inside the Dashboard. The agent collects installed applications, version and hash data, running processes and hardware inventory. The backend merges this with licence, contract and cost models; the CVE mapping and Shadow IT policy engine run on the same inventory. Package deployment and plugins execute in isolated controller areas.

Technology stack

Argus ajanı (Flutter / native) .NET Backend API PostgreSQL Argus Dashboard (Sam & Plugins alanları) MSI / paket dağıtım hattı AD / Entra hedefleme

Where it fits best

Large Windows fleets and annual licence audits

Security and asset teams needing a shared inventory

Software standardization and package rollout

Shadow IT cleanup campaigns

Patch management and version compliance

Frequently asked questions

Does it work with SeeNose?

Yes. Both products can share the same agent backbone; SeeNose governs operations and performance while Argus governs software and licences.

Which platforms are supported?

Full support for Windows-heavy fleets; Linux and macOS inventory is collected on the same schema.

Where does licence data come from?

Contract and seat data are defined in the admin console; usage data comes straight from agent telemetry.

How long does deployment take?

A typical pilot environment is ready in 1–2 days; enterprise rollout is planned with phased agent deployment.

Request a Argus demo

Let's schedule a 30-minute walkthrough built on your own scenario, then define the pilot scope together.