.svg "Watter")
Every startup needs compute power. Few can afford to waste it. This is the story of how WATTER is turning buildings into a distributed cloud, built for speed, cost, and sustainability.
Estimated time to read: 16 minutes
The Startup Compute Squeeze
Startups live and die by their ability to experiment quickly. The challenge is that experimentation now runs on GPUs, and access to those GPUs is both scarce and expensive. The rise of AI has turned cloud bills into a second payroll, and for many early-stage teams the numbers don’t add up.
Cloud providers have made it remarkably easy for developers to get started. With generous credits, seamless tooling, and ecosystems that feel familiar, most startups begin their journey on AWS, Azure, or GCP without a second thought. That model works well for early development and testing, when the priority is speed and low upfront cost. The challenge comes later, when prototypes turn into production systems. GPU capacity becomes scarce, inference workloads demand predictable performance, and proximity to customer data starts to matter. Add in egress charges and rising infrastructure bills, and what felt frictionless at the start can quickly become a constraint.
As startups move from early development into customer-facing deployments, the requirements change. Latency, reliability, and cost become much harder to ignore. This is where edge computing offers a different trajectory. By processing data closer to its source, edge deployments reduce round-trip times, enable faster feedback loops, and eliminate much of the bandwidth overhead that drives up costs in centralized models. For startups, that translates into quicker experimentation, smoother scaling, and more room to extend their runway.
Hyperscale providers remain valuable for early prototyping, but their economics and architectures are designed for global scale rather than local responsiveness. WATTER enters at the point where those limitations start to bite. By embedding compute directly inside the infrastructure people already rely on, WATTER provides startups with the ability to deploy quickly, iterate at lower cost, and align their operations with a sustainability story that creates immediate value.
As Narasimha Krishnakumar, WATTER’s Chief Product Officer, explains: “For startups, compute isn’t just a cost line, it’s existential. We make it affordable, local, and green.”
The Unique Value Proposition for Startups
Narasimha Krishnakumar often describes WATTER’s approach as “frictionless local access.” For startups, that phrase captures something important: many would prefer to have local machines they can tune and experiment with directly, rather than being constrained by the abstractions of cloud services. Physical access allows for faster iteration and deeper innovation, but maintaining on-premise hardware has rarely been practical.
WATTER was designed with that reality in mind. By embedding servers inside facilities that are close to where startups operate, the company makes compute power physically and logically accessible. This reduces the friction that slows young teams and creates the shortest possible path from idea to deployment. At the same time, those same servers do double duty by heating water for the building’s occupants. The result is infrastructure that is local, useful, and sustainable. This is not about competing head-to-head with AWS or Azure, but about providing a complementary option when cost, latency, or sustainability become blockers.
Local Compute Access
Instead of running workloads in remote data centers, startups can tap into GPU power close to where they are. This reduces latency, accelerates iteration, and avoids the bandwidth costs that come with constantly moving data back and forth to the cloud. Distributed edge computing consistently delivers ultra-low latency, which is critical for applications like video analytics, robotics, AR/VR and other AI applications where local control/automation is required. The same advantage applies to facilities that rely on video analytics for monitoring, such as retail stores or hotels. By processing those feeds locally, startups and facilities gain faster results and lower operating costs. For teams building AI agents and real-time applications, this proximity delivers both a technical and financial edge.
Green Energy Through Heat Reuse
Every cycle of compute generates heat. WATTER captures that heat and routes it into building appliances such as water heating systems. Unlike traditional data centers, WATTER does not require an abundance of fresh water for cooling. Instead, it reuses the water already circulating in the facility to cool the servers, creating a closed, efficient loop.
Startups using WATTER gain not only affordable compute but also a built-in ESG narrative. Case studies from Europe demonstrate that heat recovery from servers can provide enough thermal energy to supply thousands of homes and businesses. Instead of pledging offsets, startups can point to infrastructure that creates visible, measurable sustainability outcomes.
Flexibility Without Lock-In
WATTER complements existing cloud strategies rather than trying to replace them. For startups, this means freedom to choose the right environment for the right workload. Containerized applications already run consistently across environments, which makes it easy to direct workloads to WATTER clusters without major changes. Dev and test environments are the natural first step, giving teams the chance to try WATTER while keeping the rest of their stack unchanged. As confidence grows, usage can scale organically—without the risk of lock-in that often comes with traditional hyperscalers.
Together, these three dimensions—proximity, sustainability, and flexibility—give startups a path to compute that is aligned with their constraints and ambitions. They can move faster, spend less, and embrace sustainability at a stage when every advantage matters.
Adoption and Incentives: Lowering the Barrier
Infrastructure only matters if teams can actually use it, and the adoption curve for startups is unforgiving. Most founders do not have the time or resources to re-architect their stack just to test a new provider. They need pathways that feel familiar and safe, with low switching costs and clear upside. Narasimha Krishnakumar, WATTER’s Chief Product Officer, emphasizes this point: the journey into WATTER has to be simple, incremental, and low-risk. This is especially true for startups building AI applications and agents, where data scientists and researchers need rapid, repeated cycles of model creation, testing, and deployment.
Containerization as a Bridge
For many startups, containerization is already standard practice. Applications packaged in Docker or Kubernetes run consistently across environments, which makes shifting workloads to WATTER straightforward. Developers don’t need to rebuild their stack; they simply point their containers to a new cluster. As Krishnakumar notes, “Dev/test workloads are very easy to move.” This echoes industry research highlighting containerization as the safest way to migrate workloads between clouds, lowering both risk and cost.
Dev/Test as the First Step
Startups working on AI agents and models live on iteration, and dev/test workloads are the engines of that cycle. Running them locally on WATTER can help reduce latency, accelerate debugging, and shorten feedback loops. Analysts tracking edge adoption have pointed out that dev/test workloads are often the first to move to edge environments precisely because of their low risk and high iteration value.
Marketplaces and API-First Access
Ease of use extends beyond development and deployment to how a product/service is consumed. WATTER compute power is available through established GPU marketplaces and exposed via an API-first interface, allowing developers to spin up and manage workloads in minutes. Research into API-first infrastructure shows that developers consistently rank simplicity and modularity as top adoption drivers, and WATTER’s approach is built around those same principles.
Early-Adopter Incentives
To accelerate adoption, WATTER offers programs designed specifically for early-stage teams: pilot opportunities, usage credits, and tailored partnerships. This mirrors broader trends in compute infrastructure, where early adopter programs and proof-of-concept pilots have proven effective in de-risking adoption for startups while creating visibility for new platforms.
The result is an adoption path that feels incremental rather than disruptive. Startups can begin with dev/test workloads, validate the latency and cost benefits, and expand into production when ready. Marketplaces and APIs make it easy to get started in minutes, while pilot programs and credits reduce the financial risk of trying something new. And because WATTER compute power is already live, this isn’t a future promise—it’s an immediate opportunity. Teams can tap into GPUs today, experience the difference firsthand, and secure an advantage while the platform is still in its early, high-leverage stage.
Economics and ROI
For most startups, infrastructure decisions come down to one question: will this extend our runway or shorten it? Compute is often the largest single line item after payroll, and every percentage point of savings translates into more time to build. WATTER’s model reshapes that calculation by creating value for both the startup and the facility hosting the hardware.
Startup Economics
WATTER offers competitive GPU pricing compared to hyperscale providers, but the real value comes from the absence of hidden costs. Startups often complain about egress fees and bandwidth charges in centralized clouds, which can double or triple bills unexpectedly (a common pain point raised in Reddit forums e.g. r/startups and r/cloudcomputing). By processing workloads locally, WATTER reduces the volume of data traveling across networks, cutting both latency and bandwidth expenses. Research shows that edge computing not only lowers latency but also optimizes bandwidth and reduces total operational costs.
Facilities Economics
On the facility side, economics are even more direct. Every GPU cycle produces heat, and in WATTER’s model that heat is captured and reused for hot water. Case studies from Europe show that heat recovery from servers can offset significant utility costs. In Odense, Denmark, data center waste heat now supplies district heating for 11,000 homes. Similar projects in Finland demonstrated payback periods as short as five years for operators. WATTER adapts these same principles at the building level, giving hotels and other facilities day-one savings by reducing their water-heating bills. As Krishnakumar notes, “From day one, they are able to get their money back.”
A Shared Flywheel
This creates a flywheel effect: facilities lower their operating costs and even generate passive income, while startups benefit from compute that is both cheaper and greener. The shared value loop is what makes the model resilient. As adoption grows, more facilities join, expanding capacity for startups, which in turn strengthens the economics for hosts. Research on circular energy systems supports this logic, showing that integrating heat recovery into local energy ecosystems improves both sustainability outcomes and financial viability.
In short, WATTER doesn’t just lower compute costs; it creates a two-sided ROI that benefits both the buyer and the host. For startups, that means affordable, transparent access to GPU power. For facilities, it means eliminating one of their largest utility expenses. For both, it means joining an ecosystem that scales value as it grows.
From Buildings to the Cloud: Why Hotels Are the First Step
WATTER’s long-term opportunity is as broad as the built environment itself. Any facility that needs hot water—residential complexes, office towers, hospitals, gyms, retail/convenience stores—can become part of a distributed cloud. Each installation doubles as a source of compute power and as a utility upgrade for the occupants. The scale is enormous: millions of commercial and residential properties in the U.S. rely on central hot water systems. Capturing even a fraction of that base creates a network that is both geographically dense and economically compelling.
But every broad opportunity needs a practical starting point. For WATTER, that entry market is hotels.
Mission-Critical Reliability
Hotels rely on consistent hot water 24/7, which makes them a natural proving ground. As Narasimha Krishnakumar explains,
“For a hotel, hot water is mission-critical. If we guarantee uptime there, we can guarantee it anywhere.”
The same principle applies to WATTER’s cloud offering. Redundancy strategies ensure that even if a server fails, both the hot water system and the compute workloads continue without disruption. This dual-layer reliability addresses one of the top concerns voiced in hospitality operations as well as in cloud infrastructure adoption: uptime and continuity.
ESG and Sustainability Pressures
Hospitality is under intense pressure to demonstrate measurable ESG progress. Nearly all major hotel brands now have dedicated sustainability leadership roles and net-zero operational targets. Programs like Hilton’s LightStay and IHG’s Green Engage track energy, water, and waste performance, saving millions in utility costs.
WATTER fits naturally into this landscape. By reusing compute heat for hot water, hotels can improve their carbon and energy profiles in ways that directly contribute to sustainability certifications such as LEED or EDGE. Corporate travelers and eco-conscious guests increasingly favor LEED-certified properties, and upgrades that lower utility consumption while delivering measurable efficiency gains make it easier to achieve or maintain those standards. WATTER’s approach doesn’t just meet reporting requirements; it strengthens a hotel’s ability to align with the certifications and frameworks investors, guests, and regulators already recognize.
Infrastructure Modernization
Hotels are already investing heavily in infrastructure upgrades, with mechanical system replacement cycles averaging 7–12 years. Modernization efforts often include IoT-enabled energy management, smart HVAC, and LED retrofits. These investments are frequently tied to sustainability certifications such as LEED, which reward improvements in energy efficiency, water savings, and emissions reduction.
WATTER fits naturally into this trajectory. By integrating compute into hot water systems, facilities lower operating costs and improve their sustainability scores. At the same time, those same servers become cloud nodes, expanding local compute capacity for startups and IT teams. In practice, one upgrade delivers two benefits: modernization of building systems and expansion of a distributed cloud network.
Financial Case for Operators
Utility costs typically account for about 3% of hotel operating revenue, with hot water making up roughly 20% of that spend. Reducing or eliminating that cost translates into immediate margin improvements for operators. Market sizing research points to a $100M near-term opportunity in the hospitality sector for compute-integrated water heating. This isn’t a long-term aspiration—it’s a near-term revenue and savings opportunity that owners and operators can measure from the first day of deployment.
For cloud users, the same infrastructure that saves facilities money also makes compute more affordable. By sharing the value created through heat reuse, WATTER can offer competitive GPU pricing to startups and enterprises. The result is a financial model where both sides benefit: facilities see day-one ROI, and developers gain cost-effective access to the compute they need to scale.
The Future Vision
Turning Building Appliances into a Distributed Cloud Platform
WATTER’s first deployments in hotels are only the beginning. The long-term vision is to create a distributed, net-zero cloud that operates across both commercial and residential infrastructure, managed as a single connected entity. As Narasimha Krishnakumar describes it, the goal is a “completely scaled distributed cloud” that feels seamless not only to developers but also to IT teams looking to deploy AI agents and applications.
Today, that means providing compute at the zip-code level—clusters of nodes embedded in local buildings. Over time, as home nodes are added, this model extends even further. Locality shifts from neighborhoods to the precise latitude and longitude of individual properties. At that stage, compute is available at the level of a single household or office, enabling ultra-low-latency AI workloads, fine-grained compliance, and applications that were impossible under centralized cloud models.
From Hotels to Residences
Hotels provide the scale and reliability to start, but the model expands naturally into residential buildings, offices, hospitals, and mixed-use facilities. Each property that installs a WATTER unit adds another node to the network. Over time, these nodes form a geographically distributed cloud that delivers compute locally while reusing heat in the same location.
Zip-Code Level Access
The advantage of this architecture is proximity. Instead of centralizing workloads in a handful of massive data centers, WATTER creates access at the neighborhood level. This unlocks new classes of applications—retail video analytics, predictive maintenance on factory floors, healthcare diagnostics—that benefit from both low latency and local compliance. For the people building on top of it, that means more than just developers. IT teams deploying AI agents and applications also gain the ability to run workloads closer to where data is created, without routing everything back to a distant region.
As the network grows, this model moves beyond zip-code clusters. Once home nodes are in place, locality becomes even more precise—down to the latitude and longitude of a single property. At that stage, compute can be targeted at the level of an individual household or building, enabling ultra-low-latency AI applications and hyper-granular data residency compliance.
Aligned With Renewable Energy
Scaling in this way also strengthens the sustainability story. Research shows that elastic, energy-proportional edge compute can dynamically align workloads with the availability of renewable energy, lowering emissions without sacrificing performance.
By embedding compute in existing utilities, WATTER turns a once-linear system into a circular one: electricity powers GPUs, GPUs heat water, and the network intelligently balances demand with green energy supply.
Resilient by Design
A distributed network is also more resilient. Geographic distribution, redundancy across nodes, and hybrid edge-cloud failover models reduce single points of failure. For developers, that means higher availability. For facilities, it means mission-critical utilities like hot water are never at risk, even if a local server goes offline.
The outcome is a fundamentally different kind of cloud: distributed, local, net-zero by design. Instead of scaling through bigger data centers, WATTER scales through the built environment. Each new unit is both a utility upgrade and a cloud node, expanding capacity while reducing environmental impact. For startups, enterprises, and facilities alike, this vision represents the next infrastructure layer: compute that isn’t hidden behind regional endpoints, but embedded in the very places where people live, work, and innovate.
The Choice Ahead
The opportunity for startups is no longer theoretical. WATTER’s compute power is already available, embedded in facilities that are running today. Early adopters can spin up workloads in minutes, test with credits, and see the performance gains for themselves.
For developers, the path is straightforward: start with containerized dev/test workloads, experience faster feedback loops and lower costs, then scale into production when ready. For facilities, the value is immediate—reduced utility bills and new revenue from infrastructure that once sat idle. For investors, the story is clear: a model where every new node expands capacity while paying back from day one.
This is a rare moment where urgency and advantage overlap. Startups that join WATTER now aren’t just saving money; they are helping shape a new category of infrastructure, one that will scale from hotels to residences into a distributed, net-zero cloud.
The choice is here: keep running workloads on distant hyperscale servers, or bring compute closer, cheaper, and greener. WATTER makes that choice possible today.
→ Join the WATTER waitlist for pilot credits. Get early access to compute that is local, affordable, and green. Be part of the first distributed net-zero cloud.
