A project company may have capable people, good tools and discipline. With a larger portfolio, context still starts to disappear.

Pelenoir is built around this context: many accounts, many attachments, many commitments, many decisions and little time to reconstruct the truth afterwards.

The product direction is simple: capture company memory in a local system before the project consumes it.

CEO Pelenoir @ KENDU

Martina Uhrinova

Martina Uhrinova, CEO Pelenoir

Martina leads Pelenoir under KENDU and keeps product design, user experience and AI ethics grounded in the AEC environment.

She has worked in architecture and construction for more than 25 years. Her role is to name the risks of an AI system so project information is processed clearly, without misuse and in line with the AI Act and GDPR.

LinkedIn
CEO Business development AI ethics GDPR

CTO Pelenoir

Milan Illes

Milan Illes, CTO Pelenoir

Milan brings more than 25 years of experience with real AEC projects into Pelenoir: construction management, process control, data structures and technical architecture.

He builds Pelenoir as a domain driven, test driven and design driven system. Construction management logic is not glued on top; it is baked directly into the algorithms so the product can fit any AEC organisation.

LinkedIn
CTO 25+ years AEC domain driven AI infra

Robotics & AI Advisor

Michal Adamik

Michal Adamik, Robotics & AI Advisor Pelenoir

Michal brings a systems engineering perspective to Pelenoir, connecting physical environment with algorithmic logic - from sensors and robotics to data pipelines and automated outputs.

His experience with digitalisation advisory and system architecture helps Pelenoir stay technically correct while remaining usable in real AEC organisations.

LinkedIn
Robotics AI systems Digitalization System architecture

Automation & Integration Advisor

Matus Marko

Matus Marko, Automation & Integration Advisor Pelenoir

Matus brings deep experience in designing and implementing automated systems to Pelenoir - from data flows to tool integrations in real company environments.

His approach is pragmatic: the system must work reliably outside laboratory conditions. For Pelenoir, that means confidence that the pipeline from ingest to output holds under the pressure of real projects.

LinkedIn
Automation Integration Workflow Pipeline Systems

Business Development & Strategic Partnerships

Bran Hrivnak

Bran Hrivnak, Business Development & Strategic Partnerships Pelenoir

Bran brings business development and strategic partnership building to Pelenoir. He helps connect the product with developers, investors and the wider AEC ecosystem, where trust, timing and a precise reading of the market matter.

His experience in real estate and development helps define where Pelenoir creates business value: decision-making, portfolio work, partnerships and opening new opportunities.

LinkedIn
Business development Strategic partnerships Real estate AEC network
01

Construction portfolios

Developers, investors and corporations need to see patterns across projects and the story behind every board update.

02

Supplier pressure

Contractors and general contractors depend on an exact trail: who waited, what changed and where a claim started.

03

Expert coordination

Architects, project managers and consultants hold context that quickly becomes personal memory in people's heads and scattered tools.

04

Public accountability

Cities, municipalities and public institutions need local AI infrastructure with control over data.

Domain driven means the system starts with the language of construction: contract conditions, revisions, claims, approvals, suppliers and deadlines.

Test driven means the output must stand on real project data, not on a sample presentation.

Design driven means the output must be readable for the person who has to decide.

Local first means project memory remains under the organisation’s control.

Audit ready means every conclusion has an origin, a path and a reason.

domain testing design local infrastructure audit trail