Three native profiles
Choose your search budget.
Fast bounds the work. Ratio compares fast with PPM. Full searches the active native encoder families and keeps the smallest eligible, verified candidate.
Capability contract
What every workload gets.
No special cases.
One byte-preserving contract across text, structured records, media, telemetry, firmware and archives. These are the capabilities we publish, with their actual limits.
Sparse-byte representation
A route for zero-heavy data.
The sparse mode is an eligible candidate in the native and TypeScript full tournaments. It is kept only when its complete verified frame is smaller than the alternatives.
SAAR v7 objects
A complete object, not a loose payload.
The container records the original length, metadata, payload and an SHA-256 envelope digest. When compression does not help, stored bytes remain a valid fallback.
SAST v3 streams
Bounded chunks. Parallel batches.
The native CLI processes chunks independently, verifies the ordered stream transcript, and can run chunk batches on multiple workers. This is an architecture capability—not a TB/s claim.
Exact recovery
Return the original bytes.
Lossless means byte-for-byte recovery. Saar checks decoded output before accepting encoded candidates; container and stream checks detect corruption, not sender identity.
Formats and limits
Bounded by design.
Object and stream formats, integrity checks and hard limits — the parts you build against.
SAAR v7
Bounded objects of up to 16 MiB. Longer inputs are split into independent chunks, never silently truncated.
SAST v3
Chunks bounded at 16 MiB with up to 64 workers. SAST v2 remains readable for compatibility.
SHA-256 envelope and stream transcript checks
An envelope digest and an ordered stream transcript detect corruption. They are not encryption, authentication or sender identity.
The original bytes
A successful decode reproduces the source exactly. When compression does not help, the stored frame is still a valid, fully recoverable object.
Integration surfaces
One contract, several boundaries.
Implementations and their honest release status. Source present is not the same as released and validated.
Implemented · evaluation
Native C API
Embed the checked C11 library or use its native command-line interface. Object calls are bounded; use the stream CLI for larger inputs.
Implemented · source package
TypeScript API
Use the TypeScript compressor and stream helpers directly in Node.js applications. Published package distribution is not currently enabled.
Implemented · evaluation
Native CLI
Pipe objects and SAST streams through the checked native executable, with exact output verification and explicit resource limits.
Source present · release validation pending
MCP server
A source wrapper connects an agent tool to the native engine. Public distribution and end-to-end release validation are pending.
Source present · Marketplace release pending
VS Code extension
A source extension exposes file commands through the native executable. Marketplace publication and release acceptance are pending.
Workload roster
31 workload classes.
Every bounded byte sequence can enter an object or stream and recover exactly. Specialist routes are added only after byte-exact recovery and a measured gain; the rest remain on the universal route.
Records, sequences, tabular and ledger data.
netCDF, HDF5, DICOM, FASTQ and packet captures.
Build payloads, firmware images and encoded media.
Bounded ordered chunks with a transcript check.
Platform status
Current runtime evidence covers macOS and Linux. Windows has a serial code path but has not completed the runtime acceptance matrix. Signed public artifacts and independent security review are pending. Nothing here is presented as a shipped product.
See it on your data
Where it wins — and where it doesn’t.
Review the recorded evidence, run the bounded live comparison, or bring a representative workload to a scoped evaluation.