≈66.8× more data over the same wire
First send, before any cache exists: every 1 TB of original data goes out as about 15 GB.32
AHANAWIRE / VERSION 3.0
That is the very first send on our measured test link, before any cache exists. On fast links the first send may not shrink; repeats still do. Repeats shrink to about 4.8 GB. At $0.09 per GB of egress, a $90 terabyte costs about $1.35 to send the first time and about $0.43 on repeats. The receiving edge brings back the full original, byte for byte.12
AhanaWire is compression software you run as AW Endpoints on the link you already have. It sends fewer bytes to lower egress and bandwidth cost, and the receiving AW Endpoint restores the original byte for byte.
Effective speedup: 66.8× more data over the same wire on the first send, 208.9× on repeats.3
“Effective” means more original data gets through per byte sent; the link itself does not get faster.
Results vary by data. Try it on yours →
Your infrastructure. Your cache. Your existing link.
Our goal: speed up the internet one device at a time, so existing networks carry more and fewer massive data centers are needed.
TO SCALE · 1 TB, SCALED FROM OUR MEASURED TEST1
Bars are linear. First trip needs no cache; the next trip needs the chunks already at the receiving site. Sources & scope ↓
First send, before any cache exists: every 1 TB of original data goes out as about 15 GB.32
Once the far site already holds the data, 1 TB repeats as about 4.8 GB.3
“Effective” means more original data delivered per byte sent. The link itself does not get faster.
Version 1 finishes repeated log text that many times sooner on a full link.4
The same log clock, on a full link ten times the speed.4
Every byte you move costs money. AhanaWire makes the bytes you move tiny. For high-volume data transfer, that is the job.
Lower the egress bill. Move more data over the same wire. Nothing is lost. It works on data you already send.
$0.43
Egress fees are charged on data leaving your network or cloud. AhanaWire cuts data transfer costs by sending fewer bytes; the receiving AW Endpoint restores the original byte for byte.
A repeat terabyte costs $0.43 instead of $90.5
150 bytes
Smaller than zstd, gzip, and lz4 on the same data, on the first copy and the next.6
17,101
Every job restored. Every damaged frame refused.7
Two AW Endpoints, one at each end of the link you already have. Each one compresses what it sends and restores what it receives, byte for byte. Traffic goes both ways.
A SHORT WALKTHROUGH
Install, send, then bring the original back.
Illustrated sequence—not a live installation.
01 / INSTALL
Start compress and expand together. Each site keeps its own persistent disk cache.
$ docker compose up -d --buildRun after receiving the edge binary.
Your key comes from your account; the signed Linux binary is public.
The egress meter illustrates the measured four-file mix, not a single frame. The speed counter reveals a separate measured reference; it is not timing this animation. Controls pause or replay the sequence. Reduced-motion settings are respected.
Send a repeat terabyte for about $0.43 instead of $90. Every byte on the wire carries about 208.9× more of your original data.52
The first trip stores a densified frame. The next trip sends a short reference, because the other side already holds the chunks and rebuilds the original. The link speed has not changed; each byte on it carries more original data.
Pick a plan and continue to secure Stripe checkout. Every plan starts there, the Free plan and the Pro trial included. A card is kept on file to confirm who you are; the Free plan is never charged. Prices are in US dollars. Applicable sales tax is calculated at checkout from your billing address.
$0
500 GB of data a month, hard cap. Above the cap, traffic passes through uncompressed. No overage charges.
2 AW Endpoints (1 pair) · up to 2 keys
$49/mo
or $490/yr: pay for 10 months, get 12
5 TB of data a month, then $3 per extra TB.
2 AW Endpoints (1 pair) · up to 2 keys
$299/mo
or $2,990/yr: pay for 10 months, get 12
50 TB of data a month, then $2 per extra TB. 14-day free trial.
8 AW Endpoints (4 pairs) · up to 8 keys
$999/mo
or $9,990/yr: pay for 10 months, get 12
250 TB of data a month, then $1 per extra TB.
32 AW Endpoints (16 pairs) · up to 32 keys
Enterprise: over 1 PB a month, custom AW Endpoint and key limits, data volume and support terms. Quoted, from $2,500/mo. Apply to be an enterprise pilot partner.
Cancel any time from your account; the plan runs to the end of the paid period and is not prorated. Overage is billed monthly. The Pro trial needs a card and ends without charge if there is no card on file. After checkout you get an email to set your password, then you sign in and create your keys. Terms · Privacy. Already a customer? Sign in.
Fewer bytes leave your network. That is a smaller egress line.
The bar is the bytes that travel for the same data. The number sits beside the bar.6
On repeats, each byte on the link carries far more of your original data. The bar is that multiple of the link’s own rate, by data shape.102
Frame math filling a link, not a change in the link’s rated speed.
Version 3 is what ships to customers. The first copy is stored. The next copy is short.
The smallest lossless frame for the message. This mix leaves as about 1.5% of its size. The same message sends that frame again.
Tuned for faster links. A protected frame still opens if one half of it is lost.11
The first copy is the version 1 frame. Once that site holds the chunks, the next copy is the short frame, a few dozen bytes on each of these four files.12
It uses the link you already run. Your payload stays on your network.
Each machine runs one compress and one expand. They share a disk on that machine. The frame crosses the link you already have. AhanaAI issues the key once. The payload stays on your network.
Nothing was lost. Every measured job was restored.
Original throughput on one measured pair is the height of the bar. Figures are in the footnote.9
Every job restored; every damaged frame refused.7
Keep the small copy. Open the original later.13
Opens as the full original, byte for byte.
Best case: one long line repeated. It opens as the full line.
Chat, handoffs, and logs each keep a small fraction of their original size.
The same savings idea, on the kinds of text in these files.
Illustrative egress per terabyte on the measured files.52
$89.40 kept on the first copy, $89.80 on the next, per terabyte. Plants, utilities, energy, water, historians, facilities, operations-event text, fleet and logistics exceptions, retail and hospitality operations, and municipal operations.
$88.82, then $89.74 per terabyte. Shared services, multi-site operations, health, finance, insurance, and archive text in this shape.
$85.52, then $88.09 per terabyte. Contact centers, agent platforms, case platforms, claims, care coordination, and matter work. The next copy keeps $7.17 more per terabyte than zstd-3 on this file.
$80.79, then $86.24 per terabyte. Captions, rundowns, schedules, and short operational chat. The next copy keeps $13.62 more per terabyte than zstd-3 on this file.
Every figure on this page comes from measured files and runs, scaled up where noted. Test dates, exact byte counts, and link speeds are in the footnotes below.142
AhanaWire is a compression product that stores a densified first frame and sends a short next frame so the other side can open the original. The goal is to spend less on egress and storage and to carry more original text on the same link.
Every job in the published run restored, and every original in the published tables was restored. That is the measured scope.
About 98.5% less traffic on the first send and about 99.5% less on repeats: 1 TB goes out as about 15 GB, then about 4.8 GB, scaled from a measured 31,334-byte mix (469 bytes first, 150 bytes next). At an illustrative $0.09 per GB, a $90 terabyte costs about $1.35 to send the first time and about $0.43 on repeats. Results vary with data type and how often data repeats.12
One compress and one expand per machine, ports 19752 and 19754, cache on disk, a key issued by AhanaAI, and the payload on the customer network. The signed 3.0.6 install is at https://ahanaai.com/ahanawire/install/.
Pick a plan at https://ahanaai.com/ahanawire/#pricing and continue to Stripe checkout: Free, Starter, Pro with a 14-day free trial, or Scale, monthly or annual. After checkout, set your password from the emailed link, sign in, create a key, and follow the signed 3.0.6 install at https://ahanaai.com/ahanawire/install/. For Enterprise, apply to be an enterprise pilot partner.
For more than the Scale plan covers: over 1 PB a month, custom AW Endpoint and key limits, data volume and support terms. Enterprise is quoted, from $2,500/mo. AhanaAI is also looking for a few companies to test AhanaWire on real traffic and share usage data in return. Self-serve plans start at checkout. This opens an email to jeremiah@ahanaai.com. There is no form inbox on this website.
A first afternoon is the pair on two machines you already run: create a key in your account, put it in a mode-600 file, run the signed 3.0.6 install.sh, and send one original across the link you already have. Start with the installation guide. The signed bundle is at releases/3.0.6, with instructions and the k8s.yaml inside the verified package.
The payload stays on your network. AhanaAI issues a key, not custody of the data.
| File | Jobs/s | Original | Wire | p99 |
|---|---|---|---|---|
| Chat, 29 bytes | 70,972.21 | 49.255 MB/s | 2.058 MB/s | 0.445 ms |
| Handoff, 46 bytes | 48,388.01 | 105.099 MB/s | 2.226 MB/s | 0.909 ms |
| Logs, 29 bytes | 19,367.73 | 247.907 MB/s | 0.562 MB/s | 1.277 ms |
| Mixed, 46 bytes | 17,312.14 | 271.247 MB/s | 0.796 MB/s | 1.548 ms |