Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes
Try free Book a demo

Product roadmap

What we are building, in the open.

Few promises, each tied to a version. Work in progress has a quarter, the next items have a half-year, ideas have no date. When something ships, it links to its release notes.

Tell us what you need Release notes
Last updated
27 October 2026
Current release
2.0.0
Cadence
A feature release every quarter, fixes in between
Review
This page is reviewed every quarter; moved items say why

Themes

Five directions, chosen on purpose.

Every item on this page belongs to one of them. If a request fits none, it waits.

  • 01

    Open standards and semantics

    Plant data should be readable by any tool without a translation layer. We build on OPC UA and CESMII i3X instead of private formats.

  • 02

    Industrial AI under control

    An AI that reads plant data is common now. One that changes nothing without a person’s approval, and shows where every value came from, is what operations can trust.

  • 03

    Connectivity where it is missing

    Proxus already reads 60+ PLC, CNC and robot families. We add a driver when real projects need it, not to grow a number.

  • 04

    Security and compliance

    Enterprise sign-in, evidence for vendor reviews and the EU Cyber Resilience Act. Security work gets dates, because customers plan around them.

  • 05

    Operations at scale

    Many sites, many gateways, few people. What the platform does must be visible, and running it must stay simple.

Now, next, later

The plan, by how sure we are.

Now is in development for the next version. Next is planned for the versions after it. Later is a direction without a date.

Now

4 items

Version 2.1 · Q1 2027

  • Security and compliance

    Single sign-on with OpenID Connect, and multi-factor sign-in

    Sign in with Microsoft Entra ID, Okta, Keycloak or any OpenID Connect provider, with roles mapped from the provider’s groups. Multi-factor sign-in for local accounts.

    Planned for 2.1

  • Open standards and semantics

    CESMII i3X 1.0 API

    The namespace, models and history of a Proxus hub through the i3X interface, checked against the i3X conformance tests, so i3X clients work without custom code.

    Planned for 2.1

  • Security and compliance

    A software bill of materials with every release

    A CycloneDX SBOM published next to every release, and a written security support period for each version, as the Cyber Resilience Act asks.

    Planned for 2.1

  • Operations at scale

    Queues and backlog in Operations Center

    Each target’s page already shows what is queued for it. Operations Center gets it for every target at once, with how long data has waited and history beyond the last hour.

    Planned for 2.1

Next

5 items

Versions 2.2 and 2.3 · H2 2027

  • Open standards and semantics

    OPC UA server

    The unified namespace as an OPC UA address space, with the platform’s certificates and roles, so SCADA, MES and historians read Proxus as an OPC UA server.

    Planned for 2.2

  • Industrial AI under control

    Root cause of an alarm

    When an alarm fires, Copilot looks at what moved first on the same machine and line, compares earlier occurrences of the alarm and how they were fixed, and writes the likely cause on the alarm. It suggests; any change still waits for your approval.

    Planned for 2.2

  • Connectivity where it is missing

    BACnet/IP driver

    Building automation and utilities next to production lines: HVAC, compressed air and energy meters in the same namespace.

    Planned for 2.2

  • Operations at scale

    Helm chart for high availability

    The Kubernetes installation as a Helm chart, with the remaining high-availability work: shared keys between hub instances and network policies.

    Planned for 2.3

  • Security and compliance

    EU Cyber Resilience Act conformity

    Technical documentation, conformity assessment and CE marking for the platform before the Act applies in full. Vulnerability handling and reporting are already in place.

    Before 11 December 2027

Later

5 items

No date yet

  • Industrial AI under control

    Model inference on edge gateways

    Run ONNX models next to the machines, on the data as it is read.

  • Operations at scale

    Edge gateway redundancy

    A standby gateway that takes over a site’s devices without losing data.

  • Operations at scale

    Maintenance work

    Breakdowns and maintenance orders raised from alarms and tracked to closure.

  • Operations at scale

    More interface languages

    German first, after English and Turkish.

  • Open standards and semantics

    Energy and emissions reporting

    Energy use per line, product and shift, ready for sustainability reporting.

The one dated commitment

EU Cyber Resilience Act, before the deadline.

Regulation sets these dates, not us, and customers plan around them. So this is the only item with a day on it.

  1. 11 September 2026

    Reporting of actively exploited vulnerabilities applies.

    In place: security.txt and a single reporting address.

  2. Version 2.1 · Q1 2027

    A software bill of materials with every release, and a written security support period.

    Planned

  3. 11 December 2027

    The Act applies in full: technical documentation, conformity assessment, CE marking.

    Committed

Recently shipped

Proof that the plan turns into releases.

  • 2.0.0 Describe a machine and Copilot sets it up: profile, tags and namespace place, saved in one approval
  • 2.0.0 Trace any device, rule or target: what it depends on and where its data goes
  • 2.0.0 Copilot that changes nothing without your approval, and an MCP server for AI tools
  • 2.0.0 Siemens Industrial Edge app, behind the device’s reverse proxy
  • 2.0.0 TLS on every connection, with a built-in certificate authority
  • 2.0.0 Permissions on namespace paths, for people and for AI tools
Read the 2.0.0 release notes

How we keep this page honest

Rules we hold ourselves to.

Few items, each with a version
At most four items are in development at a time. Each names the version it is planned for.
Dates only where they are real
A quarter for work in progress, a half-year for what is next, a day only when a regulation sets it.
Moves are said out loud
When an item slips or is dropped, it says so here with a one-line reason, at the next quarterly review.
Shipped means released
An item counts as done when it is in a released version and in its release notes, not when the code is written.

This roadmap shows our current plans. It is not a commitment to deliver any feature, and plans can change. Do not base purchasing decisions on items that are not yet released.

Next step

Missing something you need?

Tell us what you are trying to do and what is in the way. Requests from real projects shape what moves from Later to Next.

Tell us what you need Release notes
  1. 01

    Scoping call

    Equipment, protocols, sites and the systems the data has to reach.

  2. 02

    Technical walkthrough

    A working demo against a scenario that resembles your plant, not a generic tour.

  3. 03

    Pilot plan

    A defined first line or site, with the deployment and security questions answered up front.

  4. 04

    Roll-out

    The same templates bring the next lines and sites online.