Energy Trading Apps Made with C# and .NET: 
Inside the ETRM/CTRM Stack

Allegro Horizon, one of the platforms energy companies use to manage commodity trading and risk across oil, gas, and power, runs on the Microsoft .NET stack, with C# used for customer extensibility. That single fact reshapes how most engineering leaders picture this software category. ETRM and CTRM platforms tend to get filed away as closed, proprietary systems with little room for a .NET team to work. The reality across several major vendors looks different, and it changes what a CTO can plan for when the platform license stops short of what the business actually needs.

Allegro Horizon is the easiest to confirm. Commodity Technology Advisory quotes ION's own product owner on it directly: the platform continues to use the Microsoft .NET stack, with C# reserved for customer extensibility. This reads as a built-with statement about the product itself, so there is no need to чsoften it into an extension-layer footnote.

Implementation partners work the same ground. Value Creed publishes technical content on upgrading Allegro Horizon to .NET Core, which points to real, current engineering activity around the platform rather than a legacy stack sitting untouched. For a team scoping work on Allegro, you get a sense of what a project asks for skill-wise: C# and some .NET Core migration experience. See Commodity Technology Advisory and Value Creed.

Endur works on a different pattern, and the distinction matters for anyone scoping work against it. Its native scripting layer, JVS, is Java-based. The place a C#/.NET developer actually plugs in is OpenComponents, a customization API that ships for both C# and Java. So the core and the extension layer speak different languages, and the C# opportunity lives in the second one.

Hiring signals confirm where the demand sits. A live BP Energy job posting asks candidates for demonstrable C# programming against Endur’s C# OpenComponent API. When an energy operator writes that requirement into a posting, it tells a service provider precisely what a real Endur extension project needs on the bench. Job postings turn over quickly, so the specific listing changes, but the pattern of energy companies asking for C# on Endur holds.

Beyond the two platforms that name C# outright, two others confirm the wider .NET stack without a source naming the language on its own.

Two evidence tiers, kept distinct so the copy never flattens a stack-level fact into a language-level one.

ION sits at the center of this market. Alongside Allegro, Endur, and RightAngle, it also owns TriplePoint and Aspect, all grouped under one commodities portfolio on iongroup.com. FIS and Pioneer Solutions are the other major names, with FIS listed alongside ION in Gartner’s Energy Trading and Risk Management market category.

A confirmed Microsoft stack under one of these platforms tells only part of the operational story. The rest shows up in what energy operators pay third parties to do around the license. capSpire delivers Endur support and application management services, extending OpenLink beyond core ETRM functionality. 6B sells digital engineering and interoperability services that connect Endur’s capabilities to a wider technology ecosystem. Two firms building a business on exactly this work is a strong signal that the extension and integration layer is a paid, active category, not an afterthought.

The cost picture points the same way. One industry analysis from Verified Market Research estimates consulting and customization at 20–40% of total ETRM implementation cost. That figure comes from a practitioner-tier source rather than a primary vendor, so it belongs in the argument as an attributed estimate, and even at the low end it describes a meaningful slice of any implementation budget.

Related reading: C# and .NET in Oil & Gas Software