GITNUXSOFTWARE ADVICE
Utilities PowerTop 10 Best Boiler Software of 2026
Explore the top 10 Boiler Software picks with a comparison and ranking, featuring UptimeRobot and Pingdom for reliable monitoring. Compare options.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
UptimeRobot
Keyword monitoring on HTTP responses to detect broken pages even when servers stay online
Built for teams needing low-friction uptime monitoring and alerting across many endpoints.
Pingdom
Uptime and performance monitoring with actionable alerts and detailed downtime reporting
Built for operations and web teams needing reliable uptime monitoring and alerting.
Statuspage
Incident timelines with automated component impact and public posting workflow
Built for teams needing branded outage communications with component-level incident tracking.
Related reading
Comparison Table
This comparison table reviews Boiler Software uptime and monitoring tools, including UptimeRobot, Pingdom, Statuspage, Better Stack (Uptime), and New Relic. It contrasts key capabilities such as alerting, uptime checks, incident communication, monitoring depth, integrations, and operational complexity so teams can match each platform to specific reliability and observability needs.
| # | Tool | Category | Overall | Features | Ease of Use | Value |
|---|---|---|---|---|---|---|
| 1 | UptimeRobot Monitors website and server endpoints with keyword, uptime, and alert checks and routes notifications via email, SMS, or integrations. | website monitoring | 8.8/10 | 9.0/10 | 8.6/10 | 8.7/10 |
| 2 | Pingdom Performs synthetic uptime checks for websites and web services and provides performance breakdowns with alerting and reporting. | uptime monitoring | 8.0/10 | 8.2/10 | 7.8/10 | 8.1/10 |
| 3 | Statuspage Publishes customer-facing service status pages with incident posting, real-time updates, and configurable notifications. | status communications | 8.3/10 | 8.4/10 | 8.7/10 | 7.7/10 |
| 4 | Better Stack (Uptime) Checks application endpoints for uptime and performance and sends alerts with log and incident context in one workflow. | uptime + alerts | 8.0/10 | 8.4/10 | 8.1/10 | 7.5/10 |
| 5 | New Relic Observes application and infrastructure health with monitoring dashboards, alert policies, and performance insights. | observability | 8.1/10 | 8.6/10 | 7.9/10 | 7.7/10 |
| 6 | Datadog Aggregates infrastructure metrics, application traces, and logs and triggers alerts based on monitored signals. | infrastructure monitoring | 8.1/10 | 8.6/10 | 7.6/10 | 7.9/10 |
| 7 | Grafana Builds dashboards and alert rules for metrics and logs from supported data sources like Prometheus and Loki. | dashboarding | 7.7/10 | 8.4/10 | 7.4/10 | 6.9/10 |
| 8 | Prometheus Collects time-series metrics from instrumented targets and exposes queryable data for alerting and visualization. | metrics collection | 8.0/10 | 8.8/10 | 7.6/10 | 7.4/10 |
| 9 | Alertmanager Routes and groups firing alerts from Prometheus into deduplicated notifications with configurable notification receivers. | alert routing | 7.3/10 | 7.6/10 | 7.0/10 | 7.1/10 |
| 10 | PagerDuty Manages incident response with alert ingestion, on-call scheduling, escalations, and post-incident workflows. | incident response | 8.0/10 | 8.2/10 | 7.6/10 | 8.0/10 |
Monitors website and server endpoints with keyword, uptime, and alert checks and routes notifications via email, SMS, or integrations.
Performs synthetic uptime checks for websites and web services and provides performance breakdowns with alerting and reporting.
Publishes customer-facing service status pages with incident posting, real-time updates, and configurable notifications.
Checks application endpoints for uptime and performance and sends alerts with log and incident context in one workflow.
Observes application and infrastructure health with monitoring dashboards, alert policies, and performance insights.
Aggregates infrastructure metrics, application traces, and logs and triggers alerts based on monitored signals.
Builds dashboards and alert rules for metrics and logs from supported data sources like Prometheus and Loki.
Collects time-series metrics from instrumented targets and exposes queryable data for alerting and visualization.
Routes and groups firing alerts from Prometheus into deduplicated notifications with configurable notification receivers.
Manages incident response with alert ingestion, on-call scheduling, escalations, and post-incident workflows.
UptimeRobot
website monitoringMonitors website and server endpoints with keyword, uptime, and alert checks and routes notifications via email, SMS, or integrations.
Keyword monitoring on HTTP responses to detect broken pages even when servers stay online
UptimeRobot focuses on uptime and website monitoring with a straightforward setup that supports multiple check types. It monitors endpoints on schedules and pushes real-time alerts through multiple channels such as email and SMS. It also provides uptime history and reporting views so teams can spot downtime patterns without building custom dashboards.
Pros
- Fast endpoint monitoring with simple check configuration
- Reliable alerting via email and SMS for downtime notifications
- Uptime history and reporting help diagnose recurring issues
- Supports multiple monitor types like HTTP, keyword, and port checks
- Bulk monitor management reduces setup time for many endpoints
Cons
- Limited native incident workflows compared with full ITSM tools
- Reporting stays focused on uptime and does not replace analytics suites
- Advanced monitoring customization requires more manual setup
Best For
Teams needing low-friction uptime monitoring and alerting across many endpoints
More related reading
Pingdom
uptime monitoringPerforms synthetic uptime checks for websites and web services and provides performance breakdowns with alerting and reporting.
Uptime and performance monitoring with actionable alerts and detailed downtime reporting
Pingdom stands out with its purpose-built website and server monitoring for keeping uptime visible and actionable. Core capabilities include scheduled uptime checks, performance and response-time tracking, and alerting when incidents occur. Detailed downtime and availability reporting helps teams correlate service changes with monitoring outcomes. Browser, API, and synthetic monitoring style options support more than basic ping checks.
Pros
- Fast setup for uptime checks with clear status history and incident timelines
- Multiple monitoring types including website, performance, and synthetic checks
- Alerting supports routing via common integrations for faster incident response
Cons
- Less suited for complex application observability like traces across services
- Synthetic scripts can require careful maintenance as pages and flows change
- Dashboards can feel monitoring-centric rather than workflow-automation oriented
Best For
Operations and web teams needing reliable uptime monitoring and alerting
Statuspage
status communicationsPublishes customer-facing service status pages with incident posting, real-time updates, and configurable notifications.
Incident timelines with automated component impact and public posting workflow
Statuspage delivers branded service status pages with real-time incident updates and subscriber notifications. It supports components, incident timelines, and public posting workflows for IT and engineering teams. The platform also offers integrations that can automate updates from common monitoring and alert sources. Designed for communication consistency, it helps teams maintain a single source of truth during outages.
Pros
- Incident and component modeling supports clear public communication
- Timeline updates and status labels keep stakeholders informed consistently
- Notification subscriptions reduce manual outreach during outages
- Brand customization helps match customer-facing communication standards
Cons
- Advanced automation and workflows depend heavily on external tooling
- Cross-system analytics and root-cause reporting are not a core focus
- Complex multi-tenant setups can require careful planning
Best For
Teams needing branded outage communications with component-level incident tracking
More related reading
Better Stack (Uptime)
uptime + alertsChecks application endpoints for uptime and performance and sends alerts with log and incident context in one workflow.
Uptime monitoring with historical status timelines for endpoint health
Better Stack (Uptime) centers on service monitoring with clear status visibility across web endpoints, APIs, and uptime checks. It pairs scheduled monitoring with alerting paths that route incidents to the right channels and teams. The tool also emphasizes incident timelines and historical availability so operators can correlate outages with changes and follow-up actions.
Pros
- Multiple endpoint checks with straightforward configuration
- Alert routing supports fast incident response across channels
- Availability history and status timelines help with outage review
Cons
- Focused on uptime checks and less on application performance metrics
- Alert tuning can require iteration to reduce noise
Best For
Teams monitoring public services and APIs with fast alerting and history
New Relic
observabilityObserves application and infrastructure health with monitoring dashboards, alert policies, and performance insights.
Distributed tracing with service maps that correlates spans, metrics, and logs
New Relic stands out with deep observability coverage that spans application performance, infrastructure, and distributed traces in one workflow. Core capabilities include real-time APM with request traces, infrastructure metrics, log analytics, and alerting tied to service-level objectives. The platform also supports full-funnel monitoring from code-level spans to server and container signals, which helps teams pinpoint where latency and errors originate.
Pros
- Unified APM, infrastructure, and logs reduces cross-tool debugging time
- Distributed tracing pinpoints latency drivers across services with actionable spans
- Flexible alerting and SLO tracking connect incidents to user impact
Cons
- High instrumentation depth can create configuration complexity
- Dashboards and alerting tuning takes time to avoid noisy signals
- Data ingestion and retention planning adds operational overhead
Best For
Platform and engineering teams needing end-to-end observability and fast incident triage
Datadog
infrastructure monitoringAggregates infrastructure metrics, application traces, and logs and triggers alerts based on monitored signals.
Service Maps with dependency visualization across traces and infrastructure
Datadog’s core strength is deep, unified observability for metrics, logs, and traces across infrastructure, containers, and apps. It provides dashboards, alerting, and SLO-style monitoring so teams can connect performance signals to incidents. Its workflow-friendly features include service maps and anomaly detection to speed root-cause discovery. Datadog also supports alert routing and integrations across common cloud and tooling ecosystems.
Pros
- Unified metrics, logs, and traces reduces cross-tool debugging overhead.
- Service maps connect dependencies for faster incident root-cause analysis.
- Anomaly detection and SLO-style monitoring improve signal quality for alerts.
Cons
- High configuration depth can slow setup and tuning for new teams.
- Alert noise can persist without disciplined threshold and ownership design.
- Advanced analytics and workflows often require strong platform knowledge.
Best For
Platforms teams needing end-to-end observability with trace-to-incident workflows
More related reading
Grafana
dashboardingBuilds dashboards and alert rules for metrics and logs from supported data sources like Prometheus and Loki.
Unified alerting with query-based rules and configurable notification routing
Grafana stands out with a highly flexible dashboard and visualization layer for monitoring and analytics data. It supports time series dashboards, alerting rules, and interactive exploration through queries against common data sources. Its ecosystem integrates easily with Grafana data source plugins and visual panels for building operational views. For Boiler Software use cases, it accelerates dashboard-driven boilerplate environments by standardizing panels, variables, and alerts across teams.
Pros
- Rich dashboarding with templates, variables, and reusable panel patterns
- Powerful alerting tied to query results and dashboard context
- Large plugin ecosystem for integrating diverse data sources
Cons
- Setup and tuning take effort, especially for complex data sources
- Alert lifecycle management across many dashboards can become operationally noisy
- Building consistent boilerplate experiences often needs governance and conventions
Best For
Teams standardizing monitoring dashboards and alerting workflows across services
Prometheus
metrics collectionCollects time-series metrics from instrumented targets and exposes queryable data for alerting and visualization.
PromQL query engine with time-series functions and instant and range queries
Prometheus stands out as a monitoring system built around the PromQL query language and time-series data model. It captures and stores metrics from instrumented services, then supports alerting rules that trigger on metric thresholds and patterns. It integrates well with exporters and service discovery so metric collection can scale across dynamic environments.
Pros
- PromQL enables expressive time-series queries for deep troubleshooting
- Built-in alerting rules based on metric evaluation reduce manual monitoring
- Exporters and service discovery simplify collection across many targets
- Long-term time-series storage and downsampling support historical analysis
Cons
- Operational overhead grows with retention policies, storage, and scaling
- Dashboards and workflows require additional tooling beyond core metrics
Best For
Engineering teams standardizing metrics monitoring with PromQL and alerting
More related reading
Alertmanager
alert routingRoutes and groups firing alerts from Prometheus into deduplicated notifications with configurable notification receivers.
Inhibition rules that mute dependent alerts when higher-severity conditions are firing
Alertmanager stands out for its dedicated alert routing and suppression layer for Prometheus alerting. It deduplicates and groups alerts, then delivers notifications through configurable receiver integrations. Core capabilities include silences, inhibition rules, and fine-grained routing based on alert labels. It operates as a separate service that pairs with Prometheus Alertmanager configuration rather than embedding alert logic into dashboards.
Pros
- Powerful routing by alert labels with nested route trees
- Alert grouping reduces noise via group_by and wait intervals
- Silences support fast, targeted suppression without redeploying alerts
- Inhibition rules prevent redundant firing across related alert types
- Receiver integrations handle common notification channels for teams
Cons
- Configuration complexity grows quickly with deep routing trees
- Debugging delivery outcomes requires careful inspection of logs and state
- Works best with Prometheus alert semantics and label conventions
- No built-in workflow UI for approvals beyond silences management
Best For
Operations teams needing configurable alert routing, grouping, and suppression
PagerDuty
incident responseManages incident response with alert ingestion, on-call scheduling, escalations, and post-incident workflows.
Incident command center with live timelines, escalation actions, and response workflow controls
PagerDuty distinguishes itself with event-driven incident orchestration that routes alerts into structured workflows across teams. It supports monitoring and ticketing integrations, escalation policies, on-call scheduling, and incident timelines with real-time status updates. Its core strength is connecting alert sources to responders through automation rules, digital handoffs, and post-incident reporting.
Pros
- Event orchestration turns alerts into guided, auditable incident timelines
- Configurable escalation policies and on-call schedules match team response models
- Deep integrations with monitoring tools reduce manual triage steps
- Automation rules support routing, grouping, and lifecycle actions
Cons
- Setup complexity rises with multi-team escalation and workflow customization
- Signal-to-noise tuning requires ongoing maintenance of alert rules
Best For
Operations and SRE teams needing reliable on-call workflows and incident automation
How to Choose the Right Boiler Software
This buyer's guide explains how to choose Boiler Software by mapping monitoring, alerting, incident workflow, and analytics capabilities to real operational needs. It covers UptimeRobot, Pingdom, Statuspage, Better Stack (Uptime), New Relic, Datadog, Grafana, Prometheus, Alertmanager, and PagerDuty. The guide shows which tools excel for uptime checks, incident communication, observability with traces, and alert routing and suppression.
What Is Boiler Software?
Boiler Software is the monitoring and alerting layer that continuously checks services, evaluates signals, and delivers incidents to the right people with enough context to respond. It typically combines endpoint or metrics monitoring, alert rules, alert routing, and incident timelines or status communication. Teams use it to detect downtime quickly, reduce alert noise, and link issues to performance or traces. In practice, tools like UptimeRobot and Better Stack (Uptime) focus on endpoint uptime checks and alert delivery, while Prometheus and Alertmanager focus on metric collection and routing for label-driven alerts.
Key Features to Look For
The right feature set determines whether incidents reach responders with the right signal quality and enough context to act fast.
Endpoint uptime and content health checks
UptimeRobot excels at HTTP keyword monitoring that checks HTTP responses for broken pages even when servers stay online. Pingdom and Better Stack (Uptime) also provide uptime checks with actionable alerts and endpoint history so teams can diagnose recurring failures.
Detailed uptime reporting with timelines
Pingdom provides clear status history and incident timelines that help operations correlate service changes with monitoring outcomes. Better Stack (Uptime) and UptimeRobot emphasize historical availability and status timelines so teams can review outages with operational context.
Customer-facing incident communication with component impact
Statuspage provides incident timelines with component-level impact modeling and a public posting workflow. This supports consistent stakeholder updates through incident updates and configurable notification subscriptions.
Unified observability with traces and correlated signals
New Relic uses distributed tracing and service maps that correlate spans, metrics, and logs for faster root-cause discovery. Datadog provides service maps that visualize dependencies across traces and infrastructure to connect performance symptoms to responsible components.
Query-driven alerting powered by metrics or logs
Grafana enables query-based alert rules tied to dashboard context, which supports consistent alert logic across dashboards. Prometheus provides a PromQL query engine with instant and range queries, and it drives alerting from time-series evaluations.
Alert routing, deduplication, and suppression to control noise
Alertmanager routes and groups firing alerts into deduplicated notifications and uses silences plus inhibition rules to mute dependent alerts. PagerDuty turns alert events into guided incident timelines with escalation policies and on-call scheduling so responders receive the right escalation sequence.
How to Choose the Right Boiler Software
Choosing the right tool starts with matching the monitoring signal source and the incident workflow needs to specific capabilities in the top options.
Define what counts as a failure before picking tooling
If broken pages must be detected even when servers respond, UptimeRobot keyword monitoring checks HTTP response content rather than only endpoint reachability. If performance and availability must be reviewed together, Pingdom combines uptime checks with performance breakdowns so alert context includes response-time impact.
Pick the workflow surface area needed during incidents
If the priority is publishing a branded customer-facing status page with consistent incident updates, Statuspage provides component modeling, incident timelines, and public posting workflows. If responders need live incident orchestration and escalations, PagerDuty builds event-driven incident timelines with escalation policies and on-call scheduling.
Choose the data foundation that matches the organization’s monitoring maturity
If the organization already operates with metrics and time-series alerting, Prometheus provides PromQL time-series queries and alerting rules evaluated from metrics. If the organization needs deep application and infrastructure observability in one place, New Relic and Datadog provide distributed traces, service maps, and alert policies tied to user impact and SLO-style monitoring.
Decide who owns alert logic and how routing is handled
If alert routing must be label-driven with deduplication and suppression, Alertmanager provides nested route trees, silences, and inhibition rules that mute dependent alerts. If teams want alert rules embedded in reusable dashboards, Grafana provides unified alerting with query-based rules and configurable notification routing.
Validate signal quality and tuning effort with a small pilot
Datadog and New Relic can require configuration and tuning effort because distributed tracing and unified observability add depth to alert logic. Grafana and Alertmanager also require careful management because alert lifecycle across many dashboards and complex routing trees can become operationally noisy without label conventions and governance.
Who Needs Boiler Software?
Boiler Software fits teams that need continuous monitoring plus alert delivery and incident communication workflows across uptime, performance, and deeper observability signals.
Teams that need low-friction uptime monitoring across many endpoints
UptimeRobot fits this need because keyword monitoring on HTTP responses detects broken pages and it supports multiple monitor types like HTTP, keyword, and port checks. Better Stack (Uptime) also fits because it pairs scheduled monitoring with alert routing and historical availability timelines.
Operations and web teams that need uptime plus performance breakdowns
Pingdom matches this use case because it combines uptime checks with performance and response-time tracking and routes alerts for fast incident response. Better Stack (Uptime) also supports fast alerting and historical status timelines for endpoint health review.
Teams that must publish customer-facing outage communication with component detail
Statuspage fits because it models incidents and components, maintains incident timelines, and automates public posting workflows with subscriber notifications. This supports a single source of truth for stakeholder communication during outages.
Platform and engineering teams that need end-to-end observability and trace-to-incident triage
New Relic and Datadog fit this segment because both provide distributed tracing and service maps that correlate spans, metrics, and logs or visualize dependencies across traces and infrastructure. These tools support flexible alerting tied to SLO-style monitoring so incidents connect to user impact during triage.
Common Mistakes to Avoid
Common failures across these tools come from mismatching monitoring signals to incident workflows and underestimating tuning and governance needs.
Only monitoring server reachability and missing broken pages
UptimeRobot avoids this problem by using keyword monitoring on HTTP responses to detect broken pages even when servers stay online. Pingdom and Better Stack (Uptime) reduce the gap by combining uptime checks with performance and endpoint health reporting.
Using a monitoring dashboard as an incident communication system
Grafana provides query-based alerting but it does not provide the branded public posting workflow and component modeling needed for customer-facing status updates. Statuspage is built for incident timelines and public posting workflows with consistent stakeholder communication.
Letting alerts flood responders without routing and suppression design
Alertmanager controls notification noise through alert grouping, deduplication, silences, and inhibition rules that mute dependent alerts. PagerDuty also reduces manual triage by orchestrating events into structured incident timelines with escalation policies and on-call schedules.
Avoiding signal depth until root-cause is required
Prometheus and Grafana can be effective for metrics and dashboards, but they do not provide distributed tracing correlation by themselves for complex dependency issues. New Relic and Datadog add distributed tracing and service maps so teams can pinpoint latency drivers and dependency failures faster.
How We Selected and Ranked These Tools
we evaluated every tool on three sub-dimensions. Features carry weight 0.40 because monitoring, alerting, incident workflows, and context determine whether teams can act on signals. Ease of use carries weight 0.30 because configuration and day-to-day operational friction affect adoption. Value carries weight 0.30 because teams need practical outcomes from the signals and workflows, not just capability lists. the overall rating is the weighted average of those three, computed as overall = 0.40 × features + 0.30 × ease of use + 0.30 × value. UptimeRobot separated itself with keyword monitoring on HTTP responses because that capability improves failure detection without requiring deep instrumentation, which directly boosts the features dimension while keeping setup approachable for many endpoints.
Frequently Asked Questions About Boiler Software
Which tools cover Boiler Software monitoring end-to-end, from uptime checks to incident response?
UptimeRobot and Pingdom cover scheduled uptime checks and response-time alerting for web endpoints. PagerDuty then orchestrates those alerts into on-call workflows with escalation policies and live incident timelines.
How do teams standardize “Boiler Software” dashboards and alert logic across many services?
Grafana provides a flexible dashboard layer that supports reusable panels, variables, and query-driven alert rules across teams. Prometheus supplies the metrics and PromQL queries that back those standardized dashboards and alert thresholds.
What’s the best way to publish a single source of truth during an outage?
Statuspage posts branded service status updates with component-level tracking and an incident timeline. It also supports automations that can push updates from common monitoring and alert sources into the public workflow.
Which option is strongest for root-cause analysis when latency and errors appear during a boiler deployment?
New Relic and Datadog connect performance signals to incident triage using tracing and cross-signal workflows. New Relic adds distributed tracing with service maps, and Datadog adds service maps plus anomaly detection to speed dependency-level investigation.
How does Prometheus alerting differ from Grafana alerting for Boiler Software use cases?
Prometheus uses alerting rules driven by metrics patterns and threshold logic expressed with PromQL. Grafana provides unified alerting rules tied to query results and can route notifications, but Prometheus remains the core engine for PromQL-based evaluation.
What problem does Alertmanager solve when too many similar alerts flood on-call responders?
Alertmanager groups, deduplicates, and suppresses alerts before they reach paging workflows. Its inhibition rules can mute dependent alerts when a higher-severity condition fires, reducing noise from cascading failures.
Which tools help teams monitor not just uptime but broken pages and degraded user experiences?
UptimeRobot can monitor HTTP responses and detect broken pages even when servers remain online. Pingdom tracks response time and provides actionable availability and downtime reporting so operations teams can correlate incidents with performance drops.
How do teams connect alert events to the correct responder and workflow automatically?
PagerDuty maps alert events into structured workflows using routing rules, escalation policies, and on-call scheduling. Better Stack (Uptime) also routes incidents through alerting paths so teams can land notifications in the right channels faster.
What integration pattern works well for building a Boiler Software monitoring stack with minimal glue code?
A common pattern pairs Prometheus for metric collection with Grafana for visualization and alert rule configuration. Alertmanager handles grouping and suppression, then PagerDuty delivers the final incident orchestration with escalation and timelines.
Conclusion
After evaluating 10 utilities power, UptimeRobot stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Utilities Power alternatives
See side-by-side comparisons of utilities power tools and pick the right one for your stack.
Compare utilities power tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.