Let me open with something a vendor rarely says: you can do this yourself. CheckMK has a free open source edition, the documentation is excellent, and a technically inclined employee will have a working setup within a weekend. If someone tells you monitoring is too complex for ordinary mortals, that person is selling fear. The real question is a different one: is this where your people’s time should go?
What “doing it yourself” really costs
The installation is the cheap part. What follows is less visible and considerably bigger.
The tuning. A fresh monitoring environment alerts on everything or on nothing. The weeks that follow go into learning what’s normal: that one server that spikes every night, that disk that has sat at 85% for years and is perfectly happy there, that certificate belonging to a service nobody uses anymore. Skip that phase and you end up with a system that makes noise until everyone ignores it. Then you have monitoring, but no watching.
The maintenance. Platform updates, adding new systems, removing old ones, adjusting alert rules as the environment changes. No single item is big, but together they form a quiet background task that never ends.
The continuity. This is the cost everyone underestimates. The colleague who set up the system knows it. What happens when that person leaves, falls ill, or is simply three weeks on holiday exactly when things go wrong? At an SME, monitoring knowledge is almost always one-person knowledge, and that is itself a risk no dashboard will ever show you.
What outsourcing really costs
Outsourcing comes with an invoice, and it’s visible and monthly. Against that stands what’s inside it: the setup and the tuning done by someone who does this for a living, ongoing maintenance, alerts that reach the right person, and the monthly reports you can use in client files and questionnaires. Plus the less tangible part: it’s somebody’s profession to watch your environment, rather than somebody’s task-on-the-side.
In fairness, the flip side too: you don’t build the knowledge in-house, and you have an external party inside your environment. That last point should be openly discussable, including what that party can and cannot see.
Where the tipping point sits
The weighing is fairly predictable. If you have an employee with affinity, time, and a colleague who can take over, doing it yourself is defensible and educational. If one of those three is missing, and at companies up to roughly fifty people one almost always is, outsourcing becomes cheaper the moment you count the hidden hours honestly. The arithmetic gets even clearer once clients or insurers start asking for demonstrable monitoring: then it’s not just about it running, but about it being documented and sustainable.
A third way
It doesn’t have to be all-or-nothing, by the way. A setup where I build and tune the environment, and your own people run it afterwards with me as the safety net, often turns out best in practice: the knowledge lands internally, the continuity is covered.
Unsure which model fits your situation? Book a no-obligation call. If doing it yourself is the right choice for you, I’ll simply tell you so.