Decoded output reconstructs the original input byte-for-byte.
ZCaps
Proprietary lossless compression for controlled systems.
ZCaps is Zetako's symmetric bit-by-bit compression engine for files, payloads and controlled data workflows.
It gives Zetako a proprietary compression layer that can be embedded into sovereign systems without relying entirely on external compression libraries.
Encode and decode follow a reversible bit-level workflow.
Designed to process arbitrary files and payloads.
A proprietary Zetako compression primitive, not a wrapper around third-party codecs.
Why ZCaps exists
Sovereign systems need their own primitives.
Most software stacks depend on general-purpose compression libraries. That is practical, but it also means the compression layer is external, generic and not always aligned with controlled infrastructure requirements.
ZCaps exists to give Zetako a proprietary compression primitive: lossless, reversible, inspectable and designed for integration into systems where data control, verification and ownership matter.
- Own the compression layer instead of only wrapping external libraries.
- Compress files and payloads through a Zetako-controlled engine.
- Decode back to the exact original input.
- Inspect output metadata through the ZCaps envelope.
- Integrate the primitive into broader product lines and partner systems.
How ZCaps works
Bit-level compression with a verifiable envelope.
ZCaps uses a symmetric encode/decode workflow powered by a compact internal matrix model. The engine operates at bit level and writes the result into a ZCaps envelope for controlled storage, decoding and inspection.
Compression is guided by a compact internal matrix profile rather than relying on an external codec library.
The engine encodes and decodes through reversible bit-level operations.
Outputs include method, profile, size metadata and SHA256 integrity references.
If compression is not beneficial, the envelope can store the original payload rather than forcing expansion.
ZCaps format
Inspectable by design.
ZCaps outputs are designed to be inspectable. The CLI can encode a file, decode it back, or inspect a capsule to read its metadata.
Envelope fields
- magic: ZCaps
- version
- method: stored or compressed
- profile_id
- original_size
- payload_size
- sha256_original
- sha256_payload
CLI flow
zcaps encode input output.zcaps zcaps inspect output.zcaps zcaps decode output.zcaps restored.output
Options
-rb, -r64kb, -r128kb, -r256kb, -r1mb, -r2mb, -r4mb Read buffer size -wb, -w64kb, -w128kb, -w256kb, -w1mb, -w2mb, -w4mb Write buffer size -fingerprint Create file fingerprint -showlog Display process information -savelog Save process information to file
Where ZCaps fits
A compression primitive for product integration.
ZCaps is not positioned as a consumer archive utility. It is a proprietary compression primitive that can be embedded into controlled products, private workflows and system-level integrations.
Compress or package controlled files and workspace artifacts where appropriate.
Support blockchain and ledger-oriented compression experiments where byte-exact recovery matters.
Package files with inspectable metadata and reversible decode.
Embed a Zetako-owned compression layer into third-party products or infrastructure.
Use a local, library-independent compressor in controlled environments.
Serve as a base primitive for future compression research and product-specific codecs.
Boundaries
Not a benchmark race.
ZCaps is not presented as a universal replacement for ZIP, ZSTD, LZ4 or Brotli. Those tools are mature and often excellent for general-purpose compression.
ZCaps exists for a different reason: to give Zetako a proprietary, lossless, inspectable compression primitive that can be integrated into controlled systems.
Some files are already dense or compressed. ZCaps can use stored mode when compression is not beneficial.
ZCaps does not replace encryption, signatures or access control.
The focus is integration, verification and system control.
ZCaps is a Zetako-owned compression engine, not a UI around external libraries.
Product integration
Bring proprietary compression into your system.
Discuss how ZCaps can be embedded into storage, archival, blockchain, workspace or controlled data workflows.