https://carlos.enredando.me/tags/aws/Recent content in Aws on EnRedAndo Me - Carlos PradosHugo -- gohugo.ioenmail@carlosprados.com (Carlos Prados)mail@carlosprados.com (Carlos Prados)© 2026 Carlos PradosMon, 16 Feb 2026 12:00:00 +0100https://carlos.enredando.me/posts/why-keystone/Mon, 16 Feb 2026 12:00:00 +0100mail@carlosprados.com (Carlos Prados)https://carlos.enredando.me/posts/why-keystone/<h2 class="relative group">The Vendor Lock-in Trap <div id="the-vendor-lock-in-trap" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-vendor-lock-in-trap" aria-label="Anchor">#</a> </span> </h2> <p>For the better part of the last decade, the industry narrative around IoT has been dominated by a &ldquo;Cloud-First&rdquo; mentality. The premise was seductive: treat your edge devices as dumb pipes and offload the heavy lifting to the cloud&rsquo;s infinite compute.</p> <p>However, as we moved from prototypes to production at scale, cracks began to appear in this facade. Latency mattered. Bandwidth costs exploded. But most importantly, we realized that by adopting managed edge runtimes, we were walking into a trap of architectural dependency.</p>