What’s new

What changed in each release of the app, newest first. This is version

1.0.5.

After a new release, the projects home shows a short notice that links to this page: “New in 1.0.5 — see what changed”. Got it puts it away for your account, in every workspace you belong to, until the next release. Every file the app exports names the version that made it: on a workbook’s Cover sheet, and under a report’s title.

1.0.5 — 2026-11-12

• The shipped site is named after no place. The typical-year site that comes with the app is now “Coastal site (typical year)”, with no country and no coordinates; its datasets and its file follow. Projects that use it keep their link and their figures, but a result stored before this release reads “design changed” until you solve again. Nothing else that ships with the app names a town, a country or a region any more.

1.0.4 — 2026-11-12

• Hydrogen is never lost in the hour-by-hour engines. In prefeasibility’s hour-by-hour mode and in the rule-based feasibility engine, the electrolyser could make hydrogen that the plant could neither use nor store once the buffer was full, and that hydrogen was dropped without being counted. Now the units that use hydrogen are served before the electrolyser, the electrolyser makes only what they and the buffer can take, the power it does not use counts as curtailed, and the balance is checked every hour and over the year. Figures change: hour-by-hour prefeasibility results move most (the example ammonia plant goes from 60,103 to 95,373 t/yr and from 1,383 to 872 $/t, and a bigger electrolyser no longer makes less product); rule-based feasibility results move a little (hydrogen made and curtailment; on the example the product and its cost are unchanged). Right-size and the cost landscape follow the engine. Stored results keep their old figures until you solve again. See How prefeasibility works.
• The cockpit’s curtailment note names both causes of curtailed energy: peaks above the electrolyser’s size, and hours when the units and the hydrogen buffer are full.
• The method pages say what the engines bracket: a run with no look-ahead and the optimiser with foresight bracket how the plant runs hour by hour; the annual screening rests on the curtailment floor you assume and can land on either side.

1.0.3 — 2026-11-12

• Solves wait their turn when the server is busy. At most two heavy runs (the solver, the optimizer, the Design lab’s searches) run at once; a run that has to wait says Queued · N ahead, then Solving…, in the design panel, the toast and the saved-runs list, and starts on its own when a worker is free. A one-year rule-based solve never waits. Stopping a queued run takes it out of the line. See Feasibility suite.
• Run it with Docker. One container image, written for a server behind a proxy and for a computer of your own, with the data in a folder you choose and the database migrated on start; its first build is pending. See Run with Docker.
• The Resources tab reads its own numbers. The sentence about wind and solar now follows the correlation card (the same reading from the same number), says when mixing the two does not steady the output, and each series states how it was made — synthetic, shipped with the app, measured, or imported — never a word typed by hand.
• Pages read on their own. The in-app pages now cite dates and feature names where they referred to internal records.

1.0.2 — 2026-11-11

• Example projects to start from. Two examples ship with the app — an ammonia export plant on the coastal site’s typical year, and a multi-product plant (e-methanol, ammonia, hydrogen export) on the reference site. From the empty projects home or the New project panel, Make a copy gives you your own copy, opened in its cockpit and ready to solve. See Examples.

1.0.1 — 2026-11-11

• Bring your own hourly data. Fill in a Timeseries workbook — the empty template, or a site you exported — and import it as a new site of your workspace. Before anything is saved, a preview shows every check the file went through and the figures it holds. Any site can also be exported as a Timeseries workbook. See Documents.
• An activity log. Who did what, and when, for the admins of a workspace, in Settings → Workspace. Filter it, and export it as CSV. Entries are kept in full for twelve months, then as monthly counts. See Activity log.
• The reference site. The 30-year resource site that comes with the app is now called “Reference site (30-year, synthetic)”.
• The Design lab. Its tools come in a new order. The production target is now a promise you set in the Reliability tab; Find a design and Least cost (LP) ask for it.
• Members. In a workspace’s members list, the app’s super admin’s role, and whether they stay a member, are theirs alone to change.

1.0.0 — 2026-11-10 — the first release

The first release. Prefeasibility, with an annual and an hourly engine, and feasibility, with a rule-based engine and a solver, for green hydrogen and its products — one product or several in one plant. Each project keeps its assumption book, with versions and snapshots. Every file the app exports follows one standard and carries a stamp that says which project, stage, assumptions and design made it. Sign-in with your own password; workspaces with roles (viewer, editor, admin), members and one-time invitation links; sharing the app with colleagues on the office network. And the Excel package: the feasibility stage as a standalone Excel edition, for a colleague who runs it on a computer without the app.