Softwr

Manufacturing · head to head

Litmus Edge vs Materialise Magics

Litmus Edge logo

Litmus Edge

Manufacturing

Industrial edge platform that collects, normalises and forwards OT data to cloud and enterprise systems

From
$1500/month
Rated
-
Materialise Magics logo

Materialise Magics

Manufacturing

Industrial build preparation and data repair for metal and polymer additive manufacturing

From
On request
Rated
-

The short version

  • Each has a real cost: Litmus Edge pricing is by site and data point, so a large tag count at one plant can cost more than a modest tag count spread over several, which is the opposite of how most manufacturers plan a rollout.; Materialise Magics new seats and modules have been subscription only since 15 May 2024, so the perpetual purchase route is closed and existing perpetual holders are on a shrinking island.
  • They diverge on capability: Litmus Edge covers Prebuilt driver library, Materialise Magics covers Mesh repair.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Litmus Edge and Materialise Magics actually diverge.

Attributes where Litmus Edge and Materialise Magics differ
AttributeLitmus EdgeMaterialise Magics
Starting price$1500/monthOn request
Pricing modelPer site by data point countquote
PlatformsLinux, Docker, Kubernetes, Cloud, On-premiseWindows

Identical on both: free tier (No), user rating (Not yet rated), category (Manufacturing).

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 Litmus Edge

  • Prebuilt driver library
  • Unified data model
  • Litmus Edge Manager
  • Edge applications
  • Store and forward
  • Cloud and broker outputs

Only in Materialise Magics

  • Mesh repair
  • Part orientation and nesting
  • Support generation
  • Build Processors
  • Simulation module
  • Structures module
  • Reporting and traceability

What people use each for

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

Litmus Edge

  • A manufacturer with twenty plants and five PLC brands that needs one data acquisition standard rather than twenty bespoke integrationsnot Materialise Magics
  • Feeding a cloud data warehouse or lakehouse with normalised production data without asking the controls team to write cloud connectorsnot Materialise Magics
  • Retrofitting data collection onto old CNC machines and robots where the protocol support is the hard part, not the analyticsnot Materialise Magics
  • Adding local buffering and computation at sites with unreliable WAN links so cloud outages do not create gaps in production historynot Materialise Magics

Materialise Magics

  • A service bureau running several brands of metal printer that wants one preparation environment instead of five vendor slicersnot Litmus Edge
  • Repairing badly formed STL or scan-derived meshes that a machine slicer will not acceptnot Litmus Edge
  • Automating support generation on metal parts where manual support editing is the bottleneck in the processnot Litmus Edge
  • Simulating and compensating for build distortion before committing an expensive metal buildnot Litmus Edge

Where each one falls short

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

Litmus Edge

  • Pricing is by site and data point, so a large tag count at one plant can cost more than a modest tag count spread over several, which is the opposite of how most manufacturers plan a rollout.
  • The entry package sits around $1,500 per month, an awkward number for a single-site pilot given that the product is infrastructure with no visible output of its own until something downstream consumes it.
  • Litmus does no analytics, so the business case always depends on a second purchase; the platform on its own produces no result a plant manager can see.
  • Full pricing beyond the entry tier is not published and the Growth and Scale packages are quoted, so scaling costs are unknown at the point you commit to the architecture.
  • A capable controls team can approximate a single-site deployment with an open-source broker and a driver gateway for a fraction of the cost, so the value case depends entirely on how many sites you are managing centrally.

Materialise Magics

  • New seats and modules have been subscription only since 15 May 2024, so the perpetual purchase route is closed and existing perpetual holders are on a shrinking island.
  • Build Processors are licensed separately per machine family, so adding a new printer brand adds a licence line as well as capital cost, and a mixed fleet multiplies the software bill.
  • The modules that deliver the biggest labour saving, notably e-Stage automated support generation, are paid extras, so the base seat alone leaves you doing manual support work.
  • Materialise publishes no prices anywhere, and quotes vary by region and reseller, so two similar bureaus can pay materially different amounts for the same configuration.
  • It is Windows only and remains a desktop application, which sits awkwardly with the cloud direction of Materialise CO-AM and means preparation capacity is tied to specific workstations and licence seats.

Pricing, plan by plan

Litmus Edge

$1500/month
  • Foundation$1500/month
    • Entry package sized by site count and data points
    • Core driver library and edge runtime
    • Store and forward to cloud and brokers
  • Growth$undefined/month
    • Larger site and data point allowance
    • Litmus Edge Manager fleet management
    • Priced on application
  • Scale$undefined/month
    • Enterprise multi-site deployment
    • Higher data point ceilings and support tier
    • Priced on application

Materialise Magics

On request
  • Magics Essentials$undefined/year
    • Mesh repair and editing
    • Part orientation and platform placement
    • Basic support generation
  • Magics with modules$undefined/year
    • Everything in Essentials
    • e-Stage automated supports, Simulation, Structures priced individually
    • Build Processors licensed per machine family

Which should you pick?

Choose Litmus Edge if

  • You need prebuilt driver library.
  • You work on Linux, Docker, Kubernetes, Cloud, On-premise.
  • You also want unified data model.

Choose Materialise Magics if

  • You need mesh repair.
  • You work on Windows.
  • You also want part orientation and nesting.

Questions people ask

Is Litmus Edge or Materialise Magics better?
Neither clearly leads. Litmus Edge starts at $1500/month and Materialise Magics at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Litmus Edge or Materialise Magics?
Litmus Edge starts at $1500/month and Materialise Magics at On request.
Does Litmus Edge or Materialise Magics run on more platforms?
Litmus Edge runs on Linux, Docker, Kubernetes, Cloud, On-premise. Materialise Magics runs on Windows.
What is Litmus Edge best used for?
Litmus Edge is most often used for a manufacturer with twenty plants and five plc brands that needs one data acquisition standard rather than twenty bespoke integrations, feeding a cloud data warehouse or lakehouse with normalised production data without asking the controls team to write cloud connectors, retrofitting data collection onto old cnc machines and robots where the protocol support is the hard part, not the analytics, adding local buffering and computation at sites with unreliable wan links so cloud outages do not create gaps in production history. Of those, a manufacturer with twenty plants and five plc brands that needs one data acquisition standard rather than twenty bespoke integrations and feeding a cloud data warehouse or lakehouse with normalised production data without asking the controls team to write cloud connectors are not what Materialise Magics is typically brought in for.
What can Litmus Edge do that Materialise Magics cannot?
Litmus Edge covers Prebuilt driver library, Unified data model, Litmus Edge Manager, Edge applications. Materialise Magics covers Mesh repair, Part orientation and nesting, Support generation, Build Processors.

Answered from the vendors’ own pages

Litmus Edge: Does Litmus Edge do analytics or dashboards?

Only lightweight edge computation and basic visualisation. It is a data acquisition and normalisation layer; the analysis happens in whatever you send the data to.

Materialise Magics: Can I still buy a perpetual Magics licence?

No. Since 15 May 2024 Materialise sells new seats and new modules on subscription only. Existing perpetual licences continue to work but new capacity is subscription.

Litmus Edge: How is it priced?

By number of sites and number of data points, in packages. The entry package starts around $1,500 per month; larger tiers are quoted.

Materialise Magics: Do I need a separate Build Processor for each printer?

You need one per machine family, licensed separately from the Magics seat. Budget for it before you buy the printer.

Litmus Edge: Can it replace my historian?

No. It buffers and forwards but is not a long-term historian. Most deployments send data into a historian, warehouse or lakehouse.

Materialise Magics: Is Magics the same as CO-AM?

No. Magics is desktop build preparation. CO-AM is the Materialise cloud platform for AM workflow and production management, which absorbed the former Link3D product.

Litmus Edge: Does it need Litmus hardware?

No. It runs on standard industrial PCs, virtual machines or containers; there is no proprietary appliance requirement.

Materialise Magics: Does Magics slice?

It prepares and supports the build and hands off through a Build Processor, which produces the machine-ready file. The machine-specific processing lives in the Build Processor.

Share

Related pages

Other head to heads