<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Self-Hosted on goroot</title>
		<link>https://blog.goroot.de/tags/self-hosted/</link>
		<description>Recent content in Self-Hosted on goroot</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 19 Aug 2026 21:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://blog.goroot.de/tags/self-hosted/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Why frontier models and privacy are not mutually exclusive</title>
				<link>https://blog.goroot.de/post/hybrid-llm-data-sovereignty/</link>
				<pubDate>Wed, 19 Aug 2026 21:00:00 +0200</pubDate>
				<guid>https://blog.goroot.de/post/hybrid-llm-data-sovereignty/</guid>
				<description>&lt;p&gt;Sooner or later, the question comes up in practically every project that&amp;rsquo;s currently getting an LLM feature: Is it even allowed to send what’s being processed here to the cloud? Support tickets with names and contract numbers, internal notes with salary data, code with customer secrets in the context window - as soon as a feature goes beyond the demo stage, a dataset appears that no one wants to send to OpenAI, Anthropic, or Google. And then the reflex kicks in: &amp;ldquo;Then we&amp;rsquo;ll just host the model ourselves.&amp;rdquo; At this point, the reality of costs intervenes.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
