Skip to main content

​
Overview

This page exists so you can assess the impact of Velatir for Desktop on your fleet without having to ask. Every figure below is measured on a running installation rather than estimated, and the measurement method is stated so your own numbers are comparable.

​
Supported platforms

No separate .NET runtime is required. The application ships with its own, so nothing needs installing or patching on your machines.

​
What gets installed

That is the whole footprint. No driver is installed, on Windows or anywhere else. Where network capture is not enabled for your organisation, no traffic is redirected and no certificate is placed in the machine’s certificate store. See How it works.
In neither case is a filesystem filter driver or a process monitoring driver installed, so Velatir does not add anything to the driver layers that typically conflict with endpoint security products.

​
Memory

On a machine with 8 GB of RAM that is roughly 0.7% on Windows and 2% on macOS.
The two columns are not measured the same way, so the real difference is smaller than it looks. Windows Task Manager reports the private working set, which excludes shared libraries. The macOS figure comes from ps, which counts resident shared libraries too. The genuine part of the difference is that the Windows version runs no capture engine and no graphical layer.

​
CPU

Under 1% of one core on both platforms, measured over a window long enough to include the periodic background work. Expressed the way Task Manager and Activity Monitor show it, as a share of the whole machine, that is around 0.1% on a typical 8-core laptop. Consumption is not constant. It consists of short peaks when the periodic tasks run, with idle in between. There is no continuous document scanning, no filesystem indexing and no background content analysis.
To measure it yourself, compare consumed CPU time across a window of several minutes rather than reading the instantaneous percentage. A one second sample lands either on a peak or in the idle gap, and neither is representative. Note also that Task Manager’s percentage is a share of all cores, so it is not directly comparable to a per-core figure.

​
Disk

The installed footprint covers two versions: the current one and the previous one, so an update can be rolled back without downloading anything again. Only those two are kept, so the footprint does not grow as you take updates.

​
Network

These are small JSON calls with negligible bandwidth. The item that matters when planning a rollout is updates: each device downloads roughly 289 MB per new version from our CDN. Across 1,000 devices that is about 290 GB per update. If that is a consideration for your network, contact support to be put on a per-tenant update channel, so you control when a version is rolled out and can schedule it outside working hours.

​
Next steps

How it works

What is inspected on each platform, and what is not.

Permissions

What the installer asks for on each platform.

Enterprise deployment

Rolling out with Intune, Jamf Pro or any MDM.

VPN compatibility

Behaviour alongside corporate VPNs.