Developers · Quickstart

From input
to verified output.

The shortest path is a real object and a real stream through the current evaluation surface, followed by an independent byte comparison. No SDK is implied before it is publicly distributed.

Native CLIC11 libraryTypeScript APISAAR v7SAST v3
saar · quickstart
evaluation
$ saar compress input.json
$ saar info input.saar
$ saar decompress input.saar -o restored.json
$ cmp input.json restored.json && echo exact

$ saar_native stream-compress --profile fast \
  --chunk-size 4194304 --threads 8 < input > output.sast

The path

Five steps, no hidden assumptions.

Each step produces a result you can inspect. If access is not agreed, the public live comparison remains the bounded alternative.

Evaluation access

Confirm access

The TypeScript package and native CLI are implemented, but public distribution is not currently enabled. Access is scoped through a technical evaluation.

Three surfaces

Choose a surface

Use the native CLI for streamed files, the native C11 library for embedding, or the TypeScript API for Node.js integration.

Object

Run a bounded object

Compress a small file, inspect the format and verify that the decoded bytes match the source exactly.

Stream

Run a checked stream

Use SAST v3 for larger inputs. The stream is ordered, chunked and verified at the end of the stream.

Your baseline

Reconcile the result

Compare complete output sizes, recovery status, machine, profile and limits. Keep the evidence even if Saar loses.

Verification is the acceptance test

A size result only counts if the decode returns the source bytes exactly. The object envelope and stream transcript also detect corruption. They are not encryption or sender identity.

Next

Go deeper on the surface you chose.

The CLI page covers commands and failure behaviour. The formats page covers object and stream versions.