What is onePump?

onePump is an early product concept for an integrated residential thermal energy hub: one coordinated heat pump system that can serve home cooling, home heating, domestic hot water, and pool heating from a shared thermal loop. Its goal is to coordinate these loads, reuse useful heat when possible, and allocate scarce capacity predictably — comfort first, hot water next, and pool heating deferrable.

Is it available to buy?

No. onePump is under development. No production hardware, firmware, or equipment control software exists, so there is no product to purchase, no price, and no launch date. The status section on the home page reflects the current stage.

Why not keep separate systems?

Separate systems are simpler to replace one at a time, but they cannot coordinate loads or recover useful cooling heat as a system. A coordinated system can redirect heat removed from the home in cooling season to hot water or the pool instead of rejecting it outdoors, and can respond to solar, battery, and time-of-use signals as a whole.

Will my pool heat more slowly?

It may, depending on installed capacity and priority settings. onePump is designed to set pool-readiness expectations with schedules and forecasts instead of promising instant recovery. Pool heating is treated as schedulable and interruptible unless the installer explicitly configures dedicated capacity.

What happens if something breaks?

The architecture aims to isolate failures by load where possible: a pool-loop fault should not disable space comfort or domestic hot water unless the shared heat pump or primary loop is affected. That behavior is planned and must be validated before pilot use, not claimed today.

Will installers understand it?

Installer repeatability is a central product risk. The concept includes a commissioning checklist, dry-run validation before automatic operation, and diagnostics that identify sensor, pump, valve, and heat exchanger problems. None of this is deployed today.

What exists today?

The repository contains an executable Python simulator (onepump_sim) for load-priority and heat-recovery behavior, a Stage 1 scorecard that recorded a "narrow" decision, controller-platform discovery research, and the local research walkthrough on the home page. There is no hardware, firmware, or field data.

Is the walkthrough an offer?

No. The package scopes and dollar ranges shown in the walkthrough are illustrative research prompts for comparing candidate package boundaries, not offers or binding quotes. Research observations do not by themselves establish demand, pricing, savings, or field performance.

Does this site track me?

No. This is a plain static site with no analytics, no cookies, and no forms that submit. Nothing you enter in the walkthrough is sent or saved; reloading resets it.

How can I follow progress?

The onePump repository holds the requirements, plans, simulator, and evidence-gated status. The README status line is the source of truth for where the project stands.