Softwr

Energy · head to head

Cognite Data Fusion vs Landis+Gyr Gridstream

Cognite Data Fusion logo

Cognite Data Fusion

Energy

Industrial data platform that contextualises OT, IT and engineering data into an asset-centric knowledge graph

From
On request
Rated
-
Full reviewWebsite
Landis+Gyr Gridstream logo

Landis+Gyr Gridstream

Energy

Advanced metering infrastructure and grid edge intelligence

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Cognite Data Fusion the platform is only as good as the contextualisation work, and that mapping effort is a consulting project that regularly costs more than the first-year subscription.; Landis+Gyr Gridstream the platform depends on Landis+Gyr metering hardware, including electric, gas and water meters plus communication network devices, rather than being sold as software alone
  • They diverge on capability: Cognite Data Fusion covers Asset-centric data model, Landis+Gyr Gridstream covers Advanced metering infrastructure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Cognite Data Fusion and Landis+Gyr Gridstream actually diverge.

Attributes where Cognite Data Fusion and Landis+Gyr Gridstream differ
AttributeCognite Data FusionLandis+Gyr Gridstream
PlatformsWeb, CloudWeb, Api
FoundedUnknown1896

Identical on both: starting price (On request), pricing model (quote), free tier (No), user rating (Not yet rated), category (Energy).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cognite Data Fusion

  • Asset-centric data model
  • Entity matching
  • P&ID parsing
  • 3D contextualisation
  • Cognite Atlas AI
  • Data workflows
  • Open SDKs
  • Extractors

Only in Landis+Gyr Gridstream

  • Advanced metering infrastructure
  • Real-time meter data
  • Grid edge analytics
  • Distribution automation
  • Outage detection
  • Voltage monitoring
  • Load profiling
  • Remote connect/disconnect

What people use each for

The jobs each tool is most often brought in to do.

Cognite Data Fusion

  • An operator that wants engineers to find the drawing, the sensor trend and the last work order for a valve from one searchnot Landis+Gyr Gridstream
  • A company standardising asset data across sites so an analytics team can build once and deploy to many plantsnot Landis+Gyr Gridstream
  • An upstream operator building a production-optimisation model that needs sensor data joined to equipment metadatanot Landis+Gyr Gridstream
  • A team replacing a stalled internal data-lake project where nobody could reconstruct what the tag names meantnot Landis+Gyr Gridstream

Landis+Gyr Gridstream

  • Advanced metering infrastructure for electricity, gas and water utilitiesnot Cognite Data Fusion
  • Edge device connectivity and orchestration through the Gridstream Connect Apps Ecosystemnot Cognite Data Fusion
  • Coordinating distributed energy resources to balance grid supply and demandnot Cognite Data Fusion
  • Energy performance monitoring and analysis for utilitiesnot Cognite Data Fusion

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cognite Data Fusion

  • The platform is only as good as the contextualisation work, and that mapping effort is a consulting project that regularly costs more than the first-year subscription.
  • Pricing is consumption-based and unpublished, so costs move with data volume and usage patterns you cannot forecast well until a year in.
  • It does not replace your historian, your ERP or your maintenance system, so Cognite is an additional recurring cost layered on systems you still pay for.
  • The reference base and data model lean heavily towards Norwegian and wider oil, gas and process industries; discrete manufacturing fit is weaker and the local partner network thinner outside energy.
  • Getting value out requires in-house Python and data engineering skill; organisations without a data team end up dependent on Cognite professional services for every new use case.

Landis+Gyr Gridstream

  • The platform depends on Landis+Gyr metering hardware, including electric, gas and water meters plus communication network devices, rather than being sold as software alone
  • No price, licensing model or subscription term is published on the solutions pages; the site offers only a contact form and a distributor finder
  • Deployment, integration and ongoing optimisation are sold as separate Lifecycle Services rather than included

Pricing, plan by plan

Cognite Data Fusion

On request
  • Cognite Data Fusion$undefined/year
    • Consumption-based pricing on data volume, compute and users
    • Available through cloud marketplaces with private offers
    • Contextualisation and onboarding quoted as a separate engagement

Landis+Gyr Gridstream

On request

No published plan breakdown. See the Landis+Gyr Gridstream review.

Which should you pick?

Choose Cognite Data Fusion if

  • You need asset-centric data model.
  • You work on Web, Cloud.
  • You also want entity matching.
Cognite Data Fusion review

Choose Landis+Gyr Gridstream if

  • You need advanced metering infrastructure.
  • You work on Web, Api.
  • You also want real-time meter data.
Landis+Gyr Gridstream review

Questions people ask

Is Cognite Data Fusion or Landis+Gyr Gridstream better?
Neither clearly leads. Cognite Data Fusion starts at On request and Landis+Gyr Gridstream at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cognite Data Fusion or Landis+Gyr Gridstream?
Cognite Data Fusion starts at On request and Landis+Gyr Gridstream at On request.
Does Cognite Data Fusion or Landis+Gyr Gridstream run on more platforms?
Cognite Data Fusion runs on Web, Cloud. Landis+Gyr Gridstream runs on Web, Api.
What is Cognite Data Fusion best used for?
Cognite Data Fusion is most often used for an operator that wants engineers to find the drawing, the sensor trend and the last work order for a valve from one search, a company standardising asset data across sites so an analytics team can build once and deploy to many plants, an upstream operator building a production-optimisation model that needs sensor data joined to equipment metadata, a team replacing a stalled internal data-lake project where nobody could reconstruct what the tag names meant. Of those, an operator that wants engineers to find the drawing, the sensor trend and the last work order for a valve from one search and a company standardising asset data across sites so an analytics team can build once and deploy to many plants are not what Landis+Gyr Gridstream is typically brought in for.
What can Cognite Data Fusion do that Landis+Gyr Gridstream cannot?
Cognite Data Fusion covers Asset-centric data model, Entity matching, P&ID parsing, 3D contextualisation. Landis+Gyr Gridstream covers Advanced metering infrastructure, Real-time meter data, Grid edge analytics, Distribution automation.

Answered from the vendors’ own pages

Cognite Data Fusion: Is Cognite a historian?

No. It reads from historians such as PI System and adds context. You still need the historian underneath.

Landis+Gyr Gridstream: How much does Landis+Gyr GridStream cost?

Landis+Gyr does not publish pricing on their website. Contact Landis+Gyr directly through their contact forms, reach out to a local distributor, or contact their sales team for pricing information.

Source
Cognite Data Fusion: How is it priced?

Consumption-based on data, compute and users, quoted per customer. Nothing is published.

Landis+Gyr Gridstream: How do I request Landis+Gyr pricing?

Use the website contact form, reach out to a local distributor, log in as an existing customer, or contact Landis+Gyr sales directly for pricing details.

Source
Cognite Data Fusion: How long does a deployment take?

First useful graph in a few months is realistic; full plant contextualisation across a site is typically a year or more.

Cognite Data Fusion: Can we do the contextualisation ourselves?

Technically yes, the SDKs and matching tools are open, but most customers use Cognite or a partner for the first site.

Share

Related pages

More on Cognite Data Fusion

More on Landis+Gyr Gridstream

Keep looking

Other head to heads