Enterprise DNA

Instead of PRTG

Stop renting PRTG. Own your monitoring workflow.

We build your version around the services you need to watch, bring your PRTG inventory across and run the agreed checks and review process for you.

PRTG 5000 lists at US$1,300 a month paid annually, or US$15,600 a year. This is a published plan price, not a claim about your invoice.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Start with the invoice

PRTG charges by monitoring capacity

Separate the checks you depend on from the review work around them. Bring your bill and the devices you need covered.

sensors

A tier based on sensors

PRTG subscriptions differ by the number of sensors you can add.

devices

Several checks per device

A device can use several sensors. Device count alone does not tell you the required tier.

paid

A five-figure annual plan

PRTG 10000 lists at US$1,642 a month paid annually, equivalent to US$19,704 a year.

trending_up

Growth can mean an upgrade

Paessler offers a larger licence when the sensor allowance no longer covers your setup.

support_agent

Support is part of that bill

The subscription includes updates and email support. Include those services when comparing costs.

analytics

Decide what needs replacing

List the collectors, notifications and reports you rely on. We scope your version against that list before a switch.

The owned workflow

Checks, evidence and responsibility together

Morning operations

Find failures and missing checks

A last successful reading is useful only if collection is still running.

  • check Failed services shown with their responsible person
  • check Silent collectors listed as missing evidence
  • check Changed settings require a fresh result
  • check Branch reviews combine failures with collection gaps

Planned work

Keep maintenance visible

Record the approved window before work starts, then keep the checks made during it.

  • check Start and end times stay on the record
  • check The reason and responsible operator stay attached
  • check Planned failures remain available for review
  • check Missing evidence still needs attention during maintenance

Recovery commitments

Put an owner and date on the fix

Join the technical reading to the promise someone made about restoring service.

  • check A named person owns each follow-up
  • check Late commitments appear in the daily review
  • check Closing a follow-up needs fresh recovery evidence
  • check Investigation papers combine readings and your local commitments

Monday review

Read what the evidence actually says

Prepare the weekly paper from checks, ownership and policy dates.

  • check Captured sample counts sit beside the success ratio
  • check The ratio is labelled as sampled results, not continuous uptime
  • check Access and retention reviews appear with operational gaps
  • check Your brand carries through the review and maintenance papers

Make it yours

Design your own PRTG replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from PRTG. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your PRTG replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your PRTG data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Network Monitoring for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Network Monitoring for Claude Code

Connected to your own database

Which services need action or have stopped reporting?

Backup storage

Te ow
Auckland
Ner st
Noah
Ate in
stale
_maintenance
false

Warehouse link

Te ow
Hamilton
Ate in
down
_maintenance
false

Warehouse spare

Te ow
Hamilton
Ner st
Noah
Ate in
unknown
_maintenance
false

Ask it anything

Questions PRTG cannot answer

Every one of these is a real question the demo answers today. Yours will be different, and that is the point.

chat_bubble Which enabled monitors have stopped reporting, even if their last reading was good?
chat_bubble Which unplanned failures have no named owner?
chat_bubble Which branch has the most missing evidence?
chat_bubble Which recovery promises are overdue?
chat_bubble Which failures happened inside approved maintenance?
chat_bubble Which monitors supplied failed samples this week?
chat_bubble Which imported sensors still need a working collector?
chat_bubble Which readings have passed our retention period?
chat_bubble Who owns the largest queue of failed or stale monitors?
chat_bubble What proportion of captured samples succeeded, and how many were actually captured?

Switching

How to switch from PRTG

The move involves exporting your sensor inventory, checking what transfers, then verifying the checks and alert routes you still need before retiring PRTG.

  1. 1

    Export your sensor inventory

    Export the PRTG sensor inventory using the export options available in your account, usually CSV or Excel, and check with PRTG if you are unsure which option to use. Include the source identifiers, device labels, probe or group, sensor types and status text. This brings across the inventory, not historical measurements, credentials or notification rules.

  2. 2

    Test, then load the records

    Run the import as a test first and review the results before loading anything. Once you are satisfied, import the saved inventory into the new database. The import supports atomic loading and repeat-import checks. Imported monitors start disabled, so bringing in the records does not start checks against your network.

  3. 3

    Review gaps and requirements

    Check the imported inventory and review which monitors still need a working collector. Confirm each monitor’s owner and collection settings before enabling it. Identify specialist checks that need separate work, since the base does not cover every PRTG sensor type. Plan separately for any historical measurements, credentials and notification rules you choose to migrate.

  4. 4

    Run both systems side by side

    Keep PRTG running while you configure and verify the replacement checks you need. Run both side by side for a short period and compare the required checks and their evidence. Confirm that each required alert route works too. Notification delivery is separate setup work, so do not assume it is covered by importing the sensor inventory.

  5. 5

    Retire PRTG after verification

    Switch off PRTG only after every required check and alert route has been verified. Before you do, confirm that you have accounted for specialist checks, historical data and notification rules that your operation needs. If a required check or route is still unverified, keep PRTG in place until you have resolved the gap.

construction

Where the real effort goes

The import handles the sensor inventory, but the main work is usually mapping your own fields, owners, collection settings and rules, then deciding how much history to bring across. Historical measurements, credentials and notification rules need separate migration work. You also need to scope checks beyond the base HTTP, TCP and DNS coverage. Enterprise DNA handles this mapping and setup when you have them run it.

Not ready for a call?

Get your PRTG switch plan by email

We will send you the step-by-step plan for moving your business off PRTG, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free version or have us build yours

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Export the PRTG sensor inventory and run the import with a dry run first
  4. 4 Configure authorised checks and verify collection before switching
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your device groups, ownership rules and recovery commitments
  • check Your PRTG inventory mapped and reconciled
  • check The collectors, notifications and operator screens your team needs
  • check A different technology stack when your environment calls for it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access, backups and recovery checks
  • check Collection scheduled from the right network location
  • check Weekly reviews and overdue work prepared for the operator
  • check Maintained through Omni by Enterprise DNA alongside your other systems
Book a discovery call

Questions

Instead of PRTG, answered

Does this replace every PRTG sensor? expand_more

The free version checks website response status, service connections and hostname resolution. It also accepts numeric readings from a separate collector. We scope specialist device checks, bandwidth collection, distributed monitoring and notifications for your version before you retire existing coverage.

What does the PRTG import bring across? expand_more

Your sensor inventory, source identifiers, device labels, groups, original types and status text. Imported monitors start disabled until their owners and collection settings are checked. Historical measurements, credentials and notification rules need separate migration work. We bring those requirements into the switching plan.

Will it tell us when a collector stops working? expand_more

The review flags enabled monitors whose evidence is missing or older than their expected interval allows. A previously successful result becomes stale. Scheduled reviews and notification delivery must be configured and verified for your installation. We run that setup as part of the managed version.

Can we use the reports to prove our uptime promise? expand_more

The free report shows the proportion of captured checks that succeeded, with the number of checks and maintenance exclusions. It does not claim continuous availability. If your contracts need a time-based service report, we build the agreed measurement and coverage rules into your version.

What do we pay Enterprise DNA, and who owns the records? expand_more

One setup fee, then a retainer for the agreed operation and ongoing work. Your records stay in a database you own. The free software has no per-sensor licence charge, while hosting, collection infrastructure and support remain real operating costs.

Bring your monitoring bill and your required checks

30 minutes with Sam. We look at your PRTG invoice, which services your business depends on and what an owned version needs to do. You leave with a clear scope for the switch.

Book a discovery call Get the free version

Network Monitoring for Claude Code is free and open source, published by Enterprise DNA.

Done paying for PRTG?

Get your version built