<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MekOps</title>
    <link>https://mekops.com/</link>
    <description>Recent content on MekOps</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© CC-BY-4.0 by MekOps</copyright>
    <lastBuildDate>Tue, 16 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mekops.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WANTED is Public: The Repo, the Docs, and What&#39;s Actually Built</title>
      <link>https://mekops.com/post/2026-06-16_wanted_public/</link>
      <pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mekops.com/post/2026-06-16_wanted_public/</guid>
      <description>
        
          
            I promised an alternative to the firmware monolith. The WANTED engine is public now — here&#39;s what actually builds and runs, and what&#39;s still a TBD.
          
          
        
      </description>
    </item>
    
    <item>
      <title>Your Firmware is a Monolith. Fix It.</title>
      <link>https://mekops.com/post/2026-06-03_wanted_part1/</link>
      <pubDate>Wed, 03 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mekops.com/post/2026-06-03_wanted_part1/</guid>
      <description>
        
          
            You wouldn&#39;t ship your entire microservices backend as a single statically-linked binary running as root on an
unpatched server, right? Yet that is exactly the architecture running on embedded devices everywhere — from smart-home
sensors to industrial controllers. Embedded firmware is stuck in the pre-container era — unisolated,
un-hot-swappable blobs. This is the first post in a series on WANTED, a new general-purpose
cloud-native runtime for embedded devices.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Siphon v0.5.x: Zero-Downtime Hot Reloading and The Garmin-Tailscale Funnel</title>
      <link>https://mekops.com/post/2026-04-21_siphon_05x_release/</link>
      <pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mekops.com/post/2026-04-21_siphon_05x_release/</guid>
      <description>
        
          
            Siphon v0.5.0 introduces the critical new feature for a gateway app: zero-downtime hot reloading.
A powerful new integration is also showcased — using tailscale funnel and the {API}Call Garmin widget to securely
bridge a watch to Home Assistant via MQTT, without exposing a single port on my router.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Project Siphon: v0.4 Architecture, The HA Add-on, and The Web UI</title>
      <link>https://mekops.com/post/2026-04-06_siphon_new_version/</link>
      <pubDate>Mon, 06 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mekops.com/post/2026-04-06_siphon_new_version/</guid>
      <description>
        
          
            With the release of the v0.4.x series, Siphon has officially outgrown its initial &#34;script replacement&#34; phase. I have
completely stripped and rebuilt the core memory bus, introduced a highly opinionated v2 declarative schema, and,
most importantly, packaged the entire engine as a native Home Assistant Add-on.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Siphon: Building a Zero-Trust Edge Gateway for Home Assistant</title>
      <link>https://mekops.com/post/2026-03-30_siphon_intro/</link>
      <pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://mekops.com/post/2026-03-30_siphon_intro/</guid>
      <description>
        
          
            If you are exposing your Home Assistant instance directly to the Internet, you are playing Russian roulette with your
local network. It only takes one zero-day vulnerability in a custom integration to give a botnet full access to your
smart home and everything else on your LAN. But we live in a connected world. You still need a way for external
services—like a GPS tracker on your car, a webhook from a Garmin watch, or a custom script running on a remote
VPS to push data into your home.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Project TELEGRAPH (Part 3): Bare Metal, Bit-Banging, and the 4MB Heist</title>
      <link>https://mekops.com/post/2026-03-27_reversing_clock/</link>
      <pubDate>Fri, 27 Mar 2026 12:00:00 +0100</pubDate>
      
      <guid>https://mekops.com/post/2026-03-27_reversing_clock/</guid>
      <description>
        
          
            With our custom ESP32 wireless flasher built and tested in Part 2, we finally severed the USB cord.
Now it was time to actually run some code on the clock&#39;s STM32F105RB.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Project TELEGRAPH (Part 2): Escaping the Cables with a Custom ESP32 Wireless Flasher</title>
      <link>https://mekops.com/post/2026-03-09_wireless_flasher/</link>
      <pubDate>Mon, 09 Mar 2026 12:00:00 +0100</pubDate>
      
      <guid>https://mekops.com/post/2026-03-09_wireless_flasher/</guid>
      <description>
        
          
            Let’s be honest: the reality of hardware reverse engineering usually involves sitting hunched over a cluttered desk,
tethered to your target device by a short USB cable, constantly manually resetting the board. I don&#39;t have much
space on my desk, and I absolutely despise cable clutter.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Project TELEGRAPH (Part 1): Rescuing a $15 LED Matrix from Software Purgatory</title>
      <link>https://mekops.com/post/2026-03-08_telegraph_intro/</link>
      <pubDate>Sun, 08 Mar 2026 12:00:00 +0100</pubDate>
      
      <guid>https://mekops.com/post/2026-03-08_telegraph_intro/</guid>
      <description>
        
          
            Sometimes the best hardware hacking projects start because you refuse to accept terrible UX.

          
          
        
      </description>
    </item>
    
    <item>
      <title>Defining MekOps: Why I&#39;m Bringing Cloud-Native to Bare Metal</title>
      <link>https://mekops.com/post/2026-01-24_hello/</link>
      <pubDate>Sat, 24 Jan 2026 10:00:00 +0100</pubDate>
      
      <guid>https://mekops.com/post/2026-01-24_hello/</guid>
      <description>
        
          
            The gap between Cloud infrastructure and Embedded systems is too wide. Here is how I plan to bridge it with Microservices, Embedded, Kernels and Operations.
          
          
        
      </description>
    </item>
    
  </channel>
</rss>