New: temperature, fans, power supplies and SSD health per server. View hardware health

Try it free

Terms and conditions

Deutsche Fassung

This English version is a convenience translation. The German version is legally binding.

General terms and conditions (GTC) of Nelpx GmbH for the “PeakNode” product
Last updated: November 2026

§ 1 Scope, customers #

(1) These general terms and conditions (hereinafter “GTC”) apply to all contracts for the use of the “PeakNode” monitoring platform as software-as-a-service (hereinafter “Software” or “PeakNode”) and for the provision of the on-premise version (§ 13) between Nelpx GmbH, Heininger Str. 9, 71554 Weissach im Tal (hereinafter “Provider”) and its customers.

(2) PeakNode is offered exclusively to entrepreneurs within the meaning of § 14 of the German Civil Code (Bürgerliches Gesetzbuch, BGB), legal entities under public law and special funds under public law (hereinafter “Customer”). Consumers within the meaning of § 13 BGB are excluded from use.

(3) Deviating, conflicting or supplementary general terms and conditions of the Customer only become part of the contract if and to the extent that the Provider has expressly agreed to their validity in writing.

(4) The Data processing agreement (§ 10) forms part of every contract for the use of the Software.

§ 2 Subject matter of the contract and services #

(1) PeakNode is a monitoring platform for monitoring servers, GPU servers, workstations, websites, services, scheduled tasks (heartbeats), DNS records, domains and SSL certificates. It comprises in particular the portal, the agent for Linux, Windows and macOS, notifications via the channels set up by the Customer, status pages, reports, teams and the NodeCare and NodeGuard functions.

(2) The Provider makes the Software available to the Customer for use via the internet as software-as-a-service (SaaS) for the term of the contract.

(3) The scope of functions, the number of server monitors, uptime monitors, heartbeats, status pages and teams, and the duration of data retention (retention period) are set out in the service description of the booked plan on the Provider’s website. One server monitor corresponds to one server, regardless of the number of its GPUs. NodeCare is included in every plan, NodeGuard in the Premium and Enterprise plans and in the on-premise version; the Customer switches NodeGuard on per server.

(4) The Provider reserves the right to continuously develop the Software and to change, extend or restrict functions, provided that this serves technical progress, is required by mandatory legal requirements, or the change is reasonable for the Customer and does not jeopardize the purpose of the contract.

(5) The agent is a script that is delivered in plain text (Linux and macOS: shell script, Windows: PowerShell script). The Customer installs it itself with the command shown in the portal. This command creates a directory for the agent and sets up its regular execution: on Linux and macOS as an entry in the crontab of the executing user (on Linux without a running cron service as a background process until the next restart), on Windows as a scheduled task under the system account. On each run, the agent reads measured values and status information of the system on which it runs and sends them to the portal via an outgoing connection that it establishes itself, encrypted via HTTPS in the SaaS version. It does not open a port, does not accept commands and does not run any programs transmitted by the portal. The portal’s answer only determines which of the information described in these GTC and on the website the agent collects on its next run (for example NodeGuard data, hardware readings, or a renewed check whether a reported file is still present). The agent collects NodeGuard data only on servers for which the Customer has switched NodeGuard on in the server monitor settings; the portal does not store NodeGuard data it receives for any other server. The agent does not change the configuration of the monitored systems. It only writes state and cache files to its own directory and temporary files to the temporary directory of the system. It does not update itself; the Customer installs a new version. The Provider does not perform any actions on the Customer’s systems via the Software.

(6) NodeCare (early warning for hardware) and NodeGuard (security functions) evaluate the data sent by the agent according to defined rules and provide the Customer with notices. They do not intervene in the Customer’s systems, do not block anything and do not remediate findings. The notices are decision aids; the Customer decides whether and which measures are taken.

(7) PeakNode is a tool for monitoring and notices. The Provider owes the provision of the Software in accordance with this § 2, not any further result. In particular, it does not owe that outages, attacks, hardware defects or data loss at the Customer are prevented. The Provider does not owe any particular detection performance. In particular, the Provider does not warrant that NodeGuard detects every attack, every vulnerability or every change, or that NodeCare indicates every hardware failure in advance. Notices may also be inaccurate. The comparison with known vulnerabilities is based on public third-party databases (OSV.dev, list of the US agency CISA), for whose completeness and accuracy the Provider assumes no responsibility. NodeCare and NodeGuard do not replace the Customer’s own security measures, data backups and maintenance, nor an assessment by experts.

(8) The measured values originate from the interfaces of the Customer’s operating system, drivers and hardware. The Provider assumes no responsibility for their accuracy. If a value is missing or invalid, the Software displays it as unknown.

(9) Uptime checks and webhooks of the SaaS version only reach publicly accessible targets.

(10) Service descriptions on the website, in the portal and in the Provider’s documents describe the Software; they are not guarantees. The Provider only assumes a guarantee if it expressly designates it in writing as a guarantee.

(11) PeakNode is intended for monitoring IT systems. It is not intended for use in environments in which a failure or malfunction of the monitoring can endanger life, body or health or cause exceptionally high financial losses. If the Customer uses PeakNode in such an environment, it may only do so together with its own monitoring that is independent of PeakNode.

§ 3 Conclusion of contract and free plan (Proof of Concept) #

(1) The presentation of the plans on the website does not constitute a legally binding offer, but an invitation to place an order.

(2) The contract is concluded when the Customer, after completing the ordering process, receives an order confirmation by email or the Provider activates the Customer’s access to the Software. For individual Enterprise contracts and for the on-premise version, the contract is concluded by signing an individual quotation.

(3) Proof of Concept: The Provider provides a free “Proof of Concept” plan. It serves to get to know and test the platform, has no time limit and is severely restricted in scope. It includes 1 server monitor, 1 uptime monitor, 1 heartbeat, 1 DNS monitor, 1 monitored domain, 1 status page and 1 project, with data retained for 14 days; API access and NodeGuard are not included. The current plan overview on the website is authoritative. There is no entitlement to the permanent provision of the free plan; the Provider may change or discontinue it with reasonable notice. A paid contract is only concluded by actively booking a paid plan. There is no automatic conversion into a paid subscription.

§ 4 Availability, maintenance and service level (SLA) #

(1) The Provider operates the SaaS services with the care of a prudent businessperson. In the paid plans, it promises an availability of the SaaS services of 99.5% per calendar month. It does not promise any availability for the free plan (§ 3 (3)). During an interruption, no checks take place and no notifications are sent.

(2) Availability is the share of the minutes of a calendar month that are not downtime. Downtime means the minutes in which no user of the Customer can sign in to the portal. It is measured at the transfer point; the transfer point is the router exit of the data center in which the Provider operates the SaaS services.

(3) The following do not count as downtime

  • maintenance windows announced by the Provider under paragraph 4,
  • interruptions that add up to less than one minute within an hour,
  • interruptions caused by installing security updates,
  • disruptions in networks outside the Provider’s control, in particular between the transfer point and the Customer,
  • attacks by third parties on the services, networks or data centers (for example DoS or DDoS attacks) and force majeure (§ 9 (9)),
  • disruptions of third-party services (paragraph 5),
  • suspensions of access due to a breach of duty by the Customer (§ 5 (7), § 7 (4)),
  • causes within the Customer’s area of responsibility, for example its systems, its network access, its access data or its settings.

(4) The Provider may temporarily restrict or interrupt the SaaS services for maintenance, updates and security measures. It usually announces scheduled maintenance work 48 hours in advance and schedules it, where possible, at times of low usage. It may carry out urgent measures for security or to prevent disruptions without notice.

(5) The delivery of notifications via third-party services (receipt of email by the Customer, Microsoft Teams, Slack, Telegram, Discord, webhook recipients) is beyond the Provider’s control; the Provider does not promise their delivery. The Customer sets up several channels if required.

(6) If availability falls below the value under paragraph 1 in two consecutive calendar months, the Customer may terminate the contract for the affected paid plan for cause. The termination must be received in text form within 30 days after the end of the second of these calendar months. Credits for falling below the availability are not provided; further claims of the Customer for falling below it are governed by § 9.

(7) For Enterprise customers, a different availability and support response times may be agreed in text form in an individual service level agreement. To the extent that it governs a matter, it takes precedence over this § 4.

§ 5 Obligations and duties of the Customer #

(1) The Customer is obliged to provide the data required for the provision of services (in particular billing and contact data) completely and truthfully.

(2) The Customer shall keep its access credentials, API keys and the access tokens of the agents confidential and protect them against access by unauthorized third parties. The Provider recommends two-factor authentication.

(3) The Customer installs and operates the agent on its own responsibility and keeps it up to date. Before installation, it checks whether the agent suits its environment, in particular whether it may be operated on the respective system with the required privileges (on Linux usually as root, on Windows under the system account) and whether the entries set up under § 2 (5) and the measurements are compatible with its operations. The agent is delivered in plain text and can be read before installation.

(4) The Customer may only use PeakNode for servers, systems, websites and services that it is authorized to monitor. This applies in particular to systems that it operates for third parties or that belong to third parties.

(5) The Customer is responsible for the lawfulness of the monitoring under data protection law. Where required, it informs the persons concerned, in particular its employees, that PeakNode processes user names of processes and, with NodeGuard enabled, SSH sign-ins with user name and source address as well as addresses from the access logs of its web servers. If there is a works council or staff council, the Customer observes its participation rights before deployment.

(6) The use of PeakNode for illegal, abusive or network-disrupting purposes is prohibited. The Customer may not overload the API provided with excessive requests not in accordance with the contract (exceeding limits, DDoS-like behavior). Uptime checks may only be directed at targets whose operator has consented to the checks or which the Customer operates itself.

(7) The Provider is entitled to block the Customer’s access to the Software temporarily, in whole or in part, if the Customer materially breaches its obligations under the contract or there is a justified suspicion of this, or if the Customer’s use endangers the security or stability of the services or of the Provider’s infrastructure. The Provider announces the suspension in advance where this is reasonable in the circumstances; otherwise it informs the Customer without delay afterwards. It lifts the suspension as soon as its reason no longer applies. The Customer’s obligation to pay the fees continues during the suspension. § 7 (4) applies to payment default.

(8) The Customer takes its own precautions, independent of PeakNode, to back up its data and to protect its systems. PeakNode is not intended as the only monitoring for systems whose failure can cause considerable damage; for such systems, the Customer additionally sets up its own, independent monitoring or alerting (see also § 2 (11)).

(9) The Customer is responsible for its settings, in particular thresholds, check intervals, recipients and notification channels. It checks at reasonable intervals whether notifications reach it.

§ 6 Rights of use and white-labeling #

(1) For the term of the contract, the Provider grants the Customer a simple, non-exclusive, non-transferable and non-sublicensable right to use the Software as intended.

(2) Reverse engineering, decompiling or disassembling the Software is prohibited unless expressly permitted by law (§ 69e of the German Copyright Act (Urheberrechtsgesetz, UrhG)). Reading and reviewing the agent, which is delivered in plain text, is permitted.

(3) Managed service and white-labeling: If the Customer (for example as an IT service provider) uses a plan that expressly includes white-labeling functions and multi-tenancy, it is entitled to resell the monitoring data, dashboards and status pages in its own name to its own end customers. The contractual relationship exists exclusively between the Customer and its end customers. Direct liability of Nelpx GmbH towards the Customer’s end customers is excluded. The Customer ensures that it is authorized vis-à-vis its end customers to process their data and, where necessary, concludes a data processing agreement with them.

§ 7 Remuneration and terms of payment #

(1) The remuneration payable by the Customer depends on the plan and billing period (monthly or annually) selected at the conclusion of the contract. All prices stated are net prices plus the applicable statutory VAT.

(2) Billing takes place in advance for the respective billing period.

(3) The Provider makes invoices available to the Customer in electronic form (PDF).

(4) If the Customer is in default of payment, the Provider is entitled, after a prior reminder, to temporarily block access to the Software until the outstanding claims have been paid in full. The Customer’s payment obligation remains in force during the block.

§ 8 Term, termination and data at the end of the contract #

(1) The term of the contract depends on the billing period selected by the Customer (for example 1 month or 12 months).

(2) The contract is automatically renewed for the respective original term unless it is properly terminated by one of the parties.

(3) Contracts with a monthly term may be terminated with 14 days’ notice to the end of the month. Contracts with an annual term may be terminated with one month’s notice to the end of the respective contract year.

(4) Termination may be effected in the portal in the account settings for the plan or in text form (for example by email to info@peaknode.de).

(5) The right to extraordinary termination for good cause remains unaffected. Good cause for the Provider exists in particular if the Customer is in default of payment for more than two months or materially violates these GTC.

(6) When a paid plan ends, the account is switched to the free plan. Measurement data exceeding its retention period is kept for a further 30 days and then deleted. Until then, the Customer can retrieve its data via the API and the export functions of the portal. If the uptime monitors, server monitors, heartbeats, DNS monitors, domains or status pages created in an account exceed the limits of its plan (for example after the end of a paid plan, after a change to a smaller plan or after a change of the free plan), the Provider informs the Customer by email. If the limits are still exceeded 14 days after this notice, the Software pauses, per type, the most recently created entries until the limit is met. Nothing is deleted. After a change to a plan with sufficient limits, the paused entries continue to run.

(7) The Customer can delete its account at any time in the account settings. In this case, the data of the account is deleted; a running subscription is ended.

§ 9 Warranty and liability #

(1) The Provider makes the Software available in its respective current state of development. Software errors that only insignificantly impair the contractual use do not give rise to claims for defects. The Customer notifies the Provider of defects without delay in text form with a comprehensible description.

(2) The Provider’s strict liability (liability regardless of fault) for damages for defects that already existed when the contract was concluded (Section 536a (1), first alternative, German Civil Code) is excluded. Liability for fault is governed by the following paragraphs.

(3) The Provider is liable without limitation

  • for intent and gross negligence,
  • for injury to life, body or health,
  • under the German Product Liability Act (Produkthaftungsgesetz),
  • to the extent of a guarantee expressly assumed by it (§ 2 (10)),
  • for fraudulently concealed defects,
  • insofar as liability is otherwise mandatory by law.

(4) Otherwise, the Provider is only liable for slight negligence if it breaches a material contractual obligation. Material contractual obligations (cardinal obligations) are obligations whose fulfillment makes the proper performance of the contract possible in the first place and on whose fulfillment the Customer may regularly rely, for example the provision of the Software in accordance with § 2. In this case, liability is limited to the damage typical for the contract and foreseeable when the contract was concluded. Any further liability for slight negligence is excluded.

(5) Liability under paragraph 4 is also limited in amount, namely to 25% per damaging event and, for all damaging events of a contract year together, to 50% of the net fees that the Customer paid to the Provider for that contract year. A contract year is the period of twelve months from the start of the contract and each following period of twelve months; for a term of more than twelve months, the current twelve-month period in which the damaging event occurs applies.

(6) In the event of slight negligence, the Provider is not liable for indirect and consequential damage, lost profit, missed savings and damage from business interruption, unless such damage was typical for the contract and foreseeable when the contract was concluded.

(7) For the loss of or damage to data and for damage from business interruption, the Provider is only liable to the extent that the damage could not have been avoided even with reasonable precautions by the Customer. Reasonable precautions are in particular regular backups of its own data and settings, insofar as the Software allows their export (§ 5 (8)), contingency planning for the case that the Software is temporarily unavailable, and for the on-premise version at least a daily backup and testing updates before installing them. For the loss of or damage to data, the Provider is in addition only liable in the amount of the effort that would have been required to restore it if the Customer had taken these precautions. This paragraph does not apply in the event of intent and gross negligence or in the other cases of paragraph 3.

(8) In the free plan (§ 3 (3)), the Provider renders its services free of charge. There, in accordance with Sections 521 and 599 of the German Civil Code, it is only liable for intent and gross negligence and, in accordance with Sections 523, 524 and 600 of the German Civil Code, for defects only if it has fraudulently concealed them. Paragraph 3 remains unaffected.

(9) The Provider is released from its performance obligations for as long as and to the extent that it is prevented from performing by force majeure. Force majeure means external events that the Provider cannot avert even with reasonable care, for example natural events, fire, large-scale failures of power or telecommunications networks, attacks by third parties on networks or data centers (for example DDoS attacks), industrial action and orders by authorities. This also applies if such events affect the operator of the data center or other suppliers of the Provider. § 4 (5) applies to notifications via third-party services.

(10) Claims of the Customer for damages and for reimbursement of futile expenses become time-barred twelve months after the statutory start of the limitation period. This does not apply in the cases of paragraph 3.

(11) Insofar as the Provider’s liability is excluded or limited under this § 9, this also applies to the personal liability of its bodies, legal representatives, employees and vicarious agents. These provisions of this § 9 do not change the burden of proof to the Customer’s disadvantage.

(12) The Customer indemnifies the Provider against third-party claims based on the Customer’s unlawful use of PeakNode, in particular monitoring systems, websites or services without authorization (§ 5 (4)) or publishing unlawful content on status pages, insofar as the Customer is responsible for this. The indemnity includes the reasonable costs of legal defense. The Provider informs the Customer without delay of such claims.

§ 10 Data protection and data processing on behalf #

(1) The Provider processes the Customer’s personal data in accordance with the General Data Protection Regulation (GDPR; German: DSGVO). Further details can be found in the Privacy policy.

(2) Insofar as the Provider processes personal data on behalf of the Customer in connection with the use of PeakNode (in particular measurement data with user names, NodeGuard data with user names and IP addresses, data of status pages and their subscribers, members of teams), the Data processing agreement pursuant to Art. 28 GDPR published on the website applies. It takes effect upon conclusion of the contract for PeakNode.

(3) For the on-premise version, paragraph 2 only applies insofar as the Provider obtains access to personal data in the course of support services.

§ 11 Amendments to the GTC #

(1) The Provider reserves the right to amend these GTC with effect for the future if this is necessary due to legal, technical or economic developments and the balance between performance and consideration is not shifted to the detriment of the Customer.

(2) The Provider will inform the Customer by email no later than six weeks before the planned entry into force of the new GTC.

(3) The Customer may object to the amendments within four weeks of receipt of the notification. If the Customer does not object, the amended GTC are deemed accepted. The Provider will separately point out the right to object and the legal consequences of silence in the notification of amendment. If the Customer objects, either party may terminate the contract as of the date on which the amendment enters into force.

§ 12 Final provisions #

(1) This contract is governed exclusively by the law of the Federal Republic of Germany, excluding the UN Convention on Contracts for the International Sale of Goods (CISG).

(2) The exclusive place of jurisdiction for all disputes arising from or in connection with this contract is Stuttgart, provided that the Customer is a merchant, a legal entity under public law or a special fund under public law.

(3) Should individual provisions of these GTC be or become invalid or unenforceable, this does not affect the validity of the remaining provisions. The invalid provision shall be replaced by the valid provision that comes closest to the economic purpose of the invalid provision.

§ 13 Special provisions for PeakNode On-Premise #

(1) With the on-premise version, the Customer receives an installation package (portal, database schema, agent scripts) for operation on its own servers in return for a one-time fee according to an individual quotation. §§ 1, 2 (1), (5) to (8), (10) and (11), §§ 5, 6 (2), 9, 10 and 12 apply accordingly, unless otherwise agreed in the quotation.

(2) The Customer operates the on-premise version on its own responsibility. Installation, operation, backup, security and updating of the servers on which it runs are the responsibility of the Customer. The availability under § 4 does not apply. The net fees for the contract year referred to in § 9 (5) are replaced by the one-time net fee paid by the Customer for the license plus the net fees it paid for updates and support for the contract year in which the damaging event occurs; here, a contract year is the period of twelve months from the provision of the license and each following period of twelve months.

(3) The on-premise version does not send any usage data to the Provider and does not check the license online. All data remains with the Customer.

(4) The Provider makes updates available as a package that the Customer installs itself. The scope of the license (number of installations, use for the Customer’s own end customers) and the duration of updates and support are set out in the individual quotation. Unless otherwise agreed, the license applies to one productive installation of the Customer, and updates and support are included for the term stated in the quotation.