Release engineering
Cross-platform builds, checksums, install docs, packaging polish, and predictable release notes.
Open-source funding
Sponsor tzap
tzap is infrastructure-shaped software: the useful parts are the boring parts that keep working after the first release. Sponsorship helps turn a promising archive format into a dependable toolchain people can trust for private data, source records, media libraries, research sets, and cold backups.
Where support goes
Compatibility and recovery testing
Archive fixtures, damaged-volume cases, random-access restore checks, fuzz targets, and regression coverage.
Documentation and specification work
Clear user workflows, implementer notes, format revisions, migration guidance, and public examples.
Maintenance time
Issue triage, dependency updates, security reviews, bug fixes, and the unglamorous work that keeps tools trustworthy.
Why it matters
Archives often outlive the machines, cloud accounts, drives, and operating systems that created them. tzap is built around that reality: authenticated metadata, encrypted private archives, explicit plaintext mode for public archives, split volumes, recovery data, and targeted restores from large datasets.
Transparent by default
Open Collective keeps funding visible, and the work itself stays inspectable through the public repositories, specification, tests, and release history.
Help make reliable archives less fragile
If tzap is useful to you, your team, or future projects that need recoverable private archives, sponsorship is the most direct way to keep the work moving.
Support open archive infrastructure
Sponsorship helps turn tzap from a promising archive format into dependable infrastructure: releases, documentation, packaging, compatibility testing, recovery fixtures, specification work, and maintenance for people storing private data and long-lived backups.
Release engineering
Fund predictable binaries, checksums, install notes, versioned artifacts, and clearer release communication.
Compatibility testing
Support fixtures for damaged volumes, random-access restore paths, large archive behavior, and regression coverage.
Specification work
Keep the public format description, implementer notes, examples, and review surface moving with the code.