<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Self-Hosting on My Blog</title><link>https://hugo-blog.aitbytes.dev/tags/self-hosting/</link><description>Recent content in Self-Hosting on My Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 11 Jun 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://hugo-blog.aitbytes.dev/tags/self-hosting/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosting GitLab in 2026: The Microsoft Independence Move</title><link>https://hugo-blog.aitbytes.dev/posts/2026-06-11-self-hosting-gitlab-guide/</link><pubDate>Thu, 11 Jun 2026 07:00:00 +0000</pubDate><guid>https://hugo-blog.aitbytes.dev/posts/2026-06-11-self-hosting-gitlab-guide/</guid><description>&lt;p&gt;A software developer at a German automotive supplier told me he chose GitLab for one reason.&lt;/p&gt;
&lt;p&gt;&amp;ldquo;Because it&amp;rsquo;s not owned by Microsoft.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;He&amp;rsquo;s not alone. Across dozens of Reddit threads, practitioner forums, and industry discussions, this sentiment appears again and again. Self-hosting GitLab isn&amp;rsquo;t just a deployment choice. For a significant segment of the community, it&amp;rsquo;s a statement about platform independence and data sovereignty.&lt;/p&gt;
&lt;p&gt;But self-hosting a platform as complex as GitLab comes with real operational costs. Here&amp;rsquo;s what that trade-off actually looks like in 2026.&lt;/p&gt;</description></item></channel></rss>