tzap-org
Help fund tzap releases, documentation, compatibility testing, and long-term maintenance.
Contributors
tzap-org is all of us
Our contributors 1
Thank you for supporting tzap-org.
Connect
Let’s get the ball rolling!
News from tzap-org
Updates on our activities and progress.
Open source archive format
https://github.com/tzap-org/tzap
Published on June 14, 2026 by tzaporg
About
tzap is an open archive format and Rust reference implementation for fast, encrypted, recoverable archives.
It is built for archives people may need to trust years from now: private datasets, source records, media libraries, research data, legal material, and cold backups.
One command should be enough. No stitching together tar, compression, encryption, checksums, parity files, split-volume naming, and restore logic by hand.
tzap focuses on:
- Fast compression with Zstandard.
- Encryption for private archive contents, names, metadata, and indexes.
- Explicit plaintext mode for public, recovery-focused archives.
- Authenticated metadata and payloads.
- Reed-Solomon recovery for damaged or missing volumes.
- Split-volume archives for drives, discs, object storage, and offline sets.
- Targeted restores from very large archives without unpacking everything.
- An open specification, open implementation, tests, and fuzz targets.
Why Sponsor
Archives often outlive the computers, cloud accounts, drives, and operating systems that created them. Reliable archive software needs more than a first release; it needs packaging, compatibility fixtures, damage testing, documentation, security review, and steady maintenance.
Sponsorship helps turn tzap from a promising open format into a dependable toolchain that people can actually adopt.
What Funding Supports
- Release engineering: cross-platform builds, checksums, packaging polish, and release notes.
- Compatibility and recovery testing: archive fixtures, damaged-volume cases, random-access restore checks, fuzz targets, and regression coverage.
- Documentation and specification work: user workflows, implementer notes, format revisions, migration guidance, and public examples.
- Maintenance time: issue triage, dependency updates, security reviews, and bug fixes.
Transparency
Open Collective keeps funding visible. The work itself stays inspectable through the public repositories, format specification, tests, and release history.
Project links:
- Website: https://tzap.org
- Reference implementation: https://github.com/tzap-org/tzap
- GitHub organization: https://github.com/tzap-org
It is built for archives people may need to trust years from now: private datasets, source records, media libraries, research data, legal material, and cold backups.
One command should be enough. No stitching together tar, compression, encryption, checksums, parity files, split-volume naming, and restore logic by hand.
tzap focuses on:
- Fast compression with Zstandard.
- Encryption for private archive contents, names, metadata, and indexes.
- Explicit plaintext mode for public, recovery-focused archives.
- Authenticated metadata and payloads.
- Reed-Solomon recovery for damaged or missing volumes.
- Split-volume archives for drives, discs, object storage, and offline sets.
- Targeted restores from very large archives without unpacking everything.
- An open specification, open implementation, tests, and fuzz targets.
Why Sponsor
Archives often outlive the computers, cloud accounts, drives, and operating systems that created them. Reliable archive software needs more than a first release; it needs packaging, compatibility fixtures, damage testing, documentation, security review, and steady maintenance.
Sponsorship helps turn tzap from a promising open format into a dependable toolchain that people can actually adopt.
What Funding Supports
- Release engineering: cross-platform builds, checksums, packaging polish, and release notes.
- Compatibility and recovery testing: archive fixtures, damaged-volume cases, random-access restore checks, fuzz targets, and regression coverage.
- Documentation and specification work: user workflows, implementer notes, format revisions, migration guidance, and public examples.
- Maintenance time: issue triage, dependency updates, security reviews, and bug fixes.
Transparency
Open Collective keeps funding visible. The work itself stays inspectable through the public repositories, format specification, tests, and release history.
Project links:
- Website: https://tzap.org
- Reference implementation: https://github.com/tzap-org/tzap
- GitHub organization: https://github.com/tzap-org
Our team
tzaporg
Admin