Kraken vs S/4HANA Utilities vs Oracle: an independent comparison

The three, honestly characterised

SAP S/4HANA Utilities is the successor to IS U and the path of least procurement resistance for SAP estates facing the 2027 maintenance deadline. Its strength is depth: decades of utility process coverage, strong regulatory localisation, and an enormous skills market. Its weakness is that it largely preserves how you operate today, at SAP cost, through an implementation that is a full reimplementation in all but name.

Oracle’s utility stack, customer care and billing, is the established alternative in the same mould: proven at scale, deeply featured, integrator delivered, and operationally similar to SAP in what it asks of you. Choosing between SAP and Oracle is largely choosing between ecosystems, not operating models.

Kraken is the different animal. Built by Octopus to run its own retail business and now licensed to others, including EDF and National Grid in the US, it is less a billing system than an operating model with software attached: customer centred, highly automated, designed for a dramatically lower cost to serve. The licence model replaces the build. The catch is symmetrical: you must actually adopt the ways of working it assumes, because a Kraken run like an SAP estate delivers the worst of both, and you accept a younger platform with a shorter track record outside energy retail.

The comparison that actually matters

Feature grids will not decide this well, because all three bill accurately when implemented well. Decide on four questions instead. Operating model: do you want to transform how you serve customers, or preserve it? Kraken forces the former; SAP and Oracle permit the latter. Cost profile: capital project plus licence maintenance, or an ongoing platform fee tied to accounts served? Control: SAP and Oracle estates are yours to customise and burden; Kraken is deliberately standard, which is a discipline as much as a constraint. And risk: mature platform with a migration you control, or a newer platform with a migration partly shaped by the licensor’s playbook?

The three side by side

Comparing more than these three? See our independent utility platform selection hub, covering Kraken, Kaluza, SAP, Oracle, Gentrack and Salesforce side by side.

What delivery experience adds

Whichever you pick, the migration is where the risk lives, and the disciplines are identical: data first, rationalise before you move, a controlled staged migration, reconcile everything, prepare the operation. Our guide to migrating a utility billing system covers them, and the SAP specific decision is covered in the 2027 and 2030 decision facing UK and Irish utilities. The platform choice sets which risks you carry; it does not remove the need to carry them well.

We have carried these migrations across all three kinds of estate. We led the first ever migration of a water utility onto Kraken and recovered it after it had fallen twelve months behind; for a major energy supplier we root caused and recovered a billing imbalance of more than £160 million that had emerged after a Kraken migration; for a UK utility we ran the discovery, negotiated the commercial terms and delivered 65 days ahead of plan; and as Kraken has moved into telecoms we have delivered a major telecoms operator onto the platform. We are independent, so that experience is pointed at your decision, not at selling you a platform. See Kraken migration consulting.

This is no longer only an energy decision

Kraken began in energy retail, but it is not staying there. It already runs water, and it is moving into broadband and telecoms, having licensed its first broadband provider and put a former BT chief executive in charge of the Kraken arm. SAP and Oracle sell utility specific stacks, but the same question, transform the operating model or preserve it, is now arriving for water companies and telecoms operators too.

The migration discipline does not change with the sector. Live customer and billing data still has to move cleanly, the cutover still has to be rehearsed for real, and someone independent still has to hold the platform and the integrator to account. Our experience already spans energy, water and telecoms, so we weigh the platform against your data and your operating ambition, whatever market you are in.

We cover this wherever Kraken lands: see our water and telecoms and broadband migration pages, or the worldwide Kraken service.

The client side view

We hold no licence to sell and no vendor commission, so our only interest is the choice that fits your data, your operating ambition and your delivery capacity. Having sat on the client side of both kinds of estate, my summary is this: choose S/4HANA or Oracle if your processes genuinely fit them and continuity is the ambition; choose Kraken if a transformed cost to serve is the ambition and you are prepared to change how you work to get it; and choose none of them until your data would survive the move. If Kraken is your choice, an independent Kraken implementation partner on your side of the table is the best protection for that data.