<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lethra — Writing</title>
    <link>https://lethra.io/blog/</link>
    <atom:link href="https://lethra.io/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Retention, cryptographic evidence, provable deletion, and the architecture decisions behind Lethra.</description>
    <language>en</language>
    <lastBuildDate>Thu, 13 Aug 2026 09:00:00 GMT</lastBuildDate>
    <item>
      <title>A company in Cyprus, data in Germany</title>
      <link>https://lethra.io/blog/a-company-in-cyprus-and-data-in-germany/</link>
      <guid isPermaLink="true">https://lethra.io/blog/a-company-in-cyprus-and-data-in-germany/</guid>
      <description>Where a company is registered and where its data physically sits are separate questions with separate answers. Both of ours are deliberate, and the reasoning is the kind a compliance reviewer will ask for anyway.</description>
      <pubDate>Thu, 13 Aug 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>company</category>
      <category>sovereignty</category>
      <category>infrastructure</category>
    </item>
    <item>
      <title>What we chose not to build</title>
      <link>https://lethra.io/blog/what-we-chose-not-to-build/</link>
      <guid isPermaLink="true">https://lethra.io/blog/what-we-chose-not-to-build/</guid>
      <description>No Kubernetes, no service mesh, no event bus, no dashboard for end users, no document management features. Each omission was a decision with a reason, and the reasons are more useful than the list.</description>
      <pubDate>Thu, 06 Aug 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>architecture</category>
      <category>engineering</category>
      <category>scope</category>
    </item>
    <item>
      <title>Four regimes, one API surface</title>
      <link>https://lethra.io/blog/four-regimes-one-api-surface/</link>
      <guid isPermaLink="true">https://lethra.io/blog/four-regimes-one-api-surface/</guid>
      <description>Retention rules differ by jurisdiction and change over time. Putting that behind a declared regime keeps it out of partner code, and makes the schedule an auditable artefact rather than a scattered assumption.</description>
      <pubDate>Tue, 28 Jul 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>product</category>
      <category>api-design</category>
      <category>architecture</category>
    </item>
    <item>
      <title>The deposit as a unit</title>
      <link>https://lethra.io/blog/the-deposit-as-a-unit/</link>
      <guid isPermaLink="true">https://lethra.io/blog/the-deposit-as-a-unit/</guid>
      <description>One sealed envelope, one key, one lifecycle. Why the whole system is built around a single unit of retention, and what breaks in designs that pick a coarser one.</description>
      <pubDate>Thu, 16 Jul 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>architecture</category>
      <category>product</category>
      <category>data-model</category>
    </item>
    <item>
      <title>Proof that outlives the provider</title>
      <link>https://lethra.io/blog/proof-that-outlives-the-provider/</link>
      <guid isPermaLink="true">https://lethra.io/blog/proof-that-outlives-the-provider/</guid>
      <description>Most compliance tooling produces evidence that stops working when the vendor does. Three verification paths, each less dependent on us than the last, and the third works with no connection to us at all.</description>
      <pubDate>Thu, 09 Jul 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>verification</category>
      <category>cryptography</category>
      <category>trust</category>
    </item>
    <item>
      <title>The provider that can read your archive</title>
      <link>https://lethra.io/blog/the-provider-that-can-read-your-archive/</link>
      <guid isPermaLink="true">https://lethra.io/blog/the-provider-that-can-read-your-archive/</guid>
      <description>If an archive provider can read what they hold for you, the risk was duplicated rather than outsourced. No certification changes that, because the exposure is a capability rather than a policy.</description>
      <pubDate>Thu, 02 Jul 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>threat-model</category>
      <category>encryption</category>
      <category>risk</category>
    </item>
    <item>
      <title>Signing once a day instead of 700,000 times</title>
      <link>https://lethra.io/blog/signing-once-a-day-instead-of-700000-times/</link>
      <guid isPermaLink="true">https://lethra.io/blog/signing-once-a-day-instead-of-700000-times/</guid>
      <description>The obvious version of our signing design needed around 700,000 hardware signatures a month. Batching them into a daily Merkle root brought it to roughly 100, with the customer-side guarantee unchanged.</description>
      <pubDate>Thu, 25 Jun 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>cryptography</category>
      <category>merkle-trees</category>
      <category>architecture</category>
      <category>cost</category>
    </item>
    <item>
      <title>What deletion actually means in a distributed system</title>
      <link>https://lethra.io/blog/what-deletion-means-in-a-distributed-system/</link>
      <guid isPermaLink="true">https://lethra.io/blog/what-deletion-means-in-a-distributed-system/</guid>
      <description>A delete call returns a status code, not evidence. Between that call and the bytes being unrecoverable sits a chain nobody outside the provider can inspect. Crypto-shredding closes the gap.</description>
      <pubDate>Thu, 18 Jun 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>cryptography</category>
      <category>deletion</category>
      <category>key-management</category>
    </item>
    <item>
      <title>Storage is the cheap part</title>
      <link>https://lethra.io/blog/storage-is-the-cheap-part/</link>
      <guid isPermaLink="true">https://lethra.io/blog/storage-is-the-cheap-part/</guid>
      <description>Long-term document retention is usually costed as a storage question. The storage line turns out to be a rounding error, and the four properties that actually matter are not things a bucket provides.</description>
      <pubDate>Thu, 11 Jun 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>architecture</category>
      <category>evidence</category>
      <category>storage</category>
    </item>
    <item>
      <title>The bureaucracy did not disappear. It moved.</title>
      <link>https://lethra.io/blog/the-bureaucracy-did-not-disappear/</link>
      <guid isPermaLink="true">https://lethra.io/blog/the-bureaucracy-did-not-disappear/</guid>
      <description>A generation of platforms removed paperwork from the user&#39;s day. The obligations attached to that paperwork did not vanish — they landed on the platform, which was built for speed rather than for keeping things.</description>
      <pubDate>Fri, 05 Jun 2026 09:00:00 GMT</pubDate>
      <author>office@lethra.io (Lethra Technologies Ltd.)</author>
      <category>retention</category>
      <category>platforms</category>
      <category>evidence</category>
    </item>
  </channel>
</rss>
