Roadmap

What is in development — and what is blocking it.

Seven specified modules that are not shipped. Each one lists the foundation that already exists and the specific condition that has to clear first.

Source citedThreshold clearedDesk reviewedHuman approved

See what is built

Request a demo

Read this first

Nothing on this page is available today. These modules are specified and partially founded, not shipped, and none of them should be factored into an evaluation of what greencio can do now. Anything that works is on the platform page.

Not shipped

Seven modules, each with its blocker named

Forward Curve

Needs legal review

GPU-hour prices across standard contract lengths, with the sources and minimum market coverage shown.

Problem: Anyone underwriting a multi-year compute commitment or pricing a hedge has no term structure to anchor to. A spot price cannot price a twelve-month obligation.
What exists today: An initial model defines the sources and minimum market coverage for each contract length.
What it needs: Needs enough Compute Index history and legal review before publication.

Spread Radar

Needs data history

A recorded tape of the gap between listed capacity prices and where they actually clear.

Problem: A procurement lead negotiating capacity has list prices and broker chatter, and no way to tell a real discount from a promotion.
What exists today: Quote collection already identifies the provider, region, hardware, and price.
What it needs: Needs enough reviewed price history to show a trend rather than one snapshot.

Morning Settlement

Needs engineering

A morning summary of price moves, new signals, items for review, and decisions due today.

Problem: A pull-only console gives an analyst no reason to return at a fixed time. Commodity desks run on ritual, and we do not currently have one.
What exists today: The index, signal feed, and brief tools already provide the inputs. Scheduled delivery is not complete.
What it needs: Needs reliable scheduled delivery and tested alerts.

Decision Outcome Ledger

Needs partner usage

Link each signal, recommendation, approval, and result in one decision history.

Problem: Investment committees need to see why a decision was made and what happened next.
What exists today: The product records decisions, approvals, and specialist runs. It does not yet record realized outcomes or corrections.
What it needs: Needs decisions with resolved outcomes to score against, which means it grows with the number of decisions partners put through it.

Basis Workbench

Needs legal review

Contribute negotiated quotes under NDA; see your price benchmarked against the settle and, at panel scale, a percentile band.

Problem: Procurement negotiates blind and cannot answer whether it is paying at the fortieth or the ninetieth percentile of the market.
What exists today: Source upload and review already exist. The shared benchmark does not.
What it needs: Requires antitrust review of the information-exchange design and enforced aggregation floors before any buyer-side panel opens.

Carbon Trail

Needs legal review

Estimate Scope 2 emissions from compute load, location, and grid carbon intensity.

Problem: Reporting teams need to explain how a compute-emissions estimate was produced.
What exists today: The public API documentation describes the planned routes. The routes are not implemented.
What it needs: Needs an independent method review and permission to use the required grid data.

Time-to-Power Tracker

Needs data history

A project record that stores the predicted power date and later compares it with the actual date.

Problem: Vendors sell snapshots of project status that are never scored against outcomes, so nobody knows whose energization dates to believe.
What exists today: Early research only. The project record and outcome-tracking experience still need to be designed.
What it needs: Requires sustained ingestion and enough elapsed time for predictions to resolve. A tracker with no resolved predictions is just a list.

Questions

Why it works this way

Why are none of these in the navigation?

Because they do not exist yet. Modules only enter the Platform menu once they are built and demonstrable, so the menu stays a reliable statement of what we have, not what we intend.

See what is built

Why do some products need legal review?

Shared benchmarks and buyer-contributed pricing can raise competition and licensing questions. We will complete that review before offering those products.

Can I influence the order?

Yes, and design partners do. Several of these compound only with customer count, so what partners bring to the engagement shapes which of them becomes viable first.

Design partner program

Do you commit to dates?

No. We publish the requirement instead of a date. When a product is ready, it moves to the Platform page and appears in the changelog.

See what has shipped

Want one of these sooner?

Design partners help set priorities, and several planned products require partner data or real usage before they are useful.

Design partner program Request a demo