Softwr

Manufacturing · head to head

Authentise vs GENESIS Version 11

Authentise logo

Authentise

Manufacturing

Modular MES and workflow automation for additive manufacturing, with ITAR-capable deployment options

From
On request
Rated
-
GENESIS Version 11 logo

GENESIS Version 11

Manufacturing

Iconics SCADA and visualisation under Mitsubishi Electric, now sold with unlimited tag licensing

From
On request
Rated
-

The short version

  • Each has a real cost: Authentise nothing is published about price, and modular licensing means the quoted entry module rarely resembles the cost of a configuration that actually runs a production floor.; GENESIS Version 11 the name has changed twice, from GENESIS64 to GENESIS Version 11 with an Iconics-to-Mitsubishi ownership shift, so documentation, forum answers and integrator experience are split across three product identities.
  • They diverge on capability: Authentise covers Additive workflow automation, GENESIS Version 11 covers Unlimited tag licensing.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Authentise and GENESIS Version 11 actually diverge.

Attributes where Authentise and GENESIS Version 11 differ
AttributeAuthentiseGENESIS Version 11
PlatformsWeb, APIWindows, Web, iOS, Android

Identical on both: starting price (On request), pricing model (quote), 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 Authentise

  • Additive workflow automation
  • Machine data capture
  • Traceability
  • Modular deployment
  • ITAR-capable hosting
  • Scheduling

Only in GENESIS Version 11

  • Unlimited tag licensing
  • GraphWorX
  • Hyper Historian
  • AnalytiX
  • Web and mobile clients
  • BACnet and building protocols
  • Alarm and notification
  • Energy AnalytiX

What people use each for

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

Authentise

  • An additive service bureau tracking jobs across a mixed fleet of printers from several vendorsnot GENESIS Version 11
  • An aerospace supplier that needs powder batch to part traceability as qualification evidencenot GENESIS Version 11
  • A defence programme requiring export-controlled geometry handled under ITAR-compliant hostingnot GENESIS Version 11
  • A corporate additive team standardising build preparation and post-processing steps across sitesnot GENESIS Version 11

GENESIS Version 11

  • A university or hospital estate adding buildings every year that no longer wants a licence negotiation for each expansionnot Authentise
  • A data centre operator needing power and cooling status overlaid on a 3D floor model rather than a line diagramnot Authentise
  • A water utility wanting pump station status on a GIS map alongside historised flow and pressure datanot Authentise
  • A Mitsubishi Electric factory automation site wanting supervisory visualisation from the same vendor as the controllersnot Authentise

Where each one falls short

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

Authentise

  • Nothing is published about price, and modular licensing means the quoted entry module rarely resembles the cost of a configuration that actually runs a production floor.
  • It is additive-specific, so a shop with significant machining, casting or fabrication work still needs a second MES and an integration between them.
  • The ITAR-capable deployment that justifies the price is irrelevant to purely commercial shops, which then find the system expensive relative to general manufacturing software.
  • Integrating with the ERP and PLM systems that already hold part and order data is project work, and the burden falls on a small vendor rather than a large systems integrator ecosystem.
  • Company scale is modest against the industrial software incumbents, which is a real consideration for a system sitting in the traceability path of qualified aerospace parts.

GENESIS Version 11

  • The name has changed twice, from GENESIS64 to GENESIS Version 11 with an Iconics-to-Mitsubishi ownership shift, so documentation, forum answers and integrator experience are split across three product identities.
  • Unlimited licensing sets a high floor: a small site with a few hundred points pays for capacity it cannot use, and tag-priced competitors remain cheaper below a few thousand points.
  • It is a Windows and Microsoft-stack product, depending on SQL Server and Windows services, so Linux-first or containerised deployment strategies do not apply to it.
  • Mitsubishi Electric now owns it outright, and roadmap priorities follow that group’s factory automation strategy rather than the independent building-automation direction Iconics previously set.
  • The 3D and GIS visualisation that distinguishes it takes real modelling effort to populate, and estates that skip that work end up with an expensive licence driving conventional 2D screens.

Pricing, plan by plan

Authentise

On request
  • Authentise Flows and MES modules$undefined/year
    • Modular licensing by function
    • Public cloud, private SaaS or ITAR-compliant deployment
    • Machine data capture and traceability

GENESIS Version 11

On request
  • GENESIS Version 11$undefined/year
    • Unlimited tags, users and connected devices within a licence
    • Licensed by product module rather than by point count
    • Sold and configured through Mitsubishi Electric and Iconics system integrators

Which should you pick?

Choose Authentise if

  • You need additive workflow automation.
  • You work on Web, API.
  • You also want machine data capture.

Choose GENESIS Version 11 if

  • You need unlimited tag licensing.
  • You work on Windows, Web, iOS, Android.
  • You also want graphworx.

Questions people ask

Is Authentise or GENESIS Version 11 better?
Neither clearly leads. Authentise starts at On request and GENESIS Version 11 at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Authentise or GENESIS Version 11?
Authentise starts at On request and GENESIS Version 11 at On request.
Does Authentise or GENESIS Version 11 run on more platforms?
Authentise runs on Web, API. GENESIS Version 11 runs on Windows, Web, iOS, Android.
What is Authentise best used for?
Authentise is most often used for an additive service bureau tracking jobs across a mixed fleet of printers from several vendors, an aerospace supplier that needs powder batch to part traceability as qualification evidence, a defence programme requiring export-controlled geometry handled under itar-compliant hosting, a corporate additive team standardising build preparation and post-processing steps across sites. Of those, an additive service bureau tracking jobs across a mixed fleet of printers from several vendors and an aerospace supplier that needs powder batch to part traceability as qualification evidence are not what GENESIS Version 11 is typically brought in for.
What can Authentise do that GENESIS Version 11 cannot?
Authentise covers Additive workflow automation, Machine data capture, Traceability, Modular deployment. GENESIS Version 11 covers Unlimited tag licensing, GraphWorX, Hyper Historian, AnalytiX.

Answered from the vendors’ own pages

Authentise: How is Authentise priced?

It is not published. Licensing is modular and quoted annually, with integration and onboarding priced separately.

GENESIS Version 11: Is GENESIS64 discontinued?

It has been superseded. GENESIS Version 11 is the current release and the name GENESIS64 is retired.

Authentise: Can it handle ITAR-controlled work?

Yes. It offers ITAR-compliant deployment alongside public cloud and private SaaS, which is a primary reason defence suppliers choose it.

GENESIS Version 11: Does version 11 really have no tag limits?

Yes, tag, user and device counting was removed in version 11. Licensing is by module instead.

Authentise: Does it work with printers from more than one manufacturer?

Yes. It is designed for mixed fleets and captures machine data across vendors, which single-vendor software will not do.

GENESIS Version 11: Who owns Iconics now?

Mitsubishi Electric, which took full ownership. Iconics continues to operate under its own name from Massachusetts.

Authentise: Is it a full MES for a general machine shop?

No. It is built around additive workflows; subtractive-heavy shops need a general MES as well.

GENESIS Version 11: Can it act as a building management system on its own?

It is the supervisory and analytics layer. It reads BACnet and building controllers but does not replace field-level plant controllers.

Share

Related pages

Other head to heads