Your logs, folded.
We build compression for your logs and event data. It keeps exactly the facts you need, at a small fraction of the size.
Logs repeat themselves.
Services write the same kinds of lines over and over, all day. You pay to store every one of them, and pay again to move them.
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 compression written for your format. It keeps exactly the facts you need and packs them into a compact record, checked on your own logs.
Discovery
Under NDA, you send us sample logs. We measure them 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, a strict reader for wherever your data lands, and a harness that checks, field by field on your real logs, that the facts going in come back out. If you need logs rebuilt from it, 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.
Case study: BattleBytes Deck Tracker
66.7 MB in. 17.7 KB out.
BattleBytes Deck Tracker, our own app for Hearthstone Battlegrounds players, folds a game’s log into a record on the player’s PC. One 66.7 MB log became a 17.7 KB record, about 1/3,760 of the size, 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
- Matchedfinal placement
The log spends 213 lines on a single minion. The record says it once.
Player names, BattleTags and account IDs never enter the record.
General-purpose compression, which keeps every byte, took the same log to 1.81 MB. The record uses it too, on the facts alone.
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 keep for years. If you need the original bytes too, we plan for that.
- SaaS platforms. Log storage and egress bills that grow with every customer.
- Remote links. Data sent over slow or metered connections.
How we handle your data.
- 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. Anything sent before an NDA is deleted unread.
- Privacy rules built in. You name the fields that identify a person in your data, and your condenser drops or masks them. Our reports hold sizes and counts, never your log lines.
Questions.
- Is it lossless?
- Not byte for byte. It keeps every fact you need, exactly, and the discovery report lists everything that is dropped before you decide. Logs rebuilt from it work the same in your tools. 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.
Start with an email: what your logs are, roughly how much you keep and what you use them for. We sign an NDA, then agree how you send the sample.
Please don’t attach any data to your first email.