Moru 2026.11.7
November 13, 2026
One host can run on several nodes, repositories move between them, and nodes check signatures against everything they know about a host, not only what each repository carries.
- Many nodes per host. Your node becomes the host’s control node when it serves with
--internal-listenand--internal-url, and keeps its repositories, accounts and keys. Empty nodes join it with a one-time node code (moru-node node-code, thenmoru-node join) or by themselves with an enrollment token (moru-node node-token, thenMORU_CONTROL_URLandMORU_JOIN_TOKEN). New repositories go to the node with the fewest, every node takes requests for any repository, and lists ask every node. Runners keep one address and get jobs from every node.moru-node nodeslists the nodes. A new host can start from a control node that holds no repositories (--role control), and on Fly.io--replay flylets Fly’s proxy send a request straight to the machine that serves it. See Running many nodes. - Moving repositories. A site admin moves a repository to another node from its Settings → Node, or with
moru-node move-repoon the control node. Reads keep working while it moves; writes pause with a 503 andRetry-After, queued jobs are cancelled, and running ones get 10 minutes (--drain) to finish. Pending webhook deliveries go with it, and open pages reconnect by themselves. An organization’s.morurepository, a repository linked to GitHub and one in the trash stay where they are.moru-node movesand Settings → Network follow every move, and a move can be aborted until it switches over. - Draining a node.
moru-node drain-node <node>, or Move all repositories off this node… in Settings → Network, moves every repository it can off a node, one at a time, each to the node with the fewest. A move that fails is rolled back and the drain goes on; five failures in a row stop it. What can’t move stays and is listed with why. The node takes no new repositories from then on, also after the drain, until--undoor Take new repositories again: use it before retiring a node, or to leave your original node holding only what the control node must. The Activity tab andmoru-node movesfollow drains, and--abortor Abort stops one. See Drain a node. - Settings → Network. One page for site admins, in three tabs. Nodes draws the host and its nodes as a diagram: each node’s certificate, role, version, repositories and last report, and the moves under way; a node’s menu drains it, retires it, revokes it, or restores its repositories from a backup, the same as the commands on the control node. Hosts is a grid of what each node knows about each host: its DID document and when the directory was last asked, revoked keys and where the node learned them, and a host the node doesn’t trust because its documents conflict. A host that one node trusts and another doesn’t shows in one row. Activity follows drains, moves, revocations and restores, with a count of those still running. Add a node, at the top, makes a node code or an enrollment token. While the control node is down, a repo node still shows the page from its own copy of the node list, without the actions. The same data is at
GET /api/v0/nodes,GET /api/v0/nodes/local(the answering node’s copy) andGET /api/v0/hosts. See Running many nodes. - Repo nodes keep working while the control node is down. Pushes, reads and changes go on for
--control-grace(5 minutes), a repo node that restarts meanwhile keeps what’s left of it, agents can submit, and running jobs keep reporting to the end. Pages work without organizations, under a notice. Register runners against the host’s public address, never a node’s own. - Protocol levels. Every node says which protocol level it speaks, and nodes within one level of each other work together, so you can upgrade one node at a time. The control node refuses a node further away.
- Backups by node.
moru-node backupknows which kind of node it runs on. A control node’s backup holds the host-wide state and keys; restored, it gets where each repository lives back from the repo nodes’ reports, and moves or revocations that hadn’t finished come back failed, to be started again. A repo node’s backup holds its repositories without its key: restored, it joins the host as a new node and takes over the old node’s repositories. Stop the old node first. - Retire or revoke a node’s key.
moru-node retire-node <DID>retires the key of a node that left cleanly: everything it signed keeps verifying, and it can’t sign anything new.moru-node revoke-node <DID> --at-ms <time> --vouched-from <checkpoint>revokes a key that leaked, keeping only what a checkpoint taken before then lists. Both refuse this node’s own key and keys this host never certified. On a host with many nodes, run them on the control node or use Revoke… in Settings → Network: the node’s moves are rolled back, every node writes the host’s signed revocation into each repository the node signed in, and what it signed stays valid as far as the newest checkpoint the control node received from it by then. Revoking works in a repository where the key signed more than 10,000 objects. See moru-node. - Checkpoints. The node records, every 10 minutes and when it starts, which objects in each repository its key signed, in
checkpoints/in the data directory. It keeps the last 144 that differ, and backups include them.moru-node checkpointtakes one by hand. Keep a copy off the node: after a leak, only a checkpoint from before it is worth anything. - Revocation records.
revoke-nodeandretire-noderecord each revocation inhost/revocations.json, with the checkpoint it vouches from inhost/checkpoints/, before they write any repository. A rerun after a failure writes from the recorded time and checkpoint. The control node records every node it revokes the same way and sends the records to the other nodes, which keep applying them while it’s down. Backups keephost/. A finished revocation’s message counts every repository that holds it: ”… is revoked in N repos on M nodes (W written now, A held it already)“. - Restoring a revoked node’s repositories.
moru-node restore-reposon a node of the host, or Restore its repositories from a backup… in Settings → Network (an upload, up to--max-restore-upload, 20 GiB by default), brings a revoked or retired node’s repositories back from its backup. A revoked node’s revocation goes into each one before it’s served. A node runs one restore of a given old node’s repositories at a time, and refuses a second until the first finishes or is aborted. - Revocations a copy lacks still count. A node checks every repository against the revocations it knows from its other repositories, from its own revocation records, and, on a host with many nodes, from the control node. An old copy of a repository, an import or a restored backup can’t make a revoked node key trusted again. Ops the key signed after its revocation don’t load, and its attestations stop counting for merges. See How trust works.
- Revocations are written where they’re missing. The node writes its own host’s revocations into any repository that lacks them: an import before it’s served, a GitHub link right after it fetches Moru’s data, every repository when a new revocation is recorded, and a repository a push brought old host data into. Failed writes are retried in the background.
- Fresh DID documents from the PLC directory. For
did:plchosts it trusts as attesters, and hosts imported repositories carry a valid DID document of, the node fetches the host’s log from the PLC directory about every 12 hours, so a rotated key stops counting even in repositories that never stored the rotation, and a host’s recovery of its log takes effect. A log that takes back what the directory served before is refused. - Why a signer isn’t trusted. The change page’s Evidence panel and the API’s
verifysay “revoked by … from …”, with “(known to this node)” when the repository itself lacks the revocation, or that the trusted host behind the signer isn’t trusted on this node because its DID documents disagree (untrusted_host). An object that no longer loads says the same in its error. - Import report. Importing from another node lists the hosts the repository names: known or new, the revocations the copy lacked and whether they were written before it was served, and any conflict between its DID documents. The JSON has
hostsandwarnings. - Nodes sign for password accounts and agents. A node now signs a password account’s or an agent’s changes with its own key, under a one-time authorization from that person’s or agent’s key. Older changes keep verifying as they are.
- Free disk space is checked first. A move’s target and
moru-node restorefrom a file refuse up front when the disk lacks free space of twice the archive’s size plus 64 MiB;moru-node restore-reposand a restore upload in Settings → Network need three times the backup’s size plus 64 MiB, since the backup is kept while its repositories are unpacked. Each says how much it needs and how much is free, and a move whose target lacks the room fails at once rather than trying again. - Fixed: two changes to the same person’s preferences, notification read state or dismissed suggestions at the same moment, for example from the web app and the command line, could overwrite each other.
Upgrading#
- Breaking: nodes on 2026.11.6 or earlier can’t read changes this release signs for password accounts and agents. Upgrade every node that reads your repositories, including nodes you import them into, along with this one.
- Breaking (API): the API and
/mcpno longer take Basic credentials (curl -u). Send the token asAuthorization: Bearer. Git is unchanged: it still takes a token as the password. - Upgrade runners too. On a host with many nodes, a runner from before this release can have a job update refused for a moment after it registers or renews its token; this release’s runner tries once more.
- On a host with many nodes, every node must run a release within one protocol level of the control node’s, or the control node refuses it. Upgrade the control node first, then the repo nodes.
- An object that loads today can stop loading after the upgrade, if the node knows that a key that signed one of its ops was revoked before that op. Its error, the Evidence panel and the import report name the host and the time. Repositories that held such objects were relying on a signature their host had withdrawn.
- Imports now write the node’s own host’s known revocations into the copy before it’s served. Imports and restores fail if
host/revocations.jsoncan’t be read, rather than serve a repository without its revocations. The error says what to do. - The node makes outbound HTTPS requests to the PLC directory (
--plc-url) for thedid:plchosts it trusts as attesters and those imported repositories name. On a node that can’t or shouldn’t reach it, setMORU_NO_PLC_REFRESH=1(--no-plc-refresh) forserveand every other command you run on the data directory. - A
did:plchost whose directory log the node can’t refresh for about a day stays trusted, including one that recovered its log (Settings → Network shows Recovered, stale). It is shown as Not trusted until a fetch succeeds only when a document a repository carries diverges from the node’s last log in a way that log’s recovery doesn’t explain. - If you restore a node from a backup taken before you revoked a node key, run
revoke-nodefor that key again with the same time (orretire-nodeagain for a key you retired).