Reading this paper is free.
AhanaAI Research · November 2026 · AhanaWire
Cut the cloud egress bill: measured results on repetitive operational text
66.8× more data through the same pipe
The first copy of this mix is 469 bytes instead of 31,334.
Measured on repeated operational text. The measured multiple is 66.8102 to 1. October 2026 four-file mix, 31,334 bytes, measured 17–21 October 2026. First copy: AhanaWire 1, the shipping pair, 469 bytes.
208.9× on the next copy
Once the far site already holds the data, the next copy is 150 bytes.
Measured on repeated operational text. The measured multiple is 208.8933 to 1. Same mix. Next copy: AhanaWire 3, 150 bytes, after the far site already holds the data.
47.7× sooner to finish logs on 10 Mbps
Version 1 finishes the log file that many times sooner on a full 10 Mbps pipe.
Measured on repeated operational text. The measured clock is 47.7366 times sooner. October 2026 in-process version 1 clocks, no added round-trip delay. Logs only.
6.7× sooner on 100 Mbps
The same log clock, on a full 100 Mbps pipe.
Measured on repeated operational text. The measured clock is 6.6793 times sooner. October 2026 in-process version 1 clocks, no added round-trip delay. Logs only.
Bytes on the measured mix
First copy and next copy are labeled separately. The highlighted bars are AhanaWire.
Abstract
Repeated operational text — plant logs, agent handoffs, mixed office days, and short chat or captions — still lands on a metered egress bill. On a measured 31,334-byte mix of those shapes, AhanaWire sent a 469-byte first copy and a 150-byte next copy once the far site already held the data. At the published AWS egress rate of $0.09 per GB, a raw terabyte is $90. The first copy of this mix keeps $88.65. The next copy keeps $89.57. On the same bytes, zstd-3 sends 808 every time, gzip-6 sends 960, and lz4-1 sends 1,088. A measured pair moved the mixed day at 271.247 MB/s of original text while the wire carried 0.796 MB/s, and 17,101 of 17,101 jobs restored.
Key results
- The measured mix is 31,334 bytes of repetitive private text. The first copy is 469 bytes, 66.8102 to 1, or 98.5032 percent off the raw size.1
- The next copy, once the far site already holds the data, is 150 bytes, 208.8933 to 1, or 99.5213 percent off the raw size.1
- On the same mix, zstd-3 sends 808 bytes every copy, gzip-6 sends 960, and lz4-1 sends 1,088.1
- At the published AWS internet-egress rate of $0.09 per GB, a raw terabyte is $90. The first copy of this mix keeps $88.65 (the remaining bill is $1.35). The next copy keeps $89.57 (the remaining bill is $0.43).2
- On the next copy, short chat-shaped text keeps $13.49 more per terabyte than zstd-3. A repeated handoff keeps $7.13 more.2
- A measured home pair, 16 clients, about eight seconds, warm next copy, moved the mixed day at 271.247 MB/s of original text while the wire carried 0.796 MB/s. Every job in that run restored.3
- On the saved card, 17,101 of 17,101 requests restored the original bytes.4
Test setup
This paper reports outcomes from the October 2026 AhanaWire customer paper. Every figure below was measured. It does not describe how the frames were built.
The corpus is four files of repetitive private text, quoted both separately and as a sum:
| Shape | Raw size (bytes) |
| Chat, captions, and short turns | 694 |
| Agent handoff | 2,172 |
| Logs and alarms | 12,800 |
| A mixed day, one file | 15,668 |
| The mix (sum) | 31,334 |
Two AhanaWire results are reported for each shape, and they are not interchangeable:
- The first copy is the frame the shipping AhanaWire 1 pair sends when the far site has not yet received this file.
- The next copy is the frame AhanaWire 3 sends once that far site already holds the data and can open the original from what it already has.
The same four files were also passed through zstd-3, gzip-6, and lz4-1. Those tools send the same compressed frame on every copy of the same file.
Dollar figures are not measured bills. They apply the published AWS internet-egress rate of $0.09 per GB to the measured byte counts, using 1,000 GB per terabyte. A raw terabyte at that rate is $90. A second illustration uses $0.02 per GB, a published Direct Connect-style rate.
The speed table is a later timed run on a home pair: 16 concurrent clients, about eight seconds, a warm next copy, and a count of every restored job. The same next-copy wire sizes were also recorded on a MacBook and a Mac Pro. Those hosts are named only as the machines in that run, not as a customer deployment.
Industries mentioned later are matched to these measured text shapes. They are not a separate study of each industry, and they are not a list of customers.
Results
The same mix, on the wire
| What you send | Raw (bytes) | AhanaWire first copy (bytes) | AhanaWire next copy (bytes) | zstd-3, every copy (bytes) | gzip-6, every copy (bytes) | lz4-1, every copy (bytes) |
| Chat, captions, short turns | 694 | 71 | 29 | 133 | 148 | 168 |
| Agent handoff | 2,172 | 108 | 46 | 218 | 232 | 268 |
| Logs and alarms | 12,800 | 85 | 29 | 87 | 143 | 143 |
| A mixed day | 15,668 | 205 | 46 | 370 | 437 | 509 |
| The measured mix | 31,334 | 469 | 150 | 808 | 960 | 1,088 |
On the mix, the first copy is 66.8102 to 1 (98.5032 percent off). The next copy is 208.8933 to 1 (99.5213 percent off). zstd-3 on the same sum is 38.78 to 1 and sends 808 bytes again.
A repeated official log line stays 127 bytes on the first copy and 33 bytes on the next copy at 1 MiB (1,048,576 bytes) and at 16 MiB (16,777,216 bytes). Those same first-copy and next-copy sizes also hold at 64 KiB. At 1 MiB and at 16 MiB, both AhanaWire copies are smaller than zstd-3, gzip-6, and lz4-1 on that line. At 16 MiB, zstd-3 is 1,613 bytes, gzip-6 is 48,890, and lz4-1 is 66,119. The next copy of that 16 MiB line is 508,400 to 1. A terabyte of that line, stored as the 127-byte first frame, is kept as 7.569 MB. A terabyte of the 31,334-byte mix, stored as the 469-byte first frame, is kept as 14.967 GB.
What a terabyte keeps, at $0.09 per GB
These dollar figures illustrate the measured sizes at a published rate. They are not a customer bill.
| Shape | Kept per terabyte, first copy | Kept per terabyte, next copy | Extra versus zstd-3 on the next copy |
| The mix (31,334 bytes) | $88.65 | $89.57 | zstd-3 keeps about $88, because 808 bytes go again |
| Logs and alarms (12,800 bytes) | $89.40 | $89.80 | about $0.40 |
| A mixed day (15,668 bytes) | $88.82 | $89.74 | about $1.90 |
| Agent handoff (2,172 bytes) | $85.52 | $88.09 | $7.13 |
| Chat, captions, short turns (694 bytes) | $80.79 | $86.24 | $13.49 |
The next copy of chat-shaped text is the widest gap versus zstd-3 on this card. At $0.02 per GB, a terabyte of handoffs keeps $19.01.
If a month of text in these shapes were billed at $0.09 per GB, the illustration would be as follows. This table scales the per-terabyte rates above. It is not a measured monthly invoice.
| Monthly text in this shape | Logs, first copy | Handoffs, first copy | Handoff, beyond zstd-3 on the next copy | Chat, beyond zstd-3 on the next copy |
| 10 TB | $894.00 | $855.20 | $71.30 | $134.90 |
| 100 TB | $8,940 | $8,552 | $713 | $1,349 |
The per-terabyte rates in that table are $89.40, $85.52, $7.13, and $13.49. To turn the illustration into a working estimate, count the terabytes that match these shapes, price the link that is actually paid, and count how often the same bytes reach a site that already holds them.
The pair already runs at that size
Sixteen concurrent clients, about eight seconds, warm next copy, every job restored. Original megabytes per second are the reconstructed text. Wire megabytes per second are what crossed the link.
| File | Home jobs/s | Original | Wire | p99 |
| Chat, next copy 29 bytes | 70,972.21 | 49.255 MB/s | 2.058 MB/s | 0.445 ms |
| Handoff, next copy 46 bytes | 48,388.01 | 105.099 MB/s | 2.226 MB/s | 0.909 ms |
| Logs, next copy 29 bytes | 19,367.73 | 247.907 MB/s | 0.562 MB/s | 1.277 ms |
| Mixed, next copy 46 bytes | 17,312.14 | 271.247 MB/s | 0.796 MB/s | 1.548 ms |
Home mixed text moved at 2,169.976 Mbit/s while the wire carried 6.368 Mbit/s, so that run added 2,163.608 Mbit/s of original text to the pipeline. Home logs moved at 1,983.256 Mbit/s onto 4.496 Mbit/s of wire. Resident size on the home pair stayed at 4.9 MB and 3.0 MB. The same next-copy wire sizes — 29, 46, 29, and 46 bytes — were measured on the home pair, a MacBook, and a Mac Pro. On the MacBook, mixed text moved at 155.590 MB/s. On the Mac Pro, mixed text moved at 99.378 MB/s.
Shapes these numbers belong to
The savings above belong to traffic that looks like the measured files, not to a named organization and not to a study of each industry.
- Logs and alarms, $89.40 then $89.80 per terabyte: manufacturing and multi-site plants; utilities, energy, and water; historians and shift archives; building and facility operations; network and security operations on alert and event text; telecom operations; transportation, fleet, and logistics exceptions; retail and hospitality operations; data-center and cloud operations; municipal and public-infrastructure operations.
- Mixed days, $88.82 then $89.74 per terabyte: regional shared services; multi-site operations that move chat, handoffs, and logs together; health, finance, and insurance operations records; public-sector and records offices moving the same docket and schedule text between sites they run.
- Handoffs, $85.52 then $88.09 per terabyte: contact centers; customer-agent platforms; IT and case platforms; insurance claims; healthcare care coordination; legal and finance matter work; professional services delivery.
- Short turns and captions, $80.79 then $86.24 per terabyte: newsroom captions, rundowns, schedules, and playout logs; support transcripts; short operational chat.
Limitations
- The corpus is four files of repetitive private text, totaling 31,334 bytes, plus a repeated official log line at several lengths. Results should not be generalized to already-compressed media, random bytes, or traffic that does not resemble these shapes.
- First-copy and next-copy sizes must be quoted with their conditions. The 150-byte mix is a next copy, after the far site already holds the data. A site that has not yet received the file still takes the first copy, which is 469 bytes on this mix.
- Dollar figures illustrate the published $0.09 per GB internet-egress rate applied to these sizes. They are not a customer invoice, a discounted contract rate, or a price for AhanaWire. Changing the rate changes the dollars. At $0.02 per GB, a terabyte of handoffs keeps $19.01, which is also an illustration.
- The 10 TB and 100 TB rows scale the measured per-terabyte rates. They are not observed monthly bills.
- The home-pair speed table is one timed run: 16 clients, about eight seconds, warm next copy, on the machines named above. It is not a wide-area network test and not a lifetime throughput rating.
- zstd-3, gzip-6, and lz4-1 were measured on these same bytes. This paper does not compare AhanaWire to WAN appliances, and it does not claim a result on traffic those products publish elsewhere.
- Restore counts cover the measured runs, including 17,101 of 17,101 requests on the saved card. That is not a contractual uptime or durability promise.
- Industry lists are shape matches from the October 2026 use-case paper. They are not customers, pilots, or case studies.
How to cite
AhanaAI Research. (2026, November). Cut the cloud egress bill: measured results on repetitive operational text. AhanaAI. https://ahanaai.com/research/cut-the-cloud-egress-bill
Republishing license, $1
Reading this paper is free. A bot that republishes it needs a $1 license. Terms: Republishing license.
Buy the republishing license, $1
data-buy-url is empty until a Stripe Payment Link is added. Do not invent a checkout URL.
Apply to be an enterprise pilot partner
If your traffic looks like the log, the handoff, the mixed day, or the short turn in this paper, we will measure one of your files the same way: first copy, next copy, and the original bytes back.
Apply to be an enterprise pilot partner