About Cordis

We believe the people who understand a system best should be the ones who define how it behaves.

We absorb the complexity so the people who understand the system can finally be the ones who own it.

Want to own yours?

The foundation

Built from frustration.
Driven by conviction.

Benno Beuting understood machines. He understood how they should behave. And he spent his days doing neither of those things.

He was writing code. Translating what he already knew into something the system could execute. And when he tried to make the system behave the way he knew it should, the code pushed back. Fragile in ways nobody could predict. So the safe choice was always a small fix instead of the right one.

“I kept thinking: I know exactly what this machine should do. Why am I spending my days fighting the code instead of defining the behavior?”
Benno Beuting, founder. 2000.

He realised the tools were built for the wrong person. So in 2000, he built for the right one.

The answer

The answer

Every other engineering discipline solved this long ago. Mechanical engineers work in CAD. Electrical engineers work in schematics. They define what something should do, and the tools handle the rest. Control software never made that move. It is still built line by line, in languages designed in the 1990s, by specialists translating knowledge that someone else already has.

Cordis SUITE makes that move. The people who understand the system define how it behaves. Everything else is generated.

The knowledge no longer lives in code nobody dares to touch. It lives in a model the whole organization owns.

Twenty-five years later, it is still the only platform that made this move.

What we stand for

What we stand for

  1. The people who understand a system should be the ones who define it.

    Not just the ones who can write code. The domain expert, the process engineer, the operator with fifteen years on the floor. They carry the knowledge. The tools should work for them, not the other way around. When the right people can finally define how a system behaves, everything about how that system performs changes.

  2. Your system should reflect your choices. Not ours.

    Every organization runs differently. Different hardware, different vendors, different ways of working. Most platforms make that choice for you. We built ours so you never have to ask permission. The platform connects to whatever you choose. It generates readable, documented code that runs on your chosen hardware and IDE, and stays out of every decision that belongs to you.

    We build the platform. You build the system.

  3. Engineering knowledge should outlast the engineer.

    When someone leaves, their knowledge should not leave with them. With Cordis it stays. In one model. In one place. Owned by the organization. Forever.

Partners

Model-driven engineering is not a Cordis invention. It is a shared conviction. These are the research institutes, universities, and companies proving it with us.

  • TNO-ESI
  • TNO
  • TU Eindhoven
  • University of Stuttgart
  • Universidad de Málaga
  • MTC
  • Inosoft
  • Capgemini

Where we are

Two locations. Chosen, not inherited.

Eindhoven places us inside Brainport, the densest concentration of high-tech manufacturing in Europe. The companies defining the next generation of industrial systems work within a few kilometres of our office. Málaga extends that presence across Southern Europe, close to the operations that run it.

We are where the hardest problems are being solved.

Cordis offices: Eindhoven, the Netherlands, and Málaga, Spain.
An unhandled error has occurred. Reload x

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.