Storage isn't just storage.
You're paying for every TB many times over - across backups, replication, audit copies, egress, cooling, and energy. The bill compounds quietly every quarter.
Jam storage engine
Jam turns folders, backups, logs, app installs, and repeated snapshots into verified archives. It tests the restore, compares storage modes, and shows the result before you delete or move the live copy.
Already in production
Live revenue customers, healthcare and genomics channels, defence innovation pathways, and hardware ecosystem partners.





How it works
Storage isn't a one-time cost. Every TB you keep gets paid for again - in backups, replication, audit copies, network egress, and energy. Jam shrinks that footprint at the source.
You're paying for every TB many times over - across backups, replication, audit copies, egress, cooling, and energy. The bill compounds quietly every quarter.
Jam packages the selected data, records metadata, tests that it can be restored, and keeps the archive self-contained unless you deliberately choose reference mode.
Send a workload sample. Two weeks later you get a real compression ratio, restore speed, and dollar savings - yours to keep, with no commitment.
The archive modes
The app explains these choices in plain language. Most users start with a self-contained archive. Backup and snapshot users can add a reference folder when they want Jam to store mostly what changed.
Creates a verified archive quickly. Use it for backups, project handoffs, cold storage, and any archive that must restore on another computer.
Best for logs, CSVs, JSON, source trees, telemetry, and structured folders where normal compression performs well.
Use this when you have an older matching backup or snapshot. The archive can be tiny, but restore needs the original reference data.
Jam's internal compressor is available for lab work, but today's app should recommend it only when the user is explicitly testing compression research.
Research lineage
Two papers we reference often: practical lossless compression with latent variables, and the broader thesis that compression reveals reusable structure in complex systems.
The ICLR 2019 BB-ANS paper shaped Jam's early direction: lossless compression, latent-variable modelling, asymmetric numeral systems, and practical parallelization.
Read arXiv:1901.04866The 2026 preprint argues compressibility reveals reusable structure, hierarchy, and useful abstractions across complex knowledge systems.
Read arXiv:2603.20396Benchmark proof
We tested Jam on real local Trading log data arranged as an older snapshot and a newer snapshot with a small changed tail. Every result below was restored and checksum-verified.
Original folder: 53.0 MB. Source: local Trading logs with a small changed tail.
Quick, self-contained backup or handoff.
Text-heavy logs, CSVs, JSON, and structured folders.
New snapshot compared with an older matching snapshot.
Near-duplicate snapshots where the reference remains available.
Reference archives are powerful for backups because they can store mostly what changed. Self-contained archives are safer when you want the archive to restore by itself on any machine.
Managed storage
Roughly 78% below AWS S3 Standard list. S3-compatible API. SOC 2 operationally compliant. Pilots, restore drills, and workload reporting included. Pricing scope excludes request, retrieval, transfer, and tax.
Quick math
Drag the sliders to your workload. List rates are public AWS S3 references; your real bill includes more line items.
Canada / ITB
For primes with Canadian industrial benefit obligations: 94.54% CCV, six emerging-tech KIC mappings, four defence-domain competencies, and structured R1–R5 Value Proposition outcomes.
How it starts
30 minutes. We map your workload, current storage, restore needs, and any procurement context.
We compress a sample of your data and report compression ratio, restore speed, and the dollar number - yours to keep.
Run Jam yourself, or move to Cithorum Cloud at $5/TB-month. No commitment until you've seen the numbers.