<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Architecture on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/architecture/</link>
    <description>Recent content in Architecture on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Build vs. Buy vs. Wrap Decision for AI Features</title>
      <link>https://www.secdev.uk/blog/leadership/4.8-build-vs-buy-vs-wrap/</link>
      <pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/4.8-build-vs-buy-vs-wrap/</guid>
      <description>&lt;p&gt;The traditional build-versus-buy decision assumes a relatively stable landscape, you evaluate the options, make a choice, and live with it for years. The AI landscape doesn&#39;t work that way. The model you build on today might be obsolete in six months. The vendor you choose might pivot, get acquired, or disappear. The capabilities that seem cutting-edge now might be commoditised by next quarter.&lt;/p&gt;&#xA;&lt;p&gt;This instability adds a third option to the traditional calculus: wrap. Build your own models, buy a platform, or wrap existing APIs with your own logic. Each has trade-offs, and the right choice depends on your specific context.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
