<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Insights on software portfolio management on Unicorn.pm</title><link>https://unicorn.pm/blog/</link><description>Recent content in Insights on software portfolio management on Unicorn.pm</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://unicorn.pm/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>European Software Alternatives: Assessing Vendor Dependence Across Your Application Portfolio</title><link>https://unicorn.pm/blog/european-software-alternatives/</link><pubDate>Mon, 12 Oct 2026 00:00:00 +0000</pubDate><guid>https://unicorn.pm/blog/european-software-alternatives/</guid><description>&lt;aside class="uc-summary"&gt;&lt;div class="uc-summary-head"&gt;In short&lt;/div&gt;&#10; &lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Digital sovereignty&lt;/strong&gt; is control over your technology choices and dependencies. It starts with knowing which vendors, and which countries, your applications depend on.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Vendor concentration hides in plain sight.&lt;/strong&gt; Each purchase looks reasonable on its own; the dependency only shows when you analyze the portfolio as a whole.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;A practical assessment&lt;/strong&gt; looks at four things: vendor concentration, geographic distribution, capability dependency and cloud dependency. European alternatives then become an informed choice, not a reflex.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&#10;&lt;/aside&gt;&#10;&#10;&lt;p&gt;For years, software was bought on functionality, security, cost and ease of implementation. Today another consideration is quickly gaining ground among CIOs, enterprise architects and application portfolio managers: &lt;strong&gt;digital sovereignty&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>CMDB vs Application Portfolio Management: What's the Difference?</title><link>https://unicorn.pm/blog/cmdb-vs-application-portfolio-management/</link><pubDate>Tue, 06 Oct 2026 08:00:00 +0200</pubDate><guid>https://unicorn.pm/blog/cmdb-vs-application-portfolio-management/</guid><description>&lt;aside class="uc-summary"&gt;&lt;div class="uc-summary-head"&gt;In short&lt;/div&gt;&#10; &lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;A CMDB&lt;/strong&gt; is the operational record of your IT assets and how they connect. It tells you &lt;em&gt;what you have&lt;/em&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Application Portfolio Management (APM)&lt;/strong&gt; judges applications on business value, cost and risk. It tells you &lt;em&gt;what to keep, replace or retire&lt;/em&gt;.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Most organizations need both.&lt;/strong&gt; The CMDB provides the data, APM turns it into decisions, and enriching CMDB records with market data connects the two.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&#10;&lt;/aside&gt;&#10;&#10;&lt;p&gt;Many organizations invest years of effort in their Configuration Management Database (CMDB). Yet when an enterprise architect, application portfolio manager or CIO asks a strategic question about the software landscape, the answer is surprisingly hard to get. Questions like these:&lt;/p&gt;</description></item></channel></rss>