Built by one person, not a company.

I'm Ege Can Gecer. My background is in biomedical engineering, and I'm currently finishing an MSc in International Engineering and Industrial Management at Hochschule Fresenius in Germany.

I built EUDAMate because EUDAMED data preparation was a bad trade for most manufacturers: pay a consultancy a lot to do it for you, or spend weeks doing it yourself by hand across 95+ fields and thousands of possible EMDN codes. I wanted a third option that was fast, transparent about what it was doing, and priced so a small manufacturer or an independent consultant could actually afford it.

I wrote the mapping, classification, and validation pipeline myself, and I'm still the one maintaining and improving it. There is no support team behind EUDAMate right now. There is me.

That also means you should know what you're dealing with. EUDAMate is a young product in early access. It hasn't been used by thousands of manufacturers, and it doesn't have a large team behind it. That's also why the pricing is what it is: built to be affordable for the people who need it, not to fund a large company. If something is unclear, missing, or doesn't work the way you expect, I want to hear about it directly.

EUDAMate does not submit anything to EUDAMED on your behalf and is not a substitute for regulatory affairs expertise. It prepares your data. Your team, or the consultant you work with, still makes the final call.

Questions, feedback, or just want to know more before you trust it with your device data: ege@eudamate.eu.