Hi, I’m Remko Weijnen.
I’m an Innovation Engineer at Cloudhouse Labs, where I work on early product ideas, prototypes and technical experiments before they become formal engineering projects. My role sits close to product: exploring what might be useful, building enough to prove or disprove an idea, and helping turn future product direction into something people can actually see, test and discuss.
I’ve spent nearly thirty years working in and around Windows, infrastructure, virtualization, application delivery and end-user computing. Earlier in my career I worked on infrastructure migration projects, including moves from Windows NT-era environments to Active Directory, Exchange and Citrix-based platforms. I have always used development and automation to make consultancy and administration work more reliable, repeatable and less boring — what many people would now simply call DevOps.
Over time, application delivery became my main focus. A lot of that work involved making difficult or badly behaved applications run properly on VDI and SBC platforms without weakening security or turning the environment into a collection of exceptions. That naturally led me deeper into Windows internals, debugging, reverse engineering and application compatibility.
I was a Citrix CTP from 2013 until the programme ended in 2025, have been a Parallels VIPP since 2017, and co-founded the Dutch Citrix User Group.
These days my work and interests also include security research, reverse engineering, automation, AI-assisted development, Home Assistant, homelab setups and building small tools to solve specific problems.
This blog is where I write about the things I work on and the technical rabbit holes I end up in. Some posts are polished walkthroughs. Others are closer to lab notes: things I tried, broke, reversed, automated or eventually understood well enough to write down.
Expect posts about Windows internals, application delivery, debugging, security tooling, reverse engineering, packaging difficult applications, AI workflows, automation, Home Assistant, lab setups and the occasional obscure problem future-me would otherwise forget.
I write mostly for people who enjoy practical technical detail: engineers, sysadmins, packagers, security folks, homelabbers and anyone who likes understanding how things work under the hood.
Nothing here is meant to be perfect or final. It is a technical blog, not a product manual. But when I find something useful, strange or hard-won, I try to write it down.
Privacy
Last updated: 4 November 2026
This is a personal blog. I don’t run analytics, I don’t use advertising or tracking, and the site itself sets no cookies. This section describes what data is still processed when you read it, and by whom.
Hosting: GitHub Pages and Cloudflare
The blog is a static site. The pages are hosted on GitHub Pages (GitHub, Inc., part of Microsoft) and reach you through Cloudflare, which sits in front of it as a CDN and for security.
Like any web server, both see the technical details of each request: your IP address, the page you ask for, your browser’s user agent, the referring page and the time. They use this to deliver the pages and to protect the site against abuse. I don’t receive these logs myself. Cloudflare gives me aggregated statistics, such as the number of requests per page and which crawlers (including AI crawlers) visit the site, but not your IP address. AI services may read the posts to answer questions; crawlers that only collect training data for parties that don’t link back are refused, both in robots.txt and at Cloudflare.
Cloudflare may set a strictly necessary security cookie (cf_clearance) if it shows you a security check. The site itself sets no cookies.
Both companies are based in the United States and are certified under the EU-US Data Privacy Framework. Their own privacy statements apply: GitHub and Cloudflare. The legal basis is my legitimate interest in publishing the blog and keeping it secure.
Stored in your browser
The site stores a few preferences in your browser’s local storage, so they stay the same between visits: light or dark theme (rw-theme), font size (rw-font), high contrast (rw-contrast), reduced motion (rw-motion) and your last few search queries (rw:recent). These never leave your browser. You can remove them by clearing the site data in your browser.
Search, fonts and scripts
Search runs entirely in your browser, using an index that is part of the site. Your searches are not sent anywhere. Fonts, scripts and videos are served from the site itself, not from a third party.
Contact form
The contact form is handled by a small Cloudflare Worker. It checks the form with Cloudflare Turnstile, a privacy-friendly alternative to a CAPTCHA that loads a script from Cloudflare on the contact page only. The Worker then sends your message as an email through Microsoft 365, where my mailbox is hosted, and does not store it. I keep the email as long as I need it to answer you.
Comments
The old WordPress version of this blog had comments. Approved comments are kept on the posts as a static, read-only archive, showing the name the commenter entered, the date and the text. Email addresses were never published. New comments are not possible. If you wrote a comment and want it removed or anonymised, let me know through the contact form.
Your rights
Under the GDPR you can ask what personal data I hold about you, and ask for it to be corrected or removed. In practice that is only the archived comments, because I don’t keep visitor data myself. For the hosting logs, contact GitHub or Cloudflare. You can reach me through the contact form. You also have the right to file a complaint with the Dutch data protection authority, the Autoriteit Persoonsgegevens.
Views and opinions on this site are my own and don’t necessarily represent my employer.