See the sample site.
£0 / month
For a first look at a single ledger for energy.
- Sample site and dataset
- Chart, table and SQL views
- No account needed for this demo
Energy and emissions, measured at the meter
Bring meters, fuel logs and invoices together.
See where the energy goes.
Report emissions you can defend.
Your readings already exist.
Start there.
One ledger for energy
The meter says one thing, the invoice another, and the spreadsheet a third. Emberline puts the readings in one ledger, with one definition for every number, so the site, the finance team and the auditor are looking at the same thing.
702 MWh
| Month | Electricity used |
|---|---|
| Apr 2026 | 812 MWh |
| May 2026 | 798 MWh |
| Jun 2026 | 771 MWh |
| Jul 2026 | 744 MWh |
| Aug 2026 | 730 MWh |
| Sep 2026 | 702 MWh |
SELECT month, SUM(kwh) / 1000 AS mwh
FROM meters.half_hourly
WHERE site = 'Plant 2'
AND month BETWEEN '2026-04' AND '2026-09'
GROUP BY month ORDER BY month; Built for the next question
A shared ledger for the people who read the meters and the people who have to sign the report.
See consumption by site, meter and shift. Tie it to production so a busy month and a wasteful month stop looking the same.
Reconcile metered use against every utility invoice, line by line, and find the bill that charged for energy nobody used.
Spot the compressor left running over the weekend, and the boiler that drifted out of tune, before the month-end number does.
Scope 1 and 2 totals built from the meter up, with the emission factor, its year and its source recorded against every figure.
Keep the path from a raw reading
to a reported tonne short.
Half-hourly meters, SCADA exports, delivery notes and the spreadsheet someone still keeps by hand.
Every invoice checked against what the meters recorded, with the gap shown rather than hidden.
Totals that trace back to the meter, with the emission factor and its year on the record.
Fits the site you already run
Keep the systems that run the plant. Bring their readings somewhere they can be compared, reconciled and reported.
How sources would connectHalf-hourly electricity · Gas · Water
SCADA exports · Building management · Historians
Utility invoices · Fuel delivery notes
CSV · Excel · Shared drives
Every total opens onto the readings that made it, and when each one arrived.
Emission factors are versioned with the year they apply to, so last year’s report still adds up next year.
Sources, assumptions and adjustments travel with the figure instead of living in someone’s inbox.
Illustrative plans for a
fictional product.
£0 / month
For a first look at a single ledger for energy.
£249 / month
A concept plan for a single operating site.
Let’s talk.
A concept plan for operators with several sites.
No. It is a fictional energy and emissions product, made up for this page. The explorer uses a fixed synthetic dataset; nothing connects to a real meter or site.
No. Consumption, emissions, prices and the site itself are illustrative. They are there so the product can explain itself, not to claim a result.
The design system this page follows specifies them, so the page loads nothing extra and needs no font licence. The serif and the monospace still do the work of separating the story from the data.
Yann Hamonou, in Astro, with hand-written CSS and one small script for the explorer, the menu and the plan previews. No page builder, no plugins.
Yes. Book the free 30-minute review and bring the product. We start with what the page has to prove, and to whom.
A concept by Yann Hamonou.