Who we are bringing ROSE to first: a public record

There is a version of an early-stage compute-infrastructure launch that keeps everything quiet, cultivates one or two lighthouse names, and hopes to convert a signed press release six months later. ROSE is not running that playbook.

The bet is simple: distributed compute on the building envelope is a market that will be defined by which sectors adopt first, in what order, and with what public posture. Being open about which conversations are underway is a feature of that market position, not a leak from it. This post is a public record of the sectors ROSE is currently in the room with, as of August 13, 2026. Not names. Not counts. Just the sector list, so the market knows the conversation is happening.

The sector list, in the order the conversation started

1. Health systems. Multi-hospital operators sizing on-premises inference footprints for imaging, ambient documentation, and clinical decision support. Data-residency and HIPAA drive the underlying urgency.
2. Hyperscale operators. Both the primary buyers (the largest names in cloud and AI training) and the tier below (regional and vertical-focused cloud operators) who are looking at distributed campus siting to relieve interconnection pressure.
3. Real-estate investment trusts. Commercial REITs with meaningful roof and façade footprint across metropolitan markets, looking at compute tenancy as a recurring-revenue asset class alongside traditional interior leases.
4. Defense primes. Sovereign compute conversations tied to DoD data-locality mandates and rapid-deployment posture on installations across the continental United States and select overseas footprints.
5. Hospitality operators. Hotel brands and independent operators with large convention-center adjacencies where guest-facing and back-of-house AI workloads are colliding with the property's power budget.
6. Insurance carriers. Carriers underwriting cyber, business-interruption, and property policies on commercial buildings, evaluating ROSE as a data-locality and resilience mitigant in their loss models.
7. Utilities. Investor-owned and municipal utilities interested in distributed compute as a load-shaping tool across their distribution footprint, both as customer-programs and as internal-asset conversations.
8. Universities. Research universities looking at campus-scale compute deployments to support internal AI research, sponsored-research workloads, and shared regional inference footprints.

"We would rather have every one of these sectors know we are in the room with their peers than run a hush-hush campaign that only surfaces after a signed contract. Public pressure and public attribution are the same thing at this stage."

Why publish the list at all

Three reasons.

First, the attribution timeline. When a health system CIO reads a compute-panel case study in eighteen months, ROSE wants the record to show that the health-systems sector conversation started in the summer of 2026, not that ROSE showed up after a competitor blazed the trail. Publishing the sector list on August 13, 2026, is a timestamped artifact of where the conversation actually began.

Second, the sector-crossing referral network. Every one of the eight sectors above has natural adjacencies to at least two of the others (health systems adjacent to insurance and utilities, REITs adjacent to hospitality and defense installations, and so on). Making the sector list public lowers the friction for a decision-maker in one sector to introduce ROSE into an adjacent conversation they are already having.

Third, honesty about the market. There is no single vertical that gets to define whether distributed compute on the building envelope becomes standard practice. It gets defined by all of these sectors moving at once, in parallel, with different constraints and different economic drivers. Publishing the list is a truer picture of where the market actually is than any single lighthouse-customer story would be.

What is on ROSE's side of the room

The architecture itself is disclosed in US provisional 64/124,031 (filed May 14, 2026): a Building-Integrated Modular Compute Surface System with coolant-neutral cassette design, deployment across roof, façade, walkway, porte-cochère, ground, in-floor reinforced, interior wall, exterior wall, and parking-deck edge surfaces, and 35 aspects across apparatus, system, method, and vendor-neutral tracks. The non-provisional is in progress. Bill Mercer III runs point on ROSE.

If you sit in one of the eight sectors above and want to be part of the early conversation, the address at the bottom of this page is the fastest way in.