Energy software development for suppliers, grids and energy services
Energy software development is building the systems behind a modern energy business: the customer portal that shows quarter-hour consumption, the platform that receives metering data from the data hub, the backend that runs a network of chargers, the tool that bids a battery's flexibility, the dashboard that watches a solar park. We build energy software for suppliers, network operators, charge point operators, aggregators and energy service companies, designed around the market's data rules and the NIS2 security duties, hosted in the EU, with the source code in your company's name.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Who we build energy software for
- Electricity and gas suppliers. Customer portals and apps, contract and switching flows, dynamic price products and the data feeds behind them.
- Distribution system operators. Metering data handling, connection requests, outage information, field work and the exchanges with the national data hub.
- Charge point operators and e-mobility services. Charging backends, payment, pricing displays, roaming and the data the rules require.
- Aggregators and flexibility providers. Platforms that pool batteries, heat pumps, chargers and industrial loads and offer them to balancing and flexibility markets.
- Producers and asset owners. Monitoring and reporting for solar, wind and storage sites, production forecasts and availability data.
- District heating, energy communities and industrial sites. Consumption and production data, sharing rules within a community, and energy management for plants and property portfolios.
What we build
- Customer portals and apps. Consumption and production per quarter hour, contracts, invoices, moving and switching, and alerts when prices or usage change.
- Metering data platforms. Receiving, validating, storing and serving meter readings and time series, with estimates and corrections tracked.
- Flexibility and demand response. Device integrations, baselines, activation, measurement of what was delivered and the reports for the market and the customer.
- EV charging backends. Charger management over OCPP, sessions, pricing, payment, roaming interfaces and the operator's view of the network.
- Forecasting. Load, price and production forecasts from your own history and weather data, measured against what actually happened.
- Field and asset work. Mobile apps for inspections, meter work and maintenance, connected to the asset register and the work order system.
- Integrations. Billing and customer systems, data hubs, market platforms, weather and price feeds, and the historians of operational systems.
Fifteen-minute data is the new normal
Energy markets in Europe used to think in hours. The EU guideline on electricity balancing, Regulation (EU) 2017/2195, Article 53, required transmission system operators to apply a 15-minute imbalance settlement period, and Nord Pool's page on the transition (read 11 November 2026) gives 30 September 2025 as the European go-live of 15-minute market time units in the day-ahead market. The Electricity Directive, Directive (EU) 2019/944, Article 20(g), requires smart metering systems to let customers be metered and settled at the same resolution as the imbalance settlement period.
For software this is concrete. Time series are stored per quarter hour, which is 96 values a normal day, 92 on the day clocks go forward and 100 on the day they go back. Forecasts, prices, settlement, invoices and the charts customers see all have to agree on the same intervals and time zone rules. Systems built for hourly data need their data model, their storage and their screens reworked, and that work is often the first project.
Metering data and the rules on access
The Electricity Directive gives customers rights to their own data that the software has to deliver. Article 20(a) requires validated historical consumption data and non-validated near real-time data to be available at no extra cost, through a standardised interface or remote access. Article 20(e) lets customers have their consumption and feed-in data sent to a third party acting for them. Article 23 requires the parties managing data to give eligible parties access on non-discriminatory terms, and Article 12 requires the technical process of switching supplier to take no longer than 24 hours by 2026.
How data moves is set nationally, inside a common frame. Implementing Regulation (EU) 2023/1162 sets a reference model for access to metering and consumption data, with roles such as the metered data administrator, the metering point administrator, the data access provider and the permission administrator, and terminology aligned with the Harmonised Electricity Market Role Model and the IEC Common Information Model. In several countries a central data hub sits in the middle. Fingrid's Datahub page (read 11 November 2026) describes the Finnish one as holding information on around 4 million electricity points of use and used by about 80 distribution system operators, 80 suppliers and 60 service providers. We build to the national message formats and test environments of the hub you connect to.
Meter data is personal data when it belongs to a household. The GDPR applies, and the recitals of Regulation 2023/1162 point out that smart meters are terminal equipment, so the ePrivacy rules on accessing information on a device apply too. Consent, purpose and retention are designed into the data model, not added to the privacy notice afterwards.
EV charging software and the AFIR rules
The Alternative Fuels Infrastructure Regulation, Regulation (EU) 2023/1804, puts specific duties on charge point operators, and most of them land in the backend:
- Ad hoc charging. Under Article 5(1), public charging points deployed from 13 April 2024 must accept a widely used payment instrument through a card reader or a contactless device, or below 50 kW a secure internet-based method such as a QR code. From 1 January 2027 points of 50 kW or more on the TEN-T road network must have a card reader or contactless device, including those built before 2024.
- Prices. Article 5(4) bases the ad hoc price at 50 kW or more on the price per kWh, with an optional occupancy fee per minute, shown before the session starts.
- Connected and smart. Article 5(7) required every public point to be digitally connected by 14 October 2024, and Article 5(8) requires points built after 13 April 2024 or renovated after 14 October 2024 to be capable of smart recharging.
- Data. Article 20 requires static and dynamic data on public points, such as location, connectors and availability, to be made available at no cost from 14 April 2025.
Chargers talk to the backend over the Open Charge Point Protocol. The Open Charge Alliance (read 11 November 2026) lists OCPP 1.6 from 2015 as still widely used, OCPP 2.0.1 from 2020, approved as the IEC 63584 standard in 2024, and OCPP 2.1 from 2025. A new backend usually supports both generations.
Security: NIS2, operational systems and AI
The NIS2 Directive, Directive (EU) 2022/2555, lists energy among the sectors of high criticality: electricity suppliers, distribution and transmission system operators, producers, nominated market operators, aggregation, demand response and storage providers, charge point operators, district heating and cooling, oil, gas and hydrogen. Covered companies must manage cybersecurity risk, including in their supply chain, and under Article 23 report significant incidents with an early warning within 24 hours, a notification within 72 hours and a final report within a month. Our work is set up for that: access logged and limited, dependencies tracked, vulnerabilities fixed on a schedule, and an incident contact who answers. More in our NIS2 compliance guide; for software products sold to customers, see the Cyber Resilience Act guide.
Business software stays apart from control systems. We read from SCADA and plant systems through a historian or a gateway the operator approves, and we do not build the functions that control the grid. The same line matters under the EU AI Act: AI systems used as safety components in the management and operation of electricity, gas or heating supply are high-risk under Annex III, point 2, with those obligations applying from 2 December 2027. Forecasting and advice tools that leave the decision with people are designed and documented so they stay outside that category.
Oil and gas: methane rules and operational data
For an oil and gas company, software work is increasingly driven by reporting. The EU Methane Regulation, Regulation (EU) 2024/1787 (read 11 November 2026), covers oil and fossil gas exploration and production, gas gathering and processing, transmission, distribution, underground storage and LNG terminals, and inactive and abandoned wells. As published, it required operators to submit a leak detection and repair programme for existing sites by 5 May 2025 and a first source-level emissions report by 5 August 2025, with site-level measurements reported by 5 February 2027 and by 31 May every year after. It bans routine flaring and allows venting only in defined cases, and major venting and flaring events have to be notified without delay.
Those duties mean data from many sources in one place: survey results, repair records with dates, emission factors and measurements by source and site, and the evidence behind each figure. We build the data platforms, field apps for survey and repair records, and reporting that keep that trail, reading from historians and maintenance systems rather than from control systems, as described above. As an oil and gas software company partner, we work next to your engineering and OT teams, not in place of them, and check each obligation against the current consolidated text of the regulation before it is built into a report.
Trading and market tools
Wholesale energy trading has its own rulebook, REMIT, Regulation (EU) No 1227/2011. Since its amendment by Regulation (EU) 2024/1106, Article 5a requires a market participant that trades algorithmically to have effective risk controls and trading limits, to notify its national regulator and ACER, and to keep records for five years. Bidding tools, battery optimisers and automated intraday trading built for such a participant log every parameter and order so those records exist.
Ready-made energy suite or custom software?
Large utilities run billing and customer systems such as SAP S/4HANA Utilities or Oracle Utilities, and there are many ready-made charge point management and flexibility platforms. We do not replace a working core system for its own sake. Custom software earns its place around it: a better customer experience than the suite offers, a data platform that ties systems together, a new product such as a dynamic tariff or a flexibility service, or a whole system for a smaller operator whose needs a big suite does not fit.
| Situation | Ready-made product | Custom software |
|---|---|---|
| Core billing for a large utility | Usually the right choice | Around it, not instead of it |
| Customer portal and app on top of billing | Generic, branded at best | Built around your products and data |
| A new service: dynamic tariff, flexibility, community sharing | Often not offered yet | Built and changed at your pace |
| Charging network with unusual pricing or hardware | Configured where possible | Built to your chargers and rules |
| Ownership of data and code | Licensed per user or connection | In your company's own account |
How we build it
- Map the market roles and data. Which roles your company holds, which exchanges and systems it connects to, and which rules apply.
- Scope and fixed price per phase, in writing. Each phase has a fixed scope and price, and the scope says what the first version leaves out.
- Test against the real interfaces. Data hub test environments, charger simulators and recorded time series, before anything touches production.
- Two-week rounds. A working version on a test environment every round.
- Launch and run. Monitoring, security updates and incident handling on a plan, or handover to your own team.
Related services: IoT software development for connected devices, dashboard development for operations views, API integration for connecting existing systems and security audit for a NIS2 check of what you already run.
You own it
As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your company's name, running in an EU data region. Meter and customer data stay in that region. You can keep us for maintenance, run it yourself or hand it to another team. For companies that use energy and want to measure and reduce it, see energy management software. For installers and service crews at customer sites, see field service management software. See prices.
Questions we get
What does energy software development cover?
Software for companies that produce, distribute, sell, store or manage energy: customer portals and apps, metering data platforms, flexibility and demand response tools, EV charging backends, monitoring for solar, wind and battery sites, forecasting, and the integrations between them and the market's data exchanges.
Does energy software have to handle 15-minute data?
In most of Europe, yes. The EU balancing guideline, Regulation (EU) 2017/2195, set a 15-minute imbalance settlement period, and Nord Pool reports that the European day-ahead market moved to 15-minute market time units on 30 September 2025. Metering, forecasting, settlement and customer views therefore need to store and show quarter-hour values, including the 92 and 100 quarter-hour days when clocks change.
Is an energy company subject to NIS2?
Most are. The NIS2 Directive lists energy as a sector of high criticality, covering electricity suppliers, distribution and transmission system operators, producers, market operators, aggregators and storage providers, charge point operators, district heating, oil, gas and hydrogen, generally from medium size upwards. Software suppliers are part of the supply chain those companies must secure.
Which OCPP version should a new charging backend support?
The Open Charge Alliance notes that OCPP 1.6, released in 2015, is still widely used while the industry moves to OCPP 2.x: 2.0.1 from 2020, approved as IEC 63584 in 2024, and 2.1 from 2025. A new backend usually supports 1.6 for the installed base and 2.0.1 or 2.1 for new chargers.
Do you connect to control systems such as SCADA?
We read from them, through the historian, a data gateway or the interfaces the operator approves, and keep the business software separate from the control network. We do not build safety functions that control the grid or a plant; those stay with the control system vendors and the operator's own engineering.
Who owns the software?
Your company. The source code is in a repository in your own account, and the database and hosting are in your company's name, in an EU data region.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.