Service areas
Five areas. In practice, a single engagement often touches three of them.
AREA 1 — INFRASTRUCTURE & SYSTEMS
Designing and running server foundations: Proxmox VE, ZFS,
Debian/Ubuntu, Windows Server, VMware, LXC and Docker
containers. High availability, cross-node replication,
UPS-driven shutdown orchestration, device passthrough for
specialised workloads.
AREA 2 — NETWORK & SECURITY
pfSense firewall with intrusion detection, VLAN segmentation,
site-to-site and roaming VPN, MikroTik CAPsMAN centralised WiFi,
managed switching and routing. Centralised logging and traffic
monitoring.
AREA 3 — TELEPHONY
Asterisk, FreePBX and 3CX: chan_sip to PJSIP migrations, SIP
trunk hookup to Swiss carriers, dial plans, call queues,
time-based routing, call recording and statistics.
AREA 4 — BACKUP & CONTINUITY
Proxmox Backup Server, ZFS replication, encrypted offsite copy,
append-only design resistant to ransomware. Equally at home in
Veeam, Commvault, TSM, Nakivo and NetBackup environments.
And above all: tested restores, not just scheduled ones.
AREA 5 — MONITORING & OPERATIONS
Metrics, useful alerts (the kind that don't cry wolf),
dashboards, written procedures and runbooks — SCOM, Prometheus,
Zabbix or LibreNMS depending on the stack. The goal is that
an outage can be handled without me if I am unreachable.
HOW IT WORKS
1. We look at what's there together. No jargon, no surprise quotes. 2. I propose a target and a path to get there, in stages. 3. We deploy outside production hours when it matters. 4. You receive the documentation. It's yours. 5. Follow-up on retainer or per intervention, your choice. [ MESSAGE TO SYSOP ] to discuss it, or [ FILE_ID.DIZ ] for concrete examples.