---
"@type": WebPage
"@id": "https://helloloam.dev/updates"
"@source": "https://helloloam.dev/data/webpage/updates.json"
"@stamp": "2026-10-20T13:48:22+00:00"
description: "What a licence key buys, what the update service keeps, and what happens when a term ends: nothing stops. Version 1.1."
headline: Loam Update Service Terms
identifier: updates
inLanguage: en
name: Updates
url: "https://helloloam.dev/updates"
---

# Updates

*Version 1.1 — 20 October 2026. Referred to by the Loam Licence, condition 6, and the Support Policy.*

## The service

The update service at `license.helloloam.dev` serves signed loam releases to installations that hold a licence key. `loam license` binds a key to an installation and gives it the trust anchor; `loam update` fetches a release, verifies it against that anchor, replaces the engine whole and runs `migrate`; a release that fails its own check is rolled back. The service never reaches an installation: the installation pulls.

## The term

1. A licence key entitles one installation — one site root on one host — to every release published in the **twelve months** from the day the key is issued. A release published in that window may be pulled after it too.
2. The term can be renewed at any time, for the same price per period. A lapse costs nothing extra: a renewal starts on the day it is made.
3. After the term, the installation keeps running at its release. `loam update` says in words that a feature needs a running term, and which fix is still free; nothing stops.
4. **Fixes are free.** Every release says what it is: a *fix* (a patch, including security fixes), a *feature*, or a new *line*. A fix may be pulled by any licensed installation on a supported line ([Support Policy](/support)) — every licence comes with its key — whether or not its term is current. A feature, and the first release of a new line, need a running term.
5. A key belongs to one installation. It may be moved to another domain after proof of the key; it is never shared between installations.

## What the service keeps

The domain; the key, encrypted and filed under its fingerprint; the status and term; and a pull log of which release was pulled when, kept for twelve months. Nothing of the site: no content, no visitors, no logs of it. To slow down abuse, the service counts requests per address — as a hash, for a minute. A key that is cancelled is kept for twelve months for the books, then removed. Payment runs through the payment provider under its own terms; what it asks of you, it keeps.

## Acceptance

Running `loam license` accepts the [Loam Licence](/licence), these terms and the [Support Policy](/support) as they stand that day; the installation writes the acceptance, with its date, in its journal.

## Availability

The service is provided on a best-effort basis, without a service-level commitment. An installation never depends on it to run; an outage affects pulling only.

## Revocation

A key is revoked only for a breach of the Loam Licence — above all redistribution, or circumventing the signed-release chain. The installation keeps running; pulling stops. A lapsed payment is not a revocation: the term simply ends.

## Plans and prices

Plans and prices are published on [this site](/get-loam), per installation, excluding VAT. A platform that provides sites to its own clients registers a key per client installation under its plan, and is the first line for those clients.

## Changes, law and forum

These terms may change for terms that begin after the change, with notice on this site. They are governed by the laws of the Netherlands; disputes are brought before the competent court of Rotterdam, without prejudice to mandatory rules on jurisdiction. The service is run by Joey den Braven, trading as Braaf - codes en creaties, Rotterdam.

## What it costs

A key buys twelve months of releases for one installation. Fixes stay free afterwards; features wait for a renewal. The service keeps your domain, your key (encrypted) and what you pulled — nothing of your site. Pulling can pause; your site never does.