Is self-hosted PRTG replacement cheaper than the PRTG subscription?
It can be, but only once you count the components the license line leaves out. Take your PRTG figures from your own renewal quote, including your current sensor tier and any step up to Enterprise Monitor, since no PRTG prices are stated here. On the open-source side the software line can drop to zero: Zabbix states it has no license fee, no device limits and no feature gates, and Checkmk Community is free and open source for small infrastructures, scalable up to about 100 hosts. Above that, Checkmk's commercial editions start at 190 euros per month for Pro and 275 euros per month for its largest edition, both billed annually. Compare your renewal with the host count you actually need to monitor before treating the zero line as the saving.
The costs that recur and the costs that arrive once decide the answer. One-time costs include discovering sensors, rebuilding templates, maps and notifications, and running both systems until alerts match. Recurring costs include the servers or virtual machines for the Zabbix server and proxies, the database (Zabbix 7.4 supports MySQL, MariaDB and PostgreSQL with TimescaleDB), backups, and upgrades. Zabbix standard releases arrive every 6 months and LTS releases every 1.5 years, so plan a maintenance window for each. If you buy Zabbix technical support, its Silver to Global tiers differ in response time and hours of cover, and the price is quoted separately. Staff time is the line teams most often undercount, so estimate the hours each year for tuning, alert review and upgrades.
Before you sign anything, ask for a written quote that lists each component on its own: migration effort in fixed scope, hardware or hosting, database, support subscription or none, and yearly upgrade and staff hours. Compare that total with the PRTG renewal over the same term, and include the cost of running both systems in parallel during cutover. If your host count sits near the Community limit, price a Checkmk Pro edition alongside Zabbix before you choose. DeployOpen scopes these migrations in writing before work starts, so you can compare like with like.
Which cost components move when you replace PRTG
This table compares each cost component of PRTG with its self-hosted Zabbix and Checkmk counterparts and marks whether it is one-time or recurring. Read it as a checklist for a quote: the license line often drops to zero, but skills, migration and upkeep stay, so ask for each component separately.
| Cost component | PRTG and self-hosted Zabbix or Checkmk | One-time or recurring |
|---|---|---|
| Software license or subscription | PRTG is billed by sensor tier under a subscription that must be renewed. Zabbix has no license fee and no device or feature limits. Checkmk Community is free, while Pro and Ultimate are paid editions billed per year. | PRTG and Checkmk commercial editions: recurring. Zabbix and Checkmk Community: none |
| Support | PRTG support is bundled with the subscription. Zabbix paid support comes in Silver, Gold, Platinum, Enterprise and Global tiers, from 8x5 to 24x7. Checkmk Pro includes 8x5 support. | Recurring if you buy support. Confirm tier and response times in writing |
| Servers and virtualization | PRTG runs on a Windows server sized to sensor count. Zabbix and Checkmk need Linux hosts, and high availability adds a second server node or proxy. Costs depend on your hypervisor and hardware. | Mostly one-time setup, then recurring hosting and power |
| Database | PRTG keeps its data in an internal store. Zabbix requires MySQL, MariaDB, PostgreSQL or TimescaleDB, so you must size, back up and patch it. Checkmk uses its own site storage. | Setup one-time, then recurring storage growth and maintenance |
| Migration labor | Exporting devices, sensors and history from the PRTG HTTP API, then mapping them to Zabbix templates or Checkmk hosts, takes engineer time. Running both tools in parallel adds overlap cost until alerts match. | One-time, driven by sensor count and map complexity |
| Implementation and template work | Custom PRTG sensors must be rebuilt as Zabbix items or Checkmk checks. Zabbix templates and Checkmk discovery reduce effort for standard devices but still need tuning and thresholds. | One-time, with ongoing changes as the estate grows |
| Upgrades and lifecycle | PRTG upgrades are covered by the subscription. Zabbix standard releases are supported for 12 months, while LTS releases are supported for 5 years. Plan upgrade windows for each release you run. | Recurring staff time for each upgrade cycle |
| Notifications and integrations | Rebuilding PRTG notification templates, ticketing hooks and maps in Zabbix or Checkmk is one-time work. Checkmk push-mode agents and automatic registration are Ultimate features, so check whether you need them. | One-time build, recurring maintenance when integrations change |
| Internal skills | Monitoring administrators must learn Zabbix or Checkmk configuration, database operations and security hardening. Training and the time to run it are a continuing cost even without a license fee. | Largely recurring, as staff turn over and the platform changes |
What moves the PRTG versus self-hosted comparison
Cost differs between PRTG and self-hosted Zabbix or Checkmk mainly because of how many devices and sensors you run, how much availability you need, and who operates the platform. The cards below set out each driver, the direction it pushes the total, and what to confirm before you ask for a quote.
Sensor and device count
PRTG is licensed by sensor tier, so the number of sensors you monitor sets the subscription size and the point where you move to a larger tier. Zabbix charges no license fee and has no device or feature limits, so growth shifts cost to servers, storage and staff time. Checkmk Community is positioned for small infrastructures and scales up to about 100 hosts, so larger estates need a commercial edition. Count hosts and services from your current PRTG export before comparing.
Checkmk edition features
Distributed monitoring, push-mode agents and automatic host registration are not all in the free Checkmk Community edition. Distributed monitoring and 8x5 support sit in Pro, while push-mode agents and automatic registration are Ultimate features. If your estate needs remote sites or mass agent rollouts, price the Pro or Ultimate subscription as a recurring line item, and ask the vendor which add-ons, such as Synthetic Monitoring, are included.
Availability and high availability design
Availability targets decide how many components you run. A Zabbix server can run as a high availability cluster with several nodes sharing one database, and proxy groups can reassign hosts when a proxy goes offline. Each extra node, proxy and database replica adds hardware and operating effort. Define the acceptable outage window and failover delay first, then size the cluster to match, so you do not pay for redundancy the business does not need.
Database choice and retention
Zabbix runs on MySQL, MariaDB, PostgreSQL or PostgreSQL with the TimescaleDB extension, and the database holds all history and trend data. Storage growth depends on item count, polling interval and retention settings, so long retention on frequent polls raises disk, backup and tuning costs. Choose a database your team already operates, confirm which versions your release supports, and check whether a DBA or managed database service is in your budget.
Support tier and response time
Zabbix software is free, but paid technical support is sold in tiers that differ by hours of coverage and response time, from 8x5 with a 1 day response to 24x7 with a 1 hour response. Checkmk Pro includes 8x5 support, and higher commercial tiers add more. Support is a recurring cost that scales with how quickly you need help outside business hours. Ask each vendor for response commitments in writing and compare them with what your on-call rota can cover.
In-house monitoring skills
The largest cost of a self-hosted platform is usually the time of the people who build templates, tune polling, maintain upgrades and answer alerts. PRTG's sensor model is simpler to start with, while Zabbix templates and Checkmk rule sets reward experienced operators. Estimate the hours per month your team can give to monitoring and note which skills are missing. A partner can plan, implement and document the platform, and ongoing support can be bought as a retainer, scoped in writing.
How to build the PRTG comparison with your own numbers
This sequence turns a vague sense that PRTG costs too much into a three-year comparison built from your own sensor counts, renewal terms, infrastructure prices and staffing, so the decision rests on figures your finance and operations teams can defend.
Export your current sensor and device counts
The monitoring administrator exports the device and sensor inventory from the PRTG web interface or through the PRTG HTTP API, grouped by probe and sensor type. Record the total sensor count, the number of devices, and which sensor types drive the count, because PRTG licensing is tied to sensors. Note any sensors that are paused or unused, since they still count toward the tier you buy unless they are removed. The step is complete when one sheet shows sensors and devices per probe and per sensor type, reconciled against the number on your current license.
Collect current renewal terms and tier details
The procurement lead or license owner pulls the active PRTG agreement, including the sensor tier, the license term, the renewal date, the notice period, and any Enterprise Monitor or hosted terms. Ask the reseller or Paessler for the price of the next renewal and for the price of the tier that would cover your sensor growth, in writing. The step is complete when you hold a dated sheet of what you pay now, what the renewal costs, and when the notice window closes, so you know the deadline the rest of the sequence must meet.
List target editions and support tiers
The monitoring lead lists the candidate platforms and the paid options each one offers. For Zabbix, the open-source software carries no license fee, and the paid part is a technical support subscription in the Silver, Gold, Platinum, Enterprise or Global tier, with response times that differ by tier. For Checkmk, list Community, Pro, Ultimate and Cloud, and note which features each includes, such as distributed monitoring, push-mode agents and synthetic monitoring. Confirm current Zabbix support prices and Checkmk edition prices with each vendor against the current price list, since published figures can change. The step is complete when each candidate has one line showing its license cost, support cost and the features your estate needs.
Price servers, database and backup storage
The infrastructure owner prices the self-hosted components from your own infrastructure catalog: application servers for the Zabbix or Checkmk core, a database host, proxies or remote collectors for distributed sites, virtualization capacity, storage for history and trends, and backup space. Size these from the sensor and item counts in step one and the database versions your chosen platform supports. Include the operating system and database licensing if your standards require it. The step is complete when each component has a unit cost from your internal rates or hardware quotes, and the total matches the sizing sheet.
Estimate migration and template rebuild effort
The platform team estimates the work to move devices, recreate thresholds, rebuild notifications and maps, and run both systems in parallel until alerts match. Count the custom sensors and scripts in your PRTG setup, since these usually need manual rework, and list the notification channels that must be recreated. Estimate effort in person-days with your own team, or request a fixed-scope quote from an implementation partner based on a written scope. The step is complete when you have a one-time effort figure for each workstream, tagged with whether it is internal labor or an external fee, and a list of the assumptions behind it.
Assign recurring staff time for upkeep
The operations manager estimates the ongoing hours for patching the platform, updating templates, maintaining discovery rules, managing proxies, reviewing alert quality and handling support tickets. Compare this with the time your team spends on PRTG today, and note the roles that would cover it. Include the cost of any support subscription as a recurring line. The step is complete when recurring staff time is written as hours per month with a named role for each task, and the total is converted to cost using your internal loaded rate.
Model a three-year view with separated lines
The finance lead builds a three-year table with two sections: one-time costs for migration effort, server build, database setup and initial configuration, and recurring costs for the PRTG renewals or the replacement's support subscription, infrastructure running costs, backup storage and staff time. Run the PRTG line at your current tier and at the tier you would need after growth, and run each candidate platform the same way. Mark every figure with its source, such as a vendor quote, an internal rate or an estimate, so reviewers can challenge the inputs. The step is complete when the model shows one-time and recurring totals per option across the three years, and the assumptions sheet is signed off by the people who own each input.
How Zabbix and Checkmk release cycles change the upkeep budget
The upkeep budget for a self-hosted Zabbix or Checkmk estate is set by release cadence, not by a one-time install. Zabbix 7.0 LTS was released on 4 June 2024 with full support until 30 June 2027 and limited support until 30 June 2029, and Zabbix 8.0 LTS is planned for Q4 2026 with full support to Q4 2029. Zabbix standard releases arrive every 6 months and are supported for 12 months. Each version change means someone tests templates, custom items, proxies and the database upgrade before production moves, so budget that effort as a recurring line item. Ask whether the team plans to follow LTS lines or standard releases, and whether a 2026 move to 8.0 LTS is inside the budget year.
Checkmk works on a different rhythm but creates the same kind of work. Checkmk 2.5.0 was tagged on April 24, 2026, and patch releases such as 2.5.0p15, tagged on September 30, 2026, follow it. Patch releases are ongoing maintenance: each one needs a staging site, a review of plug-in and agent versions on Linux and Windows hosts, and a check that rule sets still apply after upgrade. Confirm with Checkmk which edition you run, since Community is maintained as open source and the commercial editions add support tiers. Record the patch cadence you intend to keep, because skipped patches accumulate into a larger upgrade later.
Match your support tier to how long a monitoring outage can be tolerated. Zabbix support runs from 8x5 with a 1 day response (Silver) through 24x7 with a 1 hour response (Global), and its tiers are priced separately from the free software. Checkmk Pro and Ultimate include 8x5 support in their editions. Decide the longest acceptable gap in alerting for your critical services, then compare that figure with the response times in each vendor's current support terms, which you should confirm in writing. An 8x5 contract covers a weekend outage of monitoring only if you accept a delayed response, so put that trade-off in the quote request.
Frequently asked questions about PRTG replacement cost and effort
What drives the cost of moving off PRTG to a self-hosted platform?
The cost is driven by the work and the infrastructure, not by a license fee, because Zabbix open source states it has no license fee, no device limits and no feature gates. The main components are the servers and database you run, the staff time to build templates or sensors and rebuild dashboards, maps and notification rules, the migration and parallel running period, and any paid support subscription you choose. Your PRTG subscription cost is the figure to compare against, and you should price it by sensor tier and by the jump to Enterprise Monitor if you need that tier. Ask any quote to separate one-time build work from recurring operations so the two can be compared fairly.
Can our in-house team run the migration without an outside partner?
Often yes, if the team already runs Linux servers, databases and SNMP or agent-based monitoring, and has someone who can own the monitoring design. The hard parts are rarely the installation. They are mapping every PRTG sensor to a Zabbix template or Checkmk check, rebuilding alert logic so it does not flood or go silent, and proving that alerts match before PRTG is switched off. Ask yourself how many people can take on that work in parallel with their normal duties, and whether anyone has built high availability or distributed monitoring before. A short assessment of your sensor inventory will show whether the work is a weekend of tidy-up or a multi-month project.
How long does a PRTG migration take and what does the timeline depend on?
No duration figure is supplied for this migration, so treat any number you see as something to verify against your own inventory. The timeline depends mainly on the number of devices and sensors, how many sensor types are custom or scripted, how many maps and notification templates must be rebuilt, the number of sites and proxies, and how long the parallel run lasts before alerts are trusted. Support windows also matter, since a project that needs changes in production must fit change control. Ask the implementer to break the work into discovery, build, parallel run and cutover, and to tie each phase to a count of devices you have confirmed.
Is Zabbix or Checkmk Community free to run?
Both can be downloaded and run without a license fee, but free does not mean no cost. Zabbix states that its open source software has no license fee, no device limits and no feature gates, and it is now released under AGPL-3.0 from version 7.0 onward. Checkmk Community is described as free, 100 percent open-source software, and its editions page describes it as suited to small infrastructures and easily scalable up to about 100 hosts. You still pay for servers, storage, backups, staff time and any optional support. Confirm the AGPL-3.0 implications with your legal team if you plan to modify and distribute the code.
When is Checkmk Pro or Ultimate, or a Zabbix support tier, worth paying for?
Pay for a commercial tier when you need a specific feature or a response time that your team cannot cover internally. For Checkmk, the editions page lists Pro from 190 euros per month and Ultimate from 275 euros per month, both billed annually, and notes that Pro adds distributed monitoring and 8x5 support while Ultimate adds push-mode agents and automatic host registration. For Zabbix, support tiers run from 8x5 with 1 day response (Silver) to 24x7 with 1 hour response (Global), and the license itself stays free. Check whether you need 24x7 coverage, a vendor-backed path for critical alerts, or features you would otherwise have to build. Confirm current pricing directly with the vendor.
What does the work need from our staff day to day?
Plan for a named owner for monitoring configuration, someone who can maintain templates or checks, a Linux and database administrator for the platform, and a person who answers for alert quality. Zabbix requires a supported database such as MySQL, PostgreSQL or MariaDB, and version support windows vary by release, so the team needs time for upgrades. Checkmk needs its own site management and updates on the chosen distribution. For Zabbix high availability, you will also run several server nodes sharing one database, and proxy groups for distributed sites. Ask the implementer which tasks they will hand over, and which skills your staff must have before handover.
What should we ask for in a fixed-scope quote for this work?
Ask for a written scope that lists the device and sensor counts you confirmed, the sites and proxies in scope, which PRTG sensor types must be mapped, and which maps, reports and notifications must be rebuilt. Request deliverables for each phase, the acceptance criteria for a parallel run, the cutover plan and a handover package with documentation. Ask how one-time build work is priced separately from any recurring retainer for upgrades, support and testing, and what is excluded, such as custom scripts or third-party integrations. DeployOpen plans and implements self-hosted platforms in your own environment and agrees scope, deliverables and timelines in writing before work starts, and it does not publish a price list, so a quote follows from that written scope.
Who runs monitoring after the switch and what that costs in time
The main cost after a switch is the time of the people who run the platform, and it differs by tool. Zabbix needs internal skills across the Zabbix server, its database, the proxies that sit close to monitored sites, and the templates that define what gets checked. The database choice matters here: Zabbix 7.4 supports MySQL or Percona, MariaDB, PostgreSQL with TimescaleDB, and SQLite for proxies only, so the team needs someone who can size, back up and tune that database. Checkmk needs a different set of skills: site management, the rule sets that decide how hosts and services are configured, and the agent deployment that feeds data in. Before choosing, list which of these skills already exist in your team and who would own each one day to day.
Alerting is the part that stays with your team no matter which platform you pick. Someone must own alert thresholds, notification routing, escalation paths and the periodic review that removes noisy checks. PRTG sensors often grew by accretion, so the first migration task is usually deciding which alerts still matter. Ask your implementation partner to document each alert's owner and purpose, and confirm whether the on-call tool that receives alerts will be replaced in the same project. Zabbix also offers high availability and proxy groups that rebalance hosts when a proxy goes offline. Those features reduce some operational risk, but someone still has to test failover and keep the configuration consistent.
A fixed-scope implementation partner suits the build phase: architecture, templates or rules, migration, documentation and handover, all agreed in writing before work starts. A retainer suits the period after handover, when upgrades, template maintenance, backup checks and new integrations arrive in small amounts. Zabbix support subscriptions from the vendor are a separate decision that covers vendor response times, not day-to-day operations, so check what each tier includes before buying. When you request a quote from DeployOpen or any other provider, ask which tasks are one-time, which recur, and which skills the handover assumes your staff already have.
How DeployOpen scopes a fixed-price PRTG replacement
DeployOpen plans and implements self-hosted monitoring inside your own infrastructure, starting from a written scope that sets out what is replaced, what is rebuilt and what is handed over. Engagements are fixed-scope, so the cost comparison between PRTG subscriptions and Zabbix or Checkmk is agreed on paper before any migration work starts.
How we scope
- Inventory every PRTG device, sensor type and alert rule to define the migration boundary in writing.
- List which sensors map to Zabbix templates or Checkmk services and which need custom work.
- Agree the number of hosts, proxies or sites and the database platform before quoting.
- Name who inside your team will own monitoring after handover, so run costs are visible from day one.
- Ask any quote to separate one-time setup from recurring support, subscriptions and hosting.
How we build
- Deploy Zabbix or Checkmk in your own cloud accounts, data centers or air-gapped networks.
- Configure high availability, proxy layout and database backups against the scope you approved.
- Rebuild thresholds, notification rules and maps, then test alert paths end to end.
- Run PRTG and the new platform in parallel until alert behavior matches the agreed baseline.
- Harden the servers, web interface access and credentials according to the agreed security baseline.
How we hand over
- Deliver runbooks covering installation, upgrades, backups, proxy changes and restore steps.
- Document the cost model, including which licenses or support tiers were chosen and why.
- Provide a sensor-to-template mapping so your team can audit what each check does.
- Walk your operators through alert triage, dashboards and day-to-day administration.
- Confirm the exit state in writing, including what PRTG data was exported and retained.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Plan version upgrades against the Zabbix or Checkmk release lifecycle your scope specifies.
- Review capacity and sensor growth periodically so licensing and hardware keep pace with demand.
- Ask the vendor directly about support tiers, response times and current release status before committing.
