Your brain lives on LAN servers, and LAN takes care of backing it up. There is nothing for you to download, schedule, or remember. That frees the word "routine" up for what actually keeps a brain healthy over years: reviewing what changed, keeping your sources connected, and keeping the content curated.
This file covers what LAN does for you, and what is left for you to do.
LAN backs the brain up for you
Every day, LAN takes a full-tree snapshot of your brain on the server side. Full-tree means the whole thing: every wiki page, the folder structure, and the raw source files you ingested. Retention is managed by LAN, so old snapshots roll off on a schedule you do not have to think about.
There are no commands, no repository, no push, and no button to click. If your laptop dies tomorrow, your brain is untouched. That was always the point of hosting it rather than handing you a folder to look after.
If something goes badly wrong at the storage level, restoring from a snapshot is an operations task on LAN's side. Write to info@lanbrain.ai and tell us what happened and roughly when.
The routine that replaces it: hygiene
The real risk to a brain is not disk failure. It is drift: pages that quietly went wrong, a connector that stopped syncing three weeks ago, a raw/ folder nobody ever ingested. That is what the routine below is for.
Weekly: review what changed
You do not have to skim the dashboard page by page. Ask the AI to run the weekly-review skill: it reads the brain's real change history for the period and hands you a short, grouped summary of what was added, edited, or removed, and by whom. If you are an owner or admin doing oversight, the change-review skill groups the same changes by contributor so you can sign off on them or revert what should not have landed.
Every page still carries a History panel showing its previous versions, a save you regret can be reversed with Undo, and deleted pages are recoverable. You are looking for two things in the summary. First, edits you did not expect: your AI client writes to the brain, and an ingest that misread a document shows up here before it spreads. Second, a stretch with no activity at all, which usually means an integration stopped feeding the brain rather than that you had a quiet week.
Monthly: check your integrations are still connected
Connectors expire. A password change, a revoked OAuth grant, or a workspace admin tightening permissions will silently stop the flow, and a brain that stopped ingesting looks exactly like a brain nobody wrote to.
Once a month, open Settings and confirm each connected source is still green. Reconnect anything that is not. This is the single check that catches the most damage for the least effort.
Ongoing: keep the brain curated
A brain nobody prunes becomes a brain people stop trusting. Almost none of this curation is yours to do by hand. The AI edits, creates, and maintains; you review and decide. Point it at the work:
- Run the source-sweep skill so the AI re-walks your connected folders, catches what changed, and updates the pages that cite those sources with a reason for each change.
- Ask the AI to fix broken wikilinks, merge duplicate people and organisations, and add aliases so future ingests link them correctly.
- Ask it to flag pages that are no longer true, then delete the ones you confirm. A wrong page is worse than a missing one, because your AI will answer from it.
The health-checks guide has the full routine and the prompts that let the AI do most of this for you.
The AI works at your level of access
A skill runs inside the session of whoever invokes it, so it can only ever read and change what that person is allowed to. When an owner runs source-sweep or a review, it covers the whole brain; when a member runs the same skill, it covers only their departments. You do not configure this. The scope follows whoever is asking, which is why the same routines are safe for everyone on the team to run.
Recovering from a mistake
You do not need a backup for the ordinary cases, because the dashboard already covers them:
- A bad save: open the page's History panel and restore an earlier version.
- A bad ingest: use Undo to reverse the writes that ingest made.
- A deleted page: restore it from the deleted pages list.
Reach for LAN's snapshots only when the damage is larger than a page or two.
Your brain is yours
The content in your brain belongs to you. It is plain markdown, not a proprietary format, and every page is governed by permissions you control: you decide which people and which AI clients can read what, page by page. Hosting it on LAN is what removes the backup chore from your plate, not a claim on what is inside it.
When in doubt, ask the AI
Your AI client can run most of this for you. Try:
Look at what changed in my brain over the last two weeks. Flag anything that looks like a bad ingest, and tell me if any source has gone quiet.