How Oasis works.

The scale of the problem

Everything below is published, third-party data about the industry. It is not Oasis data, and none of it is modeled by us. It is here because it is the reason the project exists.

Sources are linked so you can check them. If you find one of these figures is out of date or wrong, email team@oasis.local and we will correct it.

Why a thermal module is the lever

Almost every watt a GPU draws leaves as heat, so the heat problem grows exactly as fast as the compute does. Today most sites solve it the cheapest way available: evaporate water. That works, it is well understood, and it spends a resource in precisely the regions least able to spare it — while throwing away energy that someone nearby would pay for.

The pieces of an alternative already exist and are proven separately: liquid cooling captures heat at the rack at usable temperatures, thermal storage smooths peaks, heat pumps lift recovered heat to district-heating temperatures, and dry coolers reject heat without water whenever the weather allows. What does not exist is a standard module that combines them and can be retrofitted to a site that is already running.

That is what Oasis is designing, and what the simulator estimates. Whether it is worth building is an empirical question — which is why every figure we produce is labeled as modeled, and why the model is published rather than asserted.

Honest limit: Oasis has built no hardware. The problem above is real and sourced; our proposed answer to it is, so far, a model.

What Oasis is

Oasis is an experimental research project on thermal infrastructure for AI data centers. AI clusters concentrate tens of megawatts of heat in a small footprint, and many sites reject that heat with evaporative cooling that consumes large volumes of water. Oasis explores a different loop: capture the heat at the rack, store it, and either reuse it or reject it without evaporation.

• Oasis System 001: a modular thermal-management design with five modules.
• The simulator: a server-side thermal model anyone can run to compare a baseline site with the same site using Oasis.
• Research: numbered notes on the physics, the assumptions and the open questions.
• Activity: a public log of revisions, model releases, research and chain events.
• The token: OASIS on Solana. Proceeds fund the research; the Chain tab shows it factually.

Concept stage

System 001 is a concept with a working model. No Oasis hardware is operating in any data center. The dashboard banner says so on every screen, and every performance figure carries a MODELED, SIMULATION or CONCEPT DATA tag.

The thermal loop

Heat leaves the IT load through a liquid loop, enters a thermal buffer, and is then dispatched: to heat recovery when there is a use for it, or to dry heat rejection when there isn’t. The cooled fluid returns to the racks. A control layer sits over the loop and sets where each megawatt goes.

The System tab draws this loop and lists the current revision of each module, with a history of revisions (REV 0.1, 0.2, ...).

The five modules

Revisions

The design changes through numbered revisions. Each revision has a title and notes, and publishing one is logged in the activity feed as a SYSTEM event. The current revision appears in the status labels at the top of every dashboard screen.

How the simulator works

1. 01
   Describe a site

   IT load, outdoor temperature (°C or °F), humidity, baseline WUE, the existing cooling architecture, buffer size and whether heat recovery is on.

2. 02
   Run the model

   Inputs go to the Oasis API. The model runs on the server; the page contains no formulas.

3. 03
   Read the comparison

   A baseline using your cooling architecture versus the same site with Oasis: water, cooling power, heat rejected, heat captured and recovered, buffer utilization.

4. 04
   Share it

   Each result gets an ID like SIM-8F3K2Q and a link that reloads the same result with the model version that produced it.

Temperatures entered in °F are converted to °C before they are sent. The server validates every input and returns field-level messages when something is out of range.

Inputs and bounds

Limits of the model

• It is steady-state: one operating point, not hourly weather or a year of load profiles.
• Equipment efficiencies and approach temperatures are generic assumptions, listed with every result.
• Heat recovery assumes there is a use for the heat; finding one is a site question the model can’t answer.
• Annual figures scale the operating point to a year. Real sites vary with season and utilization.

Results are estimates for comparing ideas, not engineering values. Every result shows SIMULATION, the model version and a disclaimer.

The research process

Research notes are numbered in order (R-001, R-002, ...) and filed under one category: Thermal systems, Water, Heat recovery, AI infrastructure, Modeling, Prototypes or System notes. Each states its question, method, assumptions and result, and links the model version it used when it cites simulator output.

Publishing a note logs a RESEARCH event in the activity feed. Notes can be revised; the update date is shown at the bottom of each post.

The activity feed

Where the numbers come from

Overview statistics come from the most recent simulation, or from a reference scenario when none has been run; the page says which. Chain facts are read from Solana and cached briefly. Market figures are third-party and shown with their source and time.

What the token funds

Proceeds from the OASIS token fund Oasis’s research: the thermal modeling, the prototype work behind the five modules, and the research notes published on this site. That is the token’s purpose — it pays for the work.

The token funds the work and is not an investment product. It carries no ownership of, revenue from or claim on any Oasis infrastructure, and no return of any kind is offered or implied. There is no price ticker and no buy button in the app.

Because Oasis is concept stage, the research it funds is modeling and prototype work, not the operation of a data center. Progress is published as research notes and in the activity log, so the work the token pays for can be read as it happens.

The token’s role

The OASIS token lives on Solana. The Chain tab shows factual information only: network, mint address, total supply, mint and freeze authorities (shown as “Revoked” when they are), recent transfers and network health.

There is no price ticker and no buy button in the app. Holding OASIS gives no ownership of, revenue from or claim on any Oasis infrastructure.

Before the mint is published

Until a mint address is set, the Chain tab shows “Token details will appear once the mint is published” and network facts only.

A tour of the dashboard

Connecting a wallet (optional)

Any Wallet Standard Solana wallet works: Phantom, Solflare, Backpack and others. Connecting is read-only: it shows your OASIS balance and transfers. Oasis never asks you to sign a transaction or a message.

Frequently asked questions