About

We kept seeing the same problem. So we built for it.

Otector comes from years of working inside industrial technology, where remote access to OT was always the part that never quite fit.

The origin

Built from experience, not from a whiteboard.

The name says it plainly. Protection, built for OT.

The founders of Otector previously worked together in industrial technology, combining product ownership, OT cybersecurity and solution architecture experience across many OT environments.

Across that work, the same structural problem kept appearing. Remote access to operational technology was solved one vendor, one site and one tool at a time. Each solution made sense on its own. Together they added up to a landscape that was hard to control, hard to monitor and hard to audit, carried by the people who owned the risk rather than the people who introduced it.

The tools that existed were either built for IT and bent towards OT, or built for a single vendor's own convenience. Neither gave an asset owner a way to control the whole interaction, and neither gave external providers a way of working that customers could confidently approve.

So we decided to build a better approach: one platform that puts the asset owner in control, and gives service providers a single, credible way to support the customers who rely on them.

The founders

Two people who lived the problem.

Gerald and Bilel first worked together at Yokogawa. In the years that followed, they kept encountering the same problem from different sides: remote access assembled from VPNs, jump servers and vendor-specific tools, then forced into OT environments it was never designed for.

With complementary strengths across OT security, product and solution architecture, they founded Otector to build the platform they had wanted for years.

Co-founder & CEO · Product & OT security

Gerald Willemsen

Gerald combines experience across OT security, solution architecture and product leadership. Through his work at Yokogawa, Deloitte and on complex industrial security programmes, he has helped turn difficult cybersecurity and operational requirements into practical architectures, controls and delivery roadmaps.

At Otector, he leads the product vision, security direction and customer strategy, with a focus on making governed remote access work in operational reality.

View LinkedIn profile

Co-founder & CTO · Solution architecture

Bilel Chakroun

Bilel brings deep solution architecture and engineering experience in industrial environments. He understands how identity, network boundaries, deployment constraints and operational continuity shape what can actually be implemented in OT.

At Otector, he leads the technical architecture and platform development, translating those realities into technology that is secure, practical and deployable.

View LinkedIn profile

Together, they are building Otector to close the gap between how remote access is usually managed and how industrial environments actually need it to work.

Built for the people who use itArchitecture that fits OT constraintsEvidence security teams can trust

How we build

Principles we do not compromise on.

Control stays with the client

The asset owner decides who connects, to what, and what is allowed to happen. Always.

Designed for OT constraints

Outbound connectivity, client-side credentials and deployment models that fit real industrial networks.

Made to be adopted

A platform is only as good as its use. We build so that both customers and providers want to work in it.

Come and see

We would rather show you than tell you.

The platform already has substantial working functionality. Book a walkthrough and judge it for yourself.

Book a demo