With registry push access, the 24 mirror-backed apps stopped being blocked. Ten images are now mirrored (single-platform amd64, matching the existing convention) and their pins moved: alby-hub v1.23.0 -> v1.24.0 mempool-frontend v3.0.1 -> v3.3.1 (mempool, archy-mempool-web) mempool-backend v3.0.0 -> v3.3.1 fedimintd v0.10.0 -> v0.10.1 gatewayd v0.10.0 -> v0.10.1 nostr-rs-relay 0.9.0 -> 0.10.0 portainer 2.39.1 -> 2.39.6 vaultwarden 1.30.0-alpine -> 1.37.1-alpine jellyfin 10.8.13 -> 10.11.11 home-assistant 2026.7.3 -> 2026.8.2 Every one verified pullable from our mirror after copying, so none can become an image-not-found on a node. image-versions.sh moved in lockstep — it is the baseline the update badge compares against when the catalog does not cover an app, and leaving it behind would have kept advertising an update that had already been applied. Chosen by risk, not by count: these are patch/minor bumps with no data migration. The ones held back are held for a reason each — Postgres 15->18 and 16->18 refuse to start on an older cluster, Redis 7->8, Valkey 7->9, Nextcloud 29->32 must go one major at a time, plus uptime-kuma 1->2, grafana 10->13, electrumx 1->2, photoprism, and core-lightning's three years of schema migrations. Those are each a migration plan, not a pin edit. LND (v0.18.4 -> v0.21.2) is held separately: it is only a minor bump by version but it migrates its channel database irreversibly, and this box holds real funds. Note the checker still reports several of these as behind, and that is correct: it reads the *catalog* pin, which is what nodes actually act on. These land when the catalog is regenerated and re-signed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Archipelago
Self-sovereign Bitcoin node OS and manifest-driven app platform.
Archipelago is a bootable personal server OS for Bitcoin infrastructure,
self-hosted apps, mesh communication, decentralized identity, and federation.
Apps are packaged as declarative manifest.yml files and run as rootless
Podman containers managed by the Rust backend.
What is here
core/- Rust workspace: backend API, container runtime, security, OpenWrt helpers, and performance/resource management.neode-ui/- Vue 3 + TypeScript frontend.apps/- app manifests and custom app container sources.docker/- supporting container build contexts for UI companion surfaces.image-recipe/- bootable image/ISO build inputs.Android/- Android companion app.scripts/- development, release, deployment, and validation tooling.docs/- architecture, app packaging, operations, API, and roadmap docs.
Platform model
Archipelago is built as a developer-ready app platform, not a fixed appliance:
- Apps are declared in
apps/<app-id>/manifest.yml. - The Rust parser in
core/container/src/manifest.rsis the canonical schema. - The orchestrator compiles manifests to rootless Podman/Quadlet runtime state.
- App data lives under
/var/lib/archipelago/<app-id>/. - Secrets are generated or read from
/var/lib/archipelago/secrets/and injected through Podman secrets rather than static environment values. - Release and app catalogs are signed and verified against a pinned trust anchor.
Start with:
- Architecture
- Developer Guide
- App Developer Guide
- App Manifest Spec
- Nostr Git Source Hosting Plan
- Troubleshooting
Quick start
Frontend
cd neode-ui
npm install
npm start
The dev UI runs at http://localhost:8100 with a mock backend on :5959.
Backend
cd core
cargo build
cargo test --all-features
Linux is the supported backend runtime and release-build target. macOS is fine for frontend work and many Rust compile/test loops, but host integration tests that touch Podman, systemd, networking, or image build paths require Linux.
App manifests
./scripts/validate-app-manifest.sh apps/filebrowser/manifest.yml
python3 scripts/generate-app-catalog.py
python3 scripts/check-app-catalog-drift.py --release --strict
scripts/generate-app-catalog.py requires Python with PyYAML installed.
Documentation map
The full, grouped index lives at docs/README.md. The most common entry points:
| Doc | Purpose |
|---|---|
| Architecture | System layers, crates, data paths, security model |
| Developer Guide | Local setup, code workflow, testing |
| API Reference | JSON-RPC API overview |
| App Developer Guide | How to package and test apps |
| App Manifest Spec | Manifest schema and validation rules |
| Nostr Git Source Hosting Plan | ngit/NIP-34 contribution workflow and maintainer model |
| Apps README | Packaged app catalog overview |
| Image Recipe | Bootable image build flow |
| Roadmap | Shipped, in-progress, and planned work |
| Archive | Historical plans, audits, and handoffs |
Contributing
Read CONTRIBUTING.md before opening a pull request. For security issues, follow SECURITY.md and do not open a public issue.
License
Archipelago is licensed under the MIT License. Third-party notices are listed in NOTICE and generated license inventories in component release artifacts.