v0.4.4 — Scheduled backups + offsite storage

Scheduled backups land, and they picked up an offsite bonus on the way.

Added

• Scheduled workflow backups. A dependency-free interval scheduler snapshots every connected instance's workflows to disk on a schedule, pruning to a configurable retention. Configure it on the Export / Backup view (interval, snapshots to keep, active-only) or over operator-gated /api/backups endpoints. The schedule is read live from config.json, so toggling it takes effect with no restart, and it fans out across the whole fleet regardless of which instance is active. A failing instance is isolated: the others still snapshot. Off by default.

• Offsite backup destination (S3-compatible). Scheduled backups can also push each snapshot to S3-compatible object storage (AWS S3, Cloudflare R2, Backblaze B2, Wasabi, self-hosted MinIO) so a backup survives loss of the host or its Docker volume. Opt-in via a new s3 dependency extra, with a Test connection probe. The local snapshot is always written first and an upload failure is recorded per instance without losing it. Credentials come only from the encrypted secret store as $VAR refs. Options: mirror the keep-N retention offsite, and Fernet-encrypt each object before upload. LAN MinIO allowed; the cloud metadata address is refused. Push-only in v1.

  Cloudflare R2's free plan (10 GB, no egress fees) holds years of fleet backups at no cost. Backblaze B2's 10 GB free tier is a comparable zero-cost offsite target.

Changed

• Local models show token usage instead of "price unknown" in the cost waterfall. Ollama and other always-local AI nodes are classified by n8n.node.type and render token counts with a plain "local" tag rather than a meaningless dollar figure. An operator price override still wins if one is set.

Full detail in the CHANGELOG. Backups guide: docs/guide/import-export.md.