Cost calculator

Enter your own hours and hourly rate. The result also shows when Secvalis costs more than the work it saves.

Your starting point

I do it manually todayI still have to start

Number of machines

How many hours per month do you spend manually collecting and compiling vulnerability findings today?

Include running a scanner (e.g. Trivy), storing results, sorting the list, making an action plan and preparing a report. Exclude the updates themselves, tests and maintenance windows.

Company cost of an admin hour (net)

Employee: gross × employer cost / 168; contractor: invoice net / 168

How many hours per month remain with Secvalis?

Reviewing the task list, checking scans and commenting on the report.

Calculate hours from steps

Minutes per server

Servers

Times per month

Calculations run in your browser. We do not send your entered times, rate or result. The analytics event contains only a machine count range.

What the subscription costs per machine

Starter

up to 10 machines, ≈ €49.00 per month

≈ €0.16per machine per day

Pro

up to 50 machines, ≈ €149.00 per month

≈ €0.10per machine per day

Business

up to 200 machines, ≈ €499.00 per month

≈ €0.08per machine per day

Enter your numbers and press Calculate to compare it with your own work.

What hours do not show

Besides the time saved, the subscription includes:

History of every scan
Scan history shows CVE counts, changes and CSV/PDF exports.
Tasks instead of a CVE list
Package tasks organise vulnerability work.
Priorities from CVSS, EPSS and KEV
CVSS, EPSS and KEV help assess a vulnerability.
Remediation deadlines
Set remediation deadlines per account; the KEV threshold can shorten them.
Management report
Management reports can be sent to eligible recipients on a schedule.
Evidence for the auditor
Evidence Pack bundles reports, registers, data and a SHA-256 manifest.

A daily scan shows what happened on each day

The Secvalis agent can scan a machine every day: set up cron or a systemd timer, the agent prints ready examples with --schedule-help. Saved scan results land in the machine history with the date, vulnerability counts by severity and the change since the previous scan, so you see the state on a given day, not only on the day of a manual review. A failed run leaves no entry, its cause is in the agent log on the machine.

Manual review: 1× per month

Results per month

Longest gap

29 days

without fresh data

Secvalis with a daily schedule

Results per month

Longest gap

0 days

when every daily run succeeds

Empty squares are days without a scan result. The manual count follows "Times per month" from the hours helper.