rPower is a software platform focused on energy management, building performance analytics, and operational monitoring for commercial properties, campuses and utility customers. The platform collects meter and sensor data, normalizes it across different systems, and applies analytics and rules to surface savings opportunities, faults, and performance trends. rPower targets facilities managers, energy engineers, sustainability teams, and energy service companies (ESCOs) that need continuous insight into HVAC, lighting, chilled water, submeters and tenant consumption.
rPower typically combines cloud-hosted analytics with on-premises connectors and building automation system (BAS) adapters so sites with different vendor equipment can be monitored from a single pane of glass. The product supports both portfolio-level views for enterprise stakeholders and detailed equipment- and zone-level diagnostics for operations teams. Deployments commonly include a mix of retained historical meter data, real-time streaming data and scheduled batch imports to support billing and compliance reporting.
rPower's architecture is oriented to integrate with existing BAS, submeters and IoT gateways; it is often used where teams want to reduce energy spend, document performance improvements from capital projects, and automate alerting for critical systems.
rPower ingests energy, environmental and operational data, then organizes and presents it through dashboards, automated reports and rule-based alerts. Core functionality includes data aggregation, normalization, time-series storage, KPI calculations (like energy intensity and load factor), and visualization. The platform lets users define thresholds and custom rules to trigger notifications or opening of service tickets when equipment deviates from expected behavior.
Other built-in capabilities include tenant energy allocation and billing, automated regression analysis for savings verification, and benchmarking across buildings or portfolios. rPower also provides scheduling and reporting templates for regulatory compliance and internal sustainability tracking.
rPower acts as both an operational tool for day-to-day facilities management and an analytic engine for energy managers who need to prioritize capital projects, verify savings from retrofits or participate in demand response programs.
Rpower offers these pricing plans:
Prices above reflect typical SaaS licensing by site and are intended as baseline examples. For exact, current licensing tiers, seat counts and enterprise terms, check rPower's pricing and licensing information (https://www.rpower.com/).
Rpower starts at $49/month per site for the Starter subscription when billed monthly. Monthly billing is convenient for short pilots or proof-of-concept sites; annual billing typically reduces the effective monthly rate for multi-site deployments.
Rpower costs $468/year per site for the Starter plan when billed annually at the equivalent of $39/month per site. Professional-level annual billing commonly falls in the $1,908/year per site range when billed at the discounted monthly equivalent ($159/month billed annually).
Rpower pricing ranges from $0 (free trial) to enterprise-tier custom pricing, with typical SaaS site subscriptions falling between $39/month (billed annually) and $159/month (billed annually) depending on feature set, meter counts, and support levels. Large portfolios and utility deployments frequently move to custom enterprise agreements where pricing is negotiated based on the number of meters, required integrations, data retention and professional services.
Check rPower's pricing and licensing information (https://www.rpower.com/) for official rates, pilot offers and enterprise procurement details.
rPower is used to centralize energy and operational data and convert it into actionable insight. Facilities teams use it to detect HVAC faults early, prioritize maintenance work orders, and measure the effect of retrofits. The platform's analytics help quantify savings and provide evidence for capital project payback and ongoing commissioning programs.
Energy managers use rPower for portfolio benchmarking and to identify underperforming assets. The tenant billing module enables accurate allocation of shared building loads and supports revenue recovery in multi-tenant buildings. Sustainability teams use automated reports to satisfy internal targets and external reporting requirements such as utility incentive programs.
Other common uses include submeter aggregation for multi-site chains, demand response participation through load-shedding schedules, and procurement verification during supplier transitions. rPower can support continuous commissioning workflows, reducing recurring energy losses and improving occupant comfort metrics.
rPower's strengths are its focus on time-series analytics, interoperability with common BAS protocols, and a set of operational features tuned for facilities teams. Users typically praise the platform's ability to consolidate heterogeneous data sources, the fault detection rules engine, and tenant billing capabilities. The ability to create scheduled reports and to export standardized data sets for third-party analysis is also commonly cited.
Limitations include the usual complexity of integrating with legacy BAS and meters — some projects require on-site gateway configuration or professional services. For very small sites or single-family deployments, the platform can be more capable (and expensive) than needed. Organizations with strict on-premises requirements may need the Enterprise package or additional services to meet data residency and security controls.
Another consideration is product fit: teams that need only basic dashboards or very lightweight alarms might prefer lower-cost visualization tools, while enterprises with complex HVAC systems will value rPower's deeper analytics and automation features.
rPower typically offers trial or pilot access through the Free Plan tier so teams can evaluate core ingestion, dashboards and a subset of analytics on a limited number of meters. Trials often run for a fixed period (30–90 days) and include onboarding support or a pilot engineer to accelerate deployment and validate data connections.
A pilot is usually intended to test integrations with the site's BAS, confirm meter mapping, and validate one or two fault-detection rules or tenant billing runs. Trials provide an effective way to demonstrate measured savings from a single retrofit or to validate meter-level reporting before wider roll-out.
To request a demo or pilot, many organizations use the vendor's contact form or schedule an on-site scoping session; see rPower's product and contact pages for pilot request details (https://www.rpower.com/).
Yes, rPower offers a Free Plan for evaluation and small pilots, typically limited to one site and a small number of meters. The free tier is intended for proof-of-concept and basic dashboards; full analytics, extended retention and enterprise integrations are available on paid plans.
rPower provides programmatic access through a RESTful API and supports common industrial protocols for building systems integration. The REST API exposes endpoints for time-series ingestion, meter metadata, event and alarm creation, and queryable KPIs. Authentication is commonly implemented via API keys or OAuth 2.0 tokens for enterprise customers.
Beyond REST, rPower supports data ingestion via BACnet, Modbus, MQTT and secure OPC connections, and can accept pushed data from IoT gateways or third-party aggregators. Real-time alerting is available via webhooks and allows integration with ticketing systems and chat platforms. SDKs and sample client libraries are provided for common development environments to accelerate integrations.
Common integrations include building automation systems, energy meters and submeters, ERP systems for tenant billing, and business intelligence tools. For developer documentation and example API workflows, refer to rPower's product documentation and developer resources (https://www.rpower.com/).
Rpower is used for energy management, fault detection and tenant billing across buildings and portfolios. Facilities and energy teams deploy it to centralize meter data, detect equipment faults, quantify savings from retrofits, and allocate energy costs to tenants. The platform supports both operational alerts and longer-term benchmarking.
Yes, Rpower supports common BAS protocols such as BACnet and Modbus and integrates with IoT gateways. It can ingest real-time points and scheduled data from a variety of controllers, enabling normalized telemetry across different vendor equipment. Professional services are often used for complex legacy systems.
Rpower starts at $49/month per site for the Starter plan when billed monthly, with discounted annual rates available that lower the effective monthly cost. Enterprise deployments are priced via custom quotes depending on meters, integrations and service level requirements.
Yes, Rpower offers a Free Plan intended for pilots and small evaluations, typically limited to a single site and a small number of meters. Full analytic capabilities, extended data retention and enterprise integrations require paid plans.
Yes, Rpower includes tenant billing and allocation features that map submeters to tenants, apply utility rate schedules, and produce invoices or allocation reports. This functionality helps landlords recover energy costs and provides transparent tenant statements.
Rpower supports integrations such as webhooks and direct connectors to collaboration platforms so teams can receive alerts and summary reports in chat tools or ticketing systems. Integrations can be configured to forward alarms to operations teams or to create incidents automatically.
Yes, Rpower provides a RESTful API and webhook support for programmatic access. The API exposes time-series data, metadata, alarms and billing records; developers can use API keys or OAuth tokens to build custom dashboards and integrations.
Yes, Rpower includes fault detection and diagnostics (FDD) capabilities. The rules engine analyzes trend patterns, equipment runtimes, and temperature setpoint deviations to surface likely failures and efficiency losses, helping operations teams prioritize corrective work.
Rpower adheres to common enterprise security practices including encrypted transport (TLS), role-based access controls and single sign-on options for Enterprise customers. For regulated or highly sensitive deployments, customers typically request SOC or ISO compliance documentation during procurement.
Deployment time varies but pilot deployments can be completed in 4–8 weeks. Time depends on the number of integrations, meter onboarding complexity and whether on-site gateway configuration is required. Enterprise rollouts with many sites typically follow a phased approach with pilot, iterate and scale stages.
rPower hires across product, engineering, data science and customer success roles to support its analytics and integration services. Career opportunities for data engineers and building systems integrators are common because the product combines time-series analytics with industrial system connectivity. Roles often emphasize experience with IoT, cloud platforms and building automation protocols.
Working at rPower typically involves a mix of field deployments and remote engineering—data teams focus on analytics models and rule development while field teams handle gateway setup, meter mapping and site onboarding. Larger organizations may offer roles in solutions architecture and professional services to lead enterprise rollouts.
To explore open positions and learn about application procedures, consult the company's careers page and LinkedIn presence for the most current listings (https://www.rpower.com/).
rPower partners with ESCOs, energy consultants and systems integrators to expand deployment reach and speed implementation. Affiliate and reseller agreements commonly include referral commissions, joint delivery models and authorized implementation training. Affiliates typically benefit from co-marketing materials, technical onboarding and lead-sharing programs.
If you are an energy service provider or systems integrator interested in partnering, rPower usually provides partner tiers and enablement resources to certify integration specialists and to support joint sales activities. Contact the vendor's partner program team to request partnership requirements and commission structures (https://www.rpower.com/partners).
Independent reviews and case studies can be found on industry publications, energy-focused forums and trade conference write-ups. Look for case studies published on the vendor site that document measured savings, commissioning outcomes and tenant billing implementations. For user opinions, search energy management forums, LinkedIn groups and building operations communities where facilities managers share deployment experiences.
For vendor-published references and validated customer success stories, review rPower's case studies and whitepapers on the company's resource pages (https://www.rpower.com/). Contact rPower for customer references if you require direct conversations with existing users.