Your logs, folded.
We build compression for your own logs and event data. It keeps exactly the facts you use, at a small fraction of the size.
Most of every log is repetition.
Services write the same kinds of lines over and over, all day. You pay to store them, pay to move them, and wait while they are searched.
General-purpose compression finds repeated bytes. It can’t tell the facts you use from everything around them.
Built for one format. Yours.
General tools have to work on any data. A condenser is written for yours: it keeps exactly the facts you name, packs them tightly and proves it on your own logs.
Discovery
Send us a sample. We measure it and report back with the size you can expect, what is kept and what is dropped. You see a number on your own data before you decide on a build.
Build
We write your condenser: the encoder, a strict reader for wherever the records land, and a test harness that checks every fact, field by field, on your real logs. If you need logs back in their old shape, we build that too.
Run
Formats change. On a monthly retainer we keep your condenser and its checks current, and send you a report each month.
66.7 MB in. 17.7 KB out.
BattleBytes Deck Tracker, our own app for Hearthstone Battlegrounds players, folds each game’s log into a record on the player’s PC. One 66.7 MB log became a 17.7 KB record, about 3,760 times smaller, with every board, shop, fight and result still in it.
Game log 66.7 MB
Record 17.7 KB
We rebuilt the game from its record and compared it with the original.
- 15 of 15boards
- 15 of 15shops
- 14 of 14fight results
- 1 of 1final placement
The log spends 213 lines on a single minion. The record says it once.
Names, BattleTags and account ids never enter the record.
General-purpose compression alone took the same log to 1.81 MB.
Wherever logs pile up.
Game studios
Match logs, telemetry and replays from every session.
Devices and fleets
Event streams from IoT devices, vehicles and kiosks.
Security and audit
Trails you have to keep for years.
SaaS platforms
Log storage and egress bills that grow with every customer.
Remote links
Data sent over slow or metered connections, where every byte costs.
Your data stays yours.
- NDA first. We sign before you send a single line.
- Kept apart. Your sample lives in an access-limited place of its own, never in our code.
- Deleted after. When the work ends, your data is deleted, unless your contract says otherwise.
- Nothing personal leaves. You tell us what identifies a person in your data. Your condenser scrubs it or never copies it. Our reports carry sizes and counts, not records.
Good to know.
- Is it lossless?
- It keeps every fact you name, exactly. What you don’t need is dropped, and the discovery report lists every drop before you decide. If you must keep the original bytes, for an audit or a legal hold, we plan for that from the start.
- What do you need from us?
- A representative sample of your logs, what reads them today and what decisions come from them. Your daily volume, how long you keep logs and what you pay per gigabyte help us show the savings.
- Where does it run?
- Wherever your data starts or lands: in an agent on a device, as a library call in your service, or as a batch job in your pipeline.
Send us a sample.
Tell us what your logs are, roughly how much you keep and what you use them for. We’ll reply with next steps.
Please don’t attach data yet. We sign an NDA first, then set up a private way to send it.