ClimateTech & Energy Transition
ClimateTech Software Development - EV Charging, Grid Platforms, Carbon Accounting & Energy Data
ClimateTech is software with a hardware shadow and a regulator looking over its shoulder. We build the data platforms, charging networks, and carbon-accounting engines that have to be right - because someone is going to audit them.
What we hear from ClimateTech & Energy Transition teams
- EV-charging network uptime issues that cost more in driver trust than in lost revenue
- Carbon-accounting calculations done in spreadsheets that auditors won't sign off on under CSRD or SEC climate rules
- Grid / DERMS data ingestion that breaks every time the utility's API quietly changes
- IoT meter fleets with 5% silent failure rates nobody noticed until a quarterly reconciliation
- Sustainability-reporting workflows that take a finance team two weeks per quarter and produce different answers each time
- Charging-station roaming protocols (OCPI, OCPP) implemented inconsistently across vendors
Regulation & compliance we work with
CSRD (EU sustainability reporting)
SEC climate disclosure rules
GHG Protocol (Scope 1/2/3 accounting standards)
ISO 14064 / 14067 (carbon accounting)
NERC CIP (grid cybersecurity, US)
OCPP / OCPI (EV-charging protocols)
IRA + state-level US clean-energy incentive frameworks
What we deliver
EV-charging network platforms: OCPP-compliant backends, OCPI roaming, driver apps, operator dashboards
Grid / DERMS data pipelines with reconciliation, gap-filling, and audit-ready provenance
Carbon-accounting engines: GHG Protocol-aligned calculations, source-data lineage, third-party verification workflows
Sustainability-reporting platforms aligned to CSRD / SEC / ISSB disclosure standards
IoT meter / sensor data ingestion with fleet health monitoring and silent-failure detection
Climate-related risk dashboards (TCFD-aligned) for boards and finance teams
Customer-facing transparency tools (carbon receipts, charging-session breakdowns)
How we'd build it
Blueprints: example projects with the plan, the architecture and the targets we'd start from.
FAQ
- Do you have experience with OCPP / OCPI for EV charging?
- Yes. OCPP 1.6J and 2.0.1 on the station-to-CPO side, OCPI 2.2 on the CPO-to-EMSP side. We've debugged the long tail of vendor non-compliance in both directions and know which ABB / Tritium / Kempower firmware quirks to plan around. Roaming and reservation flows are where most platforms quietly fail - we test for those explicitly.
- How do you handle carbon-accounting math that has to survive an audit?
- Every calculation has source-data lineage: emission factor sources cited, inputs versioned, calculations reproducible from raw data on demand. The platform produces an evidence pack auditors can read - not a single number. This is the difference between a sustainability dashboard and an audit-ready system, and the gap is wider than most teams expect.
- Are you familiar with CSRD and SEC climate disclosure requirements?
- Yes - we treat the regulatory framework as the design spec, not as a checklist layered on at the end. Reporting boundaries, double-materiality (CSRD), scope coverage, and assurance-readiness shape the data model from day one. We don't render legal opinions on disclosure scope; that's your sustainability counsel's job - we make sure the platform can produce whatever they need.
- Can you integrate with utility / ISO data feeds?
- Yes - both legacy SCADA-style feeds and modern REST/streaming APIs. We've handled CAISO, ERCOT, PJM, and several European TSO data sources. The pattern is a normalising layer + gap-detection so the downstream platform doesn't get poisoned by an upstream outage.
Who builds it
Our own team, working from our office in East Sarajevo, Bosnia and Herzegovina. The engineers on your scoping call are the ones who build it.
Meet the team