<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Devops on Some philosophy notes</title><link>https://jftr.info/tags/devops/</link><description>Recent content in Devops on Some philosophy notes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 11 Nov 2026 12:00:00 +0400</lastBuildDate><atom:link href="https://jftr.info/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>My AI workspace: one vault, three agents, and a wiki that learns</title><link>https://jftr.info/post/ai-workspace/</link><pubDate>Wed, 11 Nov 2026 12:00:00 +0400</pubDate><guid>https://jftr.info/post/ai-workspace/</guid><description>&lt;p&gt;For a long time my projects lived everywhere. Notes in one app, scripts in random repos, and most of the context only in my head. Every new chat with an AI assistant started from zero, and I explained the same things again and again: where the server is, how we deploy, what I already tried last week. At some point it became obvious that the problem is not the model, it is the memory around it.&lt;/p&gt;</description></item><item><title>Backups outside Russia: offsite copies that actually restore</title><link>https://jftr.info/post/offsite-backups/</link><pubDate>Wed, 14 Oct 2026 10:00:00 +0300</pubDate><guid>https://jftr.info/post/offsite-backups/</guid><description>&lt;p&gt;Lately more and more companies ask us the same question: what if something happens with infrastructure inside the country and all backups sit in the same place? One DC, one provider, one jurisdiction. That&amp;rsquo;s not a backup strategy, it&amp;rsquo;s a single point of failure.&lt;/p&gt;&#10;&lt;p&gt;At &lt;a href="https://www.linkedin.com/company/94864142/"&gt;Segotech&lt;/a&gt; we can help with it.&lt;/p&gt;&#10;&lt;h2 id="what-we-do"&gt;What we do&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;setup offsite backups to EU or China&lt;/li&gt;&#10;&lt;li&gt;encrypted at rest and in transit, keys stay with you&lt;/li&gt;&#10;&lt;li&gt;regular restore tests, so backup is not only &amp;ldquo;exist&amp;rdquo; but actually works&lt;/li&gt;&#10;&lt;li&gt;support for databases, VMs, Kubernetes, S3 storage, file servers&lt;/li&gt;&#10;&lt;li&gt;monitoring and alerts if backup job failed&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="how-it-goes"&gt;How it goes&lt;/h2&gt;&#10;&lt;p&gt;Setup is fast, usually few days. After that we can support it on monthly basis, or hand it over with docs to your team.&lt;/p&gt;</description></item></channel></rss>