Roadmap¶

This page shows what we plan to ship on the H2 Stations platform over the coming months, what each update contains, and when it is expected to reach you.

Plans can change

Dates are targets, not commitments. Scope and timing may shift as we learn from beta feedback. We update this page whenever the plan changes.

How updates reach production¶

Every update is released in two stages:

Beta. The update goes live on the beta environment first. Beta is a separate test environment filled with sample data. It is not connected to production and contains no real station data, so what you see there is for trying out features, not for looking up actual stations.
Production. After the beta period, the update is promoted to production, at most four weeks after it entered beta.

At a glance¶

Update	Mainly for	Beta	Production
v1.4 and v1.5: new fuelling option and API v1.1	Everyone	Done	Live on production (June 2026, W25)
Station infrastructure editor	Operators	June 2026 (W26)	July 2026 (W29)
API v2 (import and export)	Data users, signal originators	July 2026 (W28)	July 2026 (W31)
New station cards on the public map	Drivers	July 2026 (W30)	August 2026 (W33)
Real-time data dashboards	Operators, signal originators	August 2026 (W32)	August 2026 (W34)
Extended protocol configuration	Operators	August 2026 (W33)	August 2026 (W35)
Protocol data in the Export API	Data users	August 2026 (W34)	August 2026 (W35)

Week numbers are ISO calendar weeks, for reference.

Live now: v1.4 and v1.5 (June 2026)¶

Both releases are live on production as of mid June (W25).

v1.4 focuses on the operator portal:

Operators can submit a new station directly from the portal, with an admin review step before publication.
A new completeness indicator on every station: a single four-step gradient (incomplete, publishable, AFIR compliant, complete) with per-step hints on what is still missing, visible in the portal.
Performance and reliability improvements on the public map.

v1.5 introduces the fourth fuelling option and a new API version:

The 700 bar heavy-duty fuelling option is supported end to end: station data, operator portal, public map and APIs.
Export and Import API v1.1 expose and accept the new option. The v1.1 fuelling-option identifiers move to light-duty and heavy-duty vocabulary (700ld, 350ld, 700hd, 350hd). The Export API v1.1 also exposes the complete new AFIR dataset.
Signal originators get a new v1.1 endpoint listing the stations they are authorised to send signals for.
An Export API sandbox lets prospective data users integrate end to end against realistic sample responses, with no account and no access to production data.
API v1 keeps working unchanged, but is now deprecated and receives no new features.

Station infrastructure editor¶

For operators. Beta: June 2026 (W26). Production: July 2026 (W29).

A new station layout section in the operator portal. Operators can describe the physical infrastructure of each station instead of a flat list of fuelling options:

Dispensers, nozzles and storage units as individual entities.
Connector types per nozzle, with guidance that maps them to the familiar fuelling options.
A guided, step-by-step wizard for entering the layout, with an expert fast path for those who already know their data.

This richer description is the foundation for API v2 and the upcoming map improvements. Existing station data keeps working as is, and nothing is required from operators on day one.

API v2 (import and export)¶

For data users and signal originators. Beta: July 2026 (W28). Production: July 2026 (W31).

A new major API version on both sides of the platform, designed around the real-time data requirements of the EU Alternative Fuels Infrastructure Regulation (AFIR).

Export API v2 (read):

Extended static station information based on the new infrastructure model: dispensers, nozzles, connectors and storage.
Paginated JSON endpoints with interactive OpenAPI documentation.
A DATEX II 3 profile for consumers that integrate through national access points.

Import API v2 (write):

Four real-time signal types instead of one: availability, pricing, usage, and low hydrogen warnings.
Token-based authentication and per-client rate limits for signal originators.
Backward compatibility of the new signal types, so the data format still power v1 dashboards and analysis.

API v1 and v1.1 remain available in parallel.

New station cards on the public map¶

For drivers. Beta: July 2026 (W30). Production: August 2026 (W33).

The station cards on the public map are redesigned to surface the new data:

Current fuel price, where the operator or signal originator provides it.
A low hydrogen warning, so drivers know before they arrive.
Richer station details from the new infrastructure model, such as connectors and vehicle classes served.

Real-time data dashboards¶

For operators and signal originators. Beta: August 2026 (W32). Production: August 2026 (W34).

The portal dashboards are updated for the new signal types:

Signal originators can monitor everything they send: availability, pricing, usage and low hydrogen signals, with transmission health at a glance.
Operators get a live view of their stations covering the same data, next to the existing availability history.

Extended protocol configuration¶

For operators. Beta: August 2026 (W33). Production: August 2026 (W35).

A technical extension of the station infrastructure editor. Operators can record the precise fuelling capability of each nozzle:

The governing fuelling protocol and the standard edition the station follows.
Pressure class, pre-cooling and flow characteristics.

Complete dataset is likely to evolve.

This level of detail matters to fleet operators and vehicle manufacturers who need to know exactly which vehicles a station can serve.

Protocol data in the Export API¶

For data users. Beta: August 2026 (W34). Production: August 2026 (W35).

The protocol configuration entered by operators becomes available through Export API v2. The fields are already part of the v2 format from its first release (returned as null until populated), so this update changes no response formats and requires no new API version. Existing v2 integrations simply start receiving the additional data.