Skip to content

Business

TSR in your company’s workflows

The same compression, where your servers work: a command line for scripts, a service to read archives over the network, a C library for your own programs, Linux packages and containers.

The value

Storage is bought every year. The ratio, once.

Every copy of a piece of data pays its compression ratio: the primary archive, the backup, the off-site replica, every transfer over the network. A point gained once pays off on every copy, for the whole life of the data.

On office documents TSR goes down to 47.888%, 4.1 points below the best of ten tools. On a petabyte that is forty terabytes less, for every copy you keep: primary, backup, replica. Every year, as long as that data exists.

  • Storage on every tier: disk, tape, cloud.
  • Windows for backup and replication, shorter.
  • Bandwidth to the replica and the cloud, paid by the byte.
  • Access to archives without extracting them, and verification every week.

Integration

Where it plugs in

A command line for scripts

With --json every command writes a single JSON object and nothing else; progress goes to standard error. The nine exit codes are those of the C library: a damaged archive gives 3, to the shell as to the program.

C library, libtsr

Compress, extract and verify from your own programs, through a stable C interface with the same nine error codes as the command line.

Streaming service

tsr serve reads the archive over HTTP with range requests and as a read-only WebDAV volume. By default it listens on the local interface only; beyond it an access secret is mandatory, with caps on connections and bandwidth and transport encryption left to a reverse proxy.

Daemon with a job queue

tsr daemon queues compressions, extractions and verifications behind a local HTTP API, one job at a time. The access secret is always mandatory, and a root folder fences the paths the daemon may touch.

Periodic verification

tsr scrub repeats the deep verification with bandwidth and CPU caps, stops and resumes where it was; a systemd timer runs it once a week.

Packages and containers

.deb and .rpm packages for x86-64 and ARM64, tested by really installing them; a static binary; hardened systemd units; a container image under 3 MB holding only the binary, and one with the graphics card.

Bill of materials

Every package carries the CycloneDX SBOM of its binary, the security policy, the licence and the attributions. All dependencies have permissive licences, none copyleft.

Inside your network

The version for companies works locally and answers only whoever queries it: no automatic updates, no diagnostics, no communication to the outside.

A few commands

tsr c archive.tsr /data --fast --json --quiet
One JSON object on standard output, and nothing else.
tsr x archive.tsr /restore --json --password-file /run/secrets/tsr
The password from a file, never on the command line.
tsr serve /var/lib/tsr/backup.tsr 8080 --bind 127.0.0.1 --token-file /etc/tsr/token
The service behind a reverse proxy, with the secret in a file.
tsr scrub /var/lib/tsr/backup.tsr --banda 20M --cpu 25
The slow check: 20 MB per second and a quarter of the machine.

The trial

Thirty days on your data

The trial runs inside your network, with the version for companies. We leave you the comparison scripts, the dossiers and the bill of materials of every binary: at the end you have a table of your own numbers. If the numbers do not convince you, you have lost an afternoon.

The author follows each trial personally, one at a time, in order of arrival. Write with the subject “TSR trial” and two lines about your data: how many terabytes, which formats, how many copies. We reply with the sample recipe and a date. Licences and terms are agreed on request.

The promise

  • Every archive written today stays readable by every future version of the program.
  • Every file comes back identical byte for byte, or TSR stores it as it is.
  • The graphics card, if any, produces the same bytes as the CPU.

Documents

White paper

The TSR method in sixteen pages: the three ideas, the measurements that support them and the declared perimeter. For those who assess the technology before the product.

Italiano (PDF) · English (PDF)

On request

The commercial dossier, the benchmark dossier with the corpora, commands and machines behind every figure, the contractual framework and the technical dossier, delivered under a non-disclosure agreement. All of them in English too.

Write to us · Security and privacy