Managed operations — workplace, server, network — are the core. Everything here is an accessory: often recommended, never mandatory. Every block stands on its own invoice line and can be cancelled on its own.
The blocks at a glance
| Block | What it does | Billing |
|---|---|---|
| Endpoint protection (EDR) | Active defence on the device, monitored 24/7 | per device |
| Identity protection (ITDR) | Protects user accounts against takeover | per account |
| Managed SIEM | Logs collected centrally and analysed | per data source |
| Backup | Protection with restore tests and a log | per system |
| Licences & Microsoft 365 | Procurement and care, itemised | per user |
| Zero-trust access | Company access verified per request instead of VPN | per user |
| Hosting | Cloud, EU data centre or your house — decided by numbers | per workload |
| Hardware | Procurement, rollout — device and labour as two lines | per device |
Every block has its own page with the what, why and who-for — the name links there.
The principle behind it
Mandatory bundles are convenient — for the provider: the flat fee grows, the components blur, switching becomes expensive. We believe the opposite: whoever always sees what they pay for, and could always leave, stays for the right reason.
FAQ
Can I buy add-ons without managed operations? In exceptions, yes — licences with administration, for instance. A protection block or a backup without ongoing operations delivers only half its value, though: the part that monitors, maintains and reacts is missing.
What happens to existing licences and contracts? They go into the assessment. What is good stays — equivalent existing protection gets operated, not replaced.
Does an add-on bind me longer than the main contract? No. Add-ons follow the operations term or can be cancelled sooner. The exception is vendors’ annual licence terms — disclosed before you sign.