How the engagement runs, what it costs, and what we need from you.
For data center developers, operators, and the teams around them. 18 August 2026.
Mālama installs sensors that sign their own readings in hardware and anchor them to a public ledger. Power, water, air, and sound. The signature is created inside a secure element at the moment of measurement, before the reading touches a network or a filesystem, using a key that cannot be extracted by anyone including us. Anyone you hand the data to can verify it independently, without trusting you and without trusting Mālama. That is the whole product. Everything below is how we deliver it.
We would rather disqualify you in the first call than in month four. Some honest filters.
Most prospects are not conveniently 12 months from groundbreaking. Four realistic entry points.
When: 12 to 24 months before ground disturbance. Why this is the strongest position: you capture a full seasonal cycle of pre-existing conditions before anything changes. Every later question about causation has an arithmetic answer. What deploys: the site baseline package. Acoustic, air, water, groundwater, meteorology. No power infrastructure, no operator network integration, no security review in the hard sense.
When: ground broken, facility not yet operating. What you still get: separation of construction impacts from operational impacts, which matters because the two are treated very differently, and construction complaints are common. You also get a pre-operational baseline, which is weaker than pre-construction but far better than nothing. What you lose: the true undisturbed reference condition. State this limitation in any report rather than papering over it.
When: equipment installed, systematic testing beginning. Why we push hard on this one: commissioning is the only window in the facility's entire life when equipment runs in isolated, controlled configurations. Chillers alone. Generators alone. Partial IT load. That produces a per-source acoustic and emissions signature that turns future source attribution into a lookup instead of an argument. Once commissioning passes, that signature cannot be recovered at any price. What deploys: everything, including the rack and grid metering.
When: any time. What you get: hourly measured Scope 2 and CFE gap, continuous water and air and acoustic monitoring, fast verifiable complaint response, and a baseline for the next expansion phase. The expansion case is often the real value here. An operator who instruments now walks into the phase two hearing with years of verified data. What you do not get: a pre-construction reference. Be honest with yourself about that.
We establish where you are in the lifecycle, what is actually contested at your site, and whether we can help. You will get a straight answer, including no. Bring whoever owns permitting, because they usually know what the real exposure is.
Desk review of the parcel, receptor locations, hydrogeology, prevailing wind, existing monitoring, and the permit conditions you are operating under or expect. A site visit if the project warrants it. Output is a written assessment of what should be monitored and why, which is useful to you whether or not you proceed.
Node placement plan, reviewed by an acoustic consultant and a hydrogeologist. We do not skip this and neither should you. Placement determines whether the resulting data is admissible and whether it answers the questions you will actually be asked. A cheap deployment in the wrong locations is worse than no deployment, because it produces a record that undermines you.
Output: placement plan, bill of materials, fixed-price proposal, and a written statement of what the deployment will and will not be able to demonstrate.
Well permitting begins immediately if groundwater is in scope. This is nearly always the critical path.
Install, calibrate against reference instruments, verify, and sign the commissioning attestations that bind each device to its surveyed position. You receive the verification instructions at this point, so you can confirm the system is doing what we say from day one.
Data flows continuously. You get the dashboard, the alerting, and the raw signed record. We review with you quarterly. If a parameter drifts outside its baseline envelope, you hear about it before anyone else does, which is the entire point.
Baseline report at the 12-month mark. Then reporting to whatever cadence your obligations require, with the underlying signed dataset and independent verification instructions attached to every report.
Deployments succeed or fail on these. Stated plainly so there are no surprises in month two.
| We need | When | Why it matters |
|---|---|---|
| Site access for assessment and install | Stages 2 and 5 | Escorted is fine |
| Parcel survey, site plan, and receptor locations | Stage 2 | Placement design |
| Existing permits and any conditions of approval | Stage 2 | Determines what must be measured |
| Any prior environmental studies | Stage 2 | We build on them rather than duplicating |
| Hydrogeologic information, if it exists | Stage 3 | Well screening depth and aquifer targeting |
| A decision on groundwater wells | Stage 3 | Longest lead item. Deferring this delays everything. |
| Network egress allowlist, three destinations | Stage 5, power metering only | Covered in the security brief |
| A named owner on your side | Throughout | The single largest predictor of whether a deployment goes well |
| Honesty about what is already contested | Stage 1 | We design around your actual risk, not a generic one |
The last one deserves emphasis. If there is already community opposition, an unresolved permit condition, or a neighbor who has been complaining for a year, tell us in the first call. It changes the design substantially, and we will find out eventually.
Realistic, not optimistic.
| Milestone | Elapsed | Note |
|---|---|---|
| Scoping call to signed contract | 6 to 11 weeks | Faster if the site is simple and you move quickly on stage 3 |
| Well permitting and drilling | 4 to 8 weeks, parallel | Critical path. Jurisdiction-dependent and occasionally much longer. |
| Installation and commissioning | 1 to 2 weeks | |
| First usable data | Day one | Though a single day of data proves little |
| Seasonally complete baseline | 12 months from install | Non-negotiable if you want a defensible baseline |
| Baseline report | +2 weeks |
Work backwards from groundbreaking. To have a seasonally complete baseline before ground disturbance, the scoping call needs to happen roughly 16 to 18 months before you break ground. That is earlier than most developers are thinking about environmental monitoring. It is the single most common reason a project gets a weaker deployment than it could have had.
A six-month baseline captures two seasons and is meaningfully better than nothing. We will tell you exactly what it does and does not support.
Pricing below is illustrative. For full scope and pricing based on your needs, book a scoping call.
| Item | Hardware and installation | Annual service |
|---|---|---|
| Acoustic node, IEC 61672 Class 1 | $7,000 to $10,000 each | $600 per node |
| Air quality node, supplemental tier | $4,500 to $7,000 each | $600 per node |
| Air quality reference anchor | Pass-through plus integration | $1,500 |
| Water node, surface and process | $9,000 to $14,000 each | $600 per node |
| Groundwater node | $3,500 to $6,000 each | $400 per node |
| Well installation, third party | $15,000 to $40,000 per well | |
| Meteorological mast | $12,000 to $20,000 | $400 |
| Site gateway | $2,500 each | $1,200 per site |
Two notes on the line items that generate the most questions. Class 1 acoustic hardware is expensive and we will not substitute Class 2. Class 2 data gets challenged, and a challenged acoustic record undermines the domains where your instrumentation genuinely is reference grade. If budget is tight, we reduce node count before we reduce class. Well drilling is a third-party pass-through at cost. We manage it; we do not mark it up.
| Item | Hardware and installation | Annual service |
|---|---|---|
| MRAA-01 rack attestation appliance | $1,500 per rack | $200 per rack |
| MGM grid meter | $1,500 per feed | $200 per feed |
Eight acoustic nodes, five air nodes plus one reference anchor, three surface water nodes, six groundwater nodes, one met mast, two gateways.
| Hardware and installation, excluding wells | $200,000 to $300,000 |
| Well installation, six wells | $90,000 to $240,000 |
| Twelve-month service | $12,000 to $18,000 |
| Total pre-construction | $300,000 to $550,000 |
Operational phase for a 1,000-rack facility adds roughly $1.5M in rack metering hardware and $200,000 per year in service, on top of the environmental network at $15,000 to $20,000 per year.
Every site is different. The scoping call is where these become real numbers.
Two ways to buy. The right one depends on where you are in the lifecycle.
You buy the hardware, we provide the service layer annually. Lower total cost over a long horizon. Appropriate for the operational phase, where the asset life matches the facility life.
Monthly fee covering hardware, installation, calibration, service, and reporting. No capital outlay, no asset on your books, and we retain responsibility for keeping every instrument in calibration.
For the pre-construction baseline, managed monitoring is usually the right structure. You are a developer, not a monitoring company. You do not want to own eight sound level meters and a calibration schedule, and if the project does not proceed you should not be holding the hardware. Illustrative managed pricing for the campus above runs $14,000 to $22,000 per month across the baseline period, with well installation handled separately as a pass-through.
The data is yours. Our terms grant us a processing license, not ownership, and prohibit resale or use in aggregate products without your written consent. If your load profile is commercially sensitive, we can aggregate before egress, coarsen the transmission interval, or run the entire pipeline inside your environment so that only the cryptographic root leaves the facility. Ask about the on-premise configuration if this matters to you.
Contract terms should be confirmed in your executed agreement rather than relied upon from this document.
| Deliverable | When |
|---|---|
| Site assessment | Stage 2 |
| Placement plan with consultant review, and a written statement of limitations | Stage 3 |
| Commissioning attestations binding each device to a surveyed position | Stage 5 |
| Verification instructions, so any third party can independently confirm the data | Stage 5 |
| Live dashboard and alerting | From install |
| Baseline report with full statistical characterization | 12 months |
| Signed raw dataset, exportable at any time | Continuous |
| Compliance exports mapped to your reporting obligations | Per your cadence |
| Complaint response packet, on request, typically within hours | As needed |
| Quarterly review | Quarterly |
That last-but-one item is worth dwelling on. A complaint arrives naming a date and a time. Today, answering it takes weeks, a consultant, and produces a contestable answer. With this system you answer the same day with signed data showing exactly what conditions were at that receptor at that moment and how they compared to baseline. Fast, verifiable, good-faith response is also the most effective thing you can do to keep a complaint from becoming a class action.
Including the ones that are awkward for us.
Have you deployed this at a data center before? Not yet. The trust architecture is live in the field on carbon measurement nodes with a public on-chain record, and the sensing instruments are established third-party hardware. But a data center pilot operator would be first, and you should price that accordingly. We would rather tell you now.
Do you have SOC 2 or ISO 27001? Not yet. Both are targets. Our security integration brief states this plainly and we expect security teams to weigh it. Requiring a penetration test as a condition of the pilot is a reasonable ask.
What if the data shows we caused the problem? Then it shows that. We will not alter it and we could not if we wanted to, which is the same property that makes it worth having. Discuss the discovery implications with your counsel early rather than late. Most operators conclude that a facility they are confident in gains far more from verifiable data than it risks.
What happens if Mālama goes away? Require a data escrow and export provision in the contract, and we will agree to it. Separately, the on-chain anchors remain independently verifiable regardless of whether we exist, which is a real structural advantage over a conventional telemetry vendor. Your historical record does not evaporate with your vendor.
Can we start smaller? Yes. The most common sensible starting point is acoustic and meteorology only, at a subset of receptors, which is the lowest cost and addresses the domain generating the most litigation. Add water and air at the next phase.
Why blockchain? Because you need a timestamp that neither you nor we can alter, and that a skeptical third party can check without access to either of our systems. That is the only function it serves here. The ledger is an implementation detail, not the product. If it is an obstacle inside your organization, note that the verification property is what matters and we are happy to have that conversation on its merits.
Can we see a reference customer? On the carbon side, yes. On the data center side, not yet. See the first question.
A scoping call, one hour, no cost, no obligation. Bring whoever owns permitting. You will leave knowing whether this is worth pursuing, including if the answer is no.
Pricing is illustrative. For full scope and pricing based on your needs, book a scoping call. The MRAA-01 rack appliance and the environmental sensing package are pre-deployment as of this writing; the underlying trust architecture is in field operation on carbon measurement nodes.