---
"@type": WebPage
"@id": "https://helloloam.dev/solutions/nothing-hanging-over-you"
"@source": "https://helloloam.dev/data/webpage/nothing-hanging-over-you.json"
"@stamp": "2026-10-22T21:53:55+00:00"
about:  # 3
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/no-update-stress.json"
    name: No update stress
    identifier: no-update-stress
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/gives-you.json"
      name: Gives you
      identifier: gives-you
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/security-bolted-in.json"
    name: Security bolted in
    identifier: security-bolted-in
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/basics.json"
      name: Basics
      identifier: basics
  - "@type": DefinedTerm
    "@id": "https://helloloam.dev/data/definedterm/files-not-a-database.json"
    name: Files, not a database
    identifier: files-not-a-database
    inDefinedTermSet:
      "@type": DefinedTermSet
      "@id": "https://helloloam.dev/data/definedtermset/basics.json"
      name: Basics
      identifier: basics
description: No plugins to keep up, no login page to attack. An update replaces the engine, checks its own work, and never touches your content.
headline: Nothing hanging over you
identifier: nothing-hanging-over-you
image:
  "@type": ImageObject
  contentUrl: /assets/images/nothing-hanging-over-you.jpg
  caption: A man leans back on the sofa, hands behind his head, smiling.
inLanguage: en
name: Nothing hanging over you
url: "https://helloloam.dev/solutions/nothing-hanging-over-you"
---

# Nothing hanging over you

## The worry

A website is never finished with you. [Plugins need updates](/principles/no-update-stress), updates break things, so updates get postponed — and postponed updates are how sites get broken into. Maintenance becomes something hanging over you.

## What happens instead

A loam site has [no plugins and no login page](/principles/security-bolted-in), so the two most common ways in simply do not exist. Your content, your design and your images sit in their own folders; the engine sits beside them. An update replaces the engine and never touches your site.

## An update checks its own work

Right before an update the old engine shows a handful of your pages, right after the new one shows them again. If a page that worked stops working, the update undoes itself on the spot. Only signed releases are taken, and an update never runs by itself: someone chooses the moment.

## In practice

- Braaf runs the update on the sites it maintains; on your own server it is one command.
- Security fixes are free for every registered site.
- Nothing to migrate, nothing to reinstall.

## What it costs

[A licence](/licence) buys the stream of updates and support; without one your site keeps running, it just does not get new features. And some care stays with you: give out keys sparingly, and protect the account behind your agent like a key.