Growing shared archive
Retain reusable structure across compatible files rather than treating every file as an isolated archive.
FREE MAC TRIAL · OPTIONAL £4.99 MONTHLY PLAN
GLYX Archive.
Build on every match.
Compression that builds on what you’ve already saved. GLYX reuses information across one growing archive. As it encounters more reusable structure, later matching additions can need dramatically fewer new bytes. That means more room for files, project versions and history—and exact originals back when you need them. Try it with your own files on Mac.
Start your free Mac trial ↗Compatibility and installation information →Discuss a business evaluation →Read the investor presentation →
Apple silicon Mac · macOS 26 or later. Check compatibility and current import limits →
SEE THE DIFFERENCE IN THE RECORDED RESULTS
2,129:1 extra-storage reuse. In a 584-file repeat addition, 1.958 GB needed only 0.920 MB of extra archive and recovery records. All 584 files restored exactly.
Explore the recorded repeat-addition results, including 7,081:1 →These ratios describe the added content. The earlier archive and recovery software remain part of the complete retained system.Watch the completed benchmark film →Discuss licensing →Latest archive/state study →New operation-speed study →
UK patent application GB2624952.4 · Filed 22 October 2026 · Pending
Windows progress: 92 scoped archive and command-line checks reviewed. Full desktop workflow qualification remains in progress.
GROWING ARCHIVE · GROWING REUSE
More reusable structure.
More compression potential.
GLYX’s opportunity grows with the useful matches in your collection: reuse earlier information, add fewer new bytes and keep more of the work you value.
An archive can become more effective as it grows. Each related addition can extend the reusable foundation for the next. When later data shares more with what GLYX already holds, it can achieve higher reuse ratios while preserving exact recovery.
Think beyond compressing one file at a time. A growing collection can keep benefiting from information retained earlier: more matching structure can mean less extra storage for the next addition. That is the scalable opportunity behind GLYX—more of your history on the same drive, and fewer repeated bytes to store or transfer. Actual ratios follow the reuse found in your data.
How do I use a file in my archive?
Choose the original you need in GLYX and recover it with the compatible app and recovery key. Open the recovered file in your usual software. The rest of your collection can stay archived, and you can add a revised version back to the archive.
Understand structured state → · Understand selective rehydration →This is byte avoidance: reuse information already retained instead of keeping another full representation of the same content. Recover the original files you select when you need them. See how this connects to worlds, rendering and application state →
Archive once.
Restore selectively.
Reuse can improve as compatible content joins the same library. Actual savings depend on the data and the structure that can be retained and reused.
Large-file streaming
Process files in sections, with a bounded working set. Capacity depends on available storage and the qualified platform.
Exact selected restoration
Reconstruct and verify the files you request. Other archived content can remain compact.
Clear savings accounting
Compare original and retained sizes, including the archive and restoration record. Keep backups and app storage visible separately.
THE WORKFLOW
Choose. Archive.
Verify. Restore.
Choose your content
Add individual regular files to your archive. Keep the originals while you check recovery. Files you can add →
Review the retained size
See what was retained and what was saved. Unique data and restoration dependencies remain part of the accounting.
Restore what you need
Select files, choose a destination and verify the exact original bytes. Folder trees, permissions, timestamps and extended attributes are not preserved by this release.
WHAT THE WORK SHOWS
A result you can inspect.
In a matched 4.080 GB growing collection, including repeated inputs, GLYX’s complete recorded recovery kit occupied 1.333 GB versus 3.749 GB for ZIP Deflate 9: 64.4% less retained storage. All 1,171 entries restored exactly in both arms.
Historical engine study: these figures describe that recorded collection and its counted recovery dependencies. They are not a benchmark of the current encrypted Mac download or a forecast for your files.
PUT IT TO WORK
Start with your application.
Keep more related documents and versions in available storage. Savings depend on the reusable information in your files. The free Mac trial lets you check your own additions and recovery before relying on an archive.
Study details and comparisons →GLYX ARCHIVE · FINAL V9 BENCHMARK · 6:59
Every original recovered. See what was retained.
Explore the recorded archive build and compare retained storage with exact-recovery results.
50.109 GB added to one growing archive; all 2,803 entries restored exactly. In the original continuation, archive plus records occupied 13.085 GB; the complete recorded macOS recovery kit, including decoder, Python, dependencies and helpers, occupied 13.188 GB. The corpus includes existing and declared generated data, versions and controls. This demonstrates recoverable retained storage on that corpus; the 50 GB continuation did not include a matched ZIP arm.
Read the transcript
GLYX Archive. One growing archive.
GLYX retains useful structure from earlier files. Later matching data can reuse it and add fewer new bytes.
Watch PDFs, mixed files and related videos enter the same archive. The graphs show cumulative storage and added-batch reuse.
Same files. Same order. Existing PDFs enter the retained archives.
Saved commits show successive PDF batches. Both arms receive identical bytes, order and batches.
The same archive continues from 63 PDFs, retaining earlier structure.
Both archives reach 499 PDFs. Final storage values include every retained pin.
Fresh decoder processes restore the originals. Full bytes, sizes and SHA256 hashes are checked.
All 998 PDF checks exact. GLYX 966.28 MB; Deflate 1,393.95 MB. 30.7% fewer archive bytes on this PDF set.
Next: 66 existing mixed files and eight labelled exact-copy controls. Earlier archived structure remains available.
Real mixed-format files join the same growing archives.
Eight exact-copy controls reuse bytes already retained. Their added-batch ratio is labelled separately.
Fresh decoder processes check all 573 entries in each arm.
All 1,146 mixed-stage restoration checks passed.
Two views of the same measured growing archive.
The earlier eight-copy stage measured 5,144:1 incremental reuse.
Eleven fresh mixed-format files are added.
The broad repeat stage added 1.958 GB for 871,208 retained bytes.
Three existing MP4 files are added unchanged. GLYX video-batch ratio: 1.617:1.
The matched 4.080 GB set uses 67.15% fewer GLYX retained bytes than ZIP Deflate 9, counting the archive and all pins/side files.
1,171 entries per arm. All 2,342 restoration checks exact. Complete kits: 1.333 GB GLYX; 3.749 GB ZIP, recorded macOS basis.
The same archive continues to 50.109 GB in 2,803 logical files. Existing and declared generated data, changes and controls are included.
Two views: retained storage and cumulative compression ratio. Every measured rise and dip is retained.
Existing documents and media join declared structured data, changed versions and entropy controls.
50.109 GB input. 13.085 GB archive plus all pins. The final cumulative archive ratio is 3.829 to one.
All 2,803 original files restored exactly in a fresh decoder process. Sizes, SHA256 hashes and full bytes were checked.
Related versions, structured data and repeated content can offer reuse. Savings depend on the matches found.
Archives, all pins and recovery dependencies count. The 50 GB continuation has no matched ZIP comparison.
On the same nine-file sample, runtime optimisation reduced encoding time by 30% and restoration time by 52% versus predecessor GLYX.
Need a small part of a stored file? GLYX can return supported sections sooner, with exact bytes checked. Full-file restoration stays available.
Nine registered partial reads used 9.86% less time in the same package. Exact output checked; the full-file reader is retained.
In the separate matched comparison, ZIP Deflate 9 and ZIP-LZMA were faster on this sample. Actual verification work differs.
This update adds 105,183 bytes per active installation. The complete nine-file restoration kit is 55,468,540 bytes; archive size is unchanged.
Explore GLYX Archive. Plan a business evaluation.
Beyond Brute Force Systems. Business licensing and paid evaluations. beyondbruteforce.com · hello@beyondbruteforce.com
One verified shared recipe helped three test archives use 14.1% fewer archive and pin bytes. All nine files restored exactly. This was a controlled local trial.
Keeping unchanged recipes once across hub versions made the hub store 56.9% smaller. Catalogues, maps and pins count. Older pins still work.
Including server and client software, the installed update saves 122,056 bytes: 0.0554%. Old rollback adds 280,294 bytes. Automatic global sharing is a future stage.
RECORDED PRIVATE CANDIDATE
742 files.
742 exact restores.
1.651 GB of source content became a 793.6 MB archive and restoration record, compared with a 1.490 GB same-content ZIP.
The recorded candidate was 46.8% smaller than ZIP on this cohort. Runtime and installation storage are additional; this is a private candidate result.
See the comparison →Release & licensing
The free Mac trial is available now: seven days, one supported Mac and 100 GB of cumulative original input, with no payment card or automatic charge. The optional monthly plan is £4.99 for one supported Mac, with no cumulative paid input allowance. Local disk capacity, catalogue and import limits still apply. Sign in to subscribe after activating the current download, and review the monthly terms. Team, business-deployment and OEM arrangements remain available for discussion by email.
Paid writing needs an online permission refresh at least every ten minutes. Compatible archive recovery stays free and offline with the matching GLYX Recovery app and archive key.
A browser edition is planned, with local file processing under assessment. It is not available yet. We are exploring Google Cloud Marketplace as a separate business sales channel; the direct Mac trial does not require an app-store listing.
UK patent application GB2624952.4 was filed on 22 October 2026 and is pending. Gaming interfaces and AI integrations are separate integration work, with their own qualification steps.
Build on what
your archive retains.
Compatible additions can reuse retained structure. These recorded examples use different datasets and denominators.
126 MB added for 51.7 KB extra
Forty new files required 51,712 extra retained bytes for 125,985,692 source bytes: about 2,436:1 for that addition. The existing archive was about 496 MB and still counts. This is not a whole-archive or ZIP ratio.
96.5% smaller than ZIP
A separate generated, related CSV study reached a 541,752-byte archive and restoration record after four imports, versus 15,466,144 bytes for ZIP. Runtime and installation storage are additional. Results depend on the data.
YOUR DATA. MORE POSSIBILITIES.
From personal libraries
to application memory.
The opportunity extends beyond individual files: exact retained records can support other software when their meaning, access and current applicability are handled by that software.
Compact shared libraries
Archive compatible files together and restore just the selected content. Keep retention, backups and recovery within your own policy.
Lower data overhead
Evaluate storage, transfer and repeated-data costs on the same content and access pattern, with restoration work included.
Exact retained records
Explore compact persistence for tool data, structured histories and verified artifacts. Archive restoration supplies data; the application decides what it means and when to use it.
State that can return
Pair exact records with Seed State reconstruction for recovery and repeated state operations in a qualified integration.
Personal use and business licensing
The personal GLYX plan is £4.99 per month for one supported Mac. Start free or sign in to subscribe. The free trial never charges automatically. Business deployment and OEM licensing are discussed separately by email, with terms agreed for the workload.
Paid writing needs an online permission refresh at least every ten minutes. Compatible archive recovery stays free and offline with the matching GLYX Recovery app and archive key.
For a coordinated BBF stack, agree one commercial cost boundary so the same storage or processing saving is charged once.
Compare individual and combined offers →GET STARTED · 13 CHAPTERS
Your first GLYX archive, step by step.
Make more of the storage you already own. This five-minute guide takes you from signup to your first archive, with clear steps for keeping your archive and key safe, checking recovery, and understanding the free trial.
The app demonstration uses an earlier Mac interface and archive format. Follow the current download and release notes for your version. Signup and connection steps are illustrated; the app section is a recorded Mac example. The recorded key export uses an earlier unencrypted format—protect recovery keys and follow the backup options in your installed version.
BUSINESS EVALUATIONS AND LICENSING
Business evaluations.
Licensing for your workload.
Tell us what you want to improve, the platform you use and the result you need. We discuss suitability, evaluation scope and commercial terms privately by email.
Any evaluation fee, licence, support arrangements and delivery commitments are agreed in writing before work begins. Start with a non-confidential outline.
Growing libraries.
Returning state.
Newer October studies connect exact archival persistence to Seed State's qualified reconstruction. A 17 October versioned-data comparison retained 57.3% fewer logical bytes than trained Zstandard, with exact full and selected-range reconstruction.
This is evidence for the tested archive/state component, separate from the 742-file GLYX desktop cohort. Physical allocation, processing time and comparator details are available together.
Read the latest combined study →RECORDED ENGINE STUDY · 19 OCTOBER 2026
22.65% less time.
Exact restoration retained.
In the 19 October engine study, the GLYX candidate completed the repeated-content workload in 894.07 ms versus 1,155.85 ms for the existing engine. Four of six tested workloads qualified for a complete-operation improvement, with median elapsed-time reductions of 14.75–22.65%.
All 1,656 exact-output checks passed, and matched archive sizes were unchanged. The candidate uses more working memory: the largest measured child-process peak was about 129 MB, versus about 34 MB on several baseline workloads. This is a private engine candidate, separate from the installed desktop release.
See all six workloads, timing boundaries and memory →GLYX ARCHIVE · PRODUCT EXPLAINER · 1:38
Reuse compatible structure. Restore the exact files.
Discover how GLYX reuses information across your files and restores the originals.
Read the transcript
Projects change. You need the latest files, and you may need an earlier version later. Keeping that history can mean storing the same information again and again.
GLYX Archive looks for compatible information it can reuse across an archive, while preserving what is needed to recover the original files exactly. Different files can contain familiar structure. New information still needs to be stored.
For you, the benefit is more room for useful files and older versions within the storage you already have. Where you pay for the space retained, reducing that billable amount reduces the storage charge.
In one recorded comparison, we used a selected library of seven hundred and forty-two files. Counting the archive and the recorded restore software, GLYX used about forty-three percent less space than the same files in ZIP. Every file came back exactly.
We also tested adding previously saved content again. In that separate exact-repeat test, adding almost two gigabytes again needed less than one megabyte of extra archive and recovery records. The earlier archive and required software still had to be kept.
The goal is useful storage saving with exact recovery. We compare your real data with the best practical alternative, count everything you need to keep and run, and check that the original files come back exactly.
Bring a backup history or a project library. Compare what you keep, what you can restore and what you pay for.
GLYX Archive. Beyond Brute Force. Reuse structure. Create more.
More to see.
Explore the product films, select a scene and browse 16 earlier public films and updates.