Commercial model
You buy it as a managed service,
one site at a time.
How buying works, in four steps
01
Master agreement.
One agreement governs the program: service definitions, SLA framework, security addendum, and the rules every site inherits.
02
Service Order per site.
Ordering a site is one document: configuration, capacity tier, term, and charges. Executing it is notice to proceed.
03
Site Deployment Plan.
The engineering plan of record: survey results, transport composition, engineered availability, and the delivery SLA values, approved by you before they bind, then attached to the Service Order automatically.
04
Acceptance.
Billing begins when the site passes its acceptance tests on production traffic, and each site's term runs from its own acceptance.
How pricing is put together
Pricing is a flat, all-inclusive monthly fee per site covering the deployed edge, the site fabric, the contracted transport tier, and managed services, with a defined upgrade path from the base tier to high-capacity tiers as measured volumes require. The Aggregation Core is ordered once and scales on a published capacity ladder as sites are added, with a contractual commitment that core capacity stays ahead of aggregate site demand.
Changes, additions, and ancillary work are priced from a rate card rather than renegotiated. Third-party pass-through costs above a defined threshold require your pre-approval. Transport commitments are aligned to service terms where commercially practicable, and any material commitment extending beyond a term is identified before deployment.
Why this costs less to run
You stop paying for internet reach this traffic never uses.
Internet access bundles two things into one price: the transport itself, and per-megabit reachability to the entire internet. This traffic goes to two known places, so it needs the first and none of the second. The managed service unbundles the purchase: dedicated transport plus flat private interconnection, and no internet transit on the data path at all.
The AWS saving, step by step
AWS charges less to pull data out of S3 when it leaves on a private connection.
Your program stores data in Amazon S3. Putting data into S3 is free either way. The charge comes when data leaves again, and leaving is exactly what the biggest flow in this program does: training pulls datasets back out of S3 toward the GPU environment, over and over, once per training pass.
If that data leaves over the public internet, AWS bills its internet egress rate. If it leaves over a private connection at the Aggregation Core, AWS bills its private rate, which is roughly a quarter as much. Nothing else about your AWS account changes, and OSI never touches the money: the saving lands directly on your own AWS invoice.
What AWS charges to pull one gigabyte back out of S3
Over the private path
$0.02 / GB
Over the public internet
$0.05 to $0.09 / GB
Same data, same AWS account, two different rates. The difference, about five cents per gigabyte, is money you stop spending the day the private path is live. It shows up as a smaller AWS bill, not as an OSI charge.
A worked example
- 1A busy site sends about 14.2 PB into Amazon S3 in a month.
- 2Training pulls a quarter of it back out of S3, about 3.5 PB.
- 3Over the internet AWS bills that S3 retrieval at roughly $0.07 per GB.
- 4Over the private path AWS bills it at roughly $0.02 per GB.
Saved that month, one site
~$177,000
On your own AWS invoice, repeated every month the site runs, and repeated again for every training pass over the same data.
Try it with your own S3 numbers.
Move the sliders to match your program. The result is the monthly reduction in your own AWS bill.
AWS S3 retrieval savings calculator
Reading every stored byte back once in the month is 100 percent. Multiple training passes over the same data go above 100 percent.
AWS transfer rates shown are public list prices: about $0.02 per GB on a private connection and about $0.09 per GB over the internet. Your contractual AWS pricing governs. The saving lands on your own AWS invoice. OSI service charges are separate and set in the Service Order and rate card.
AWS transfer rates shown are public list prices for US regions. Your contractual AWS pricing governs. OSI service charges are separate and set in the Service Order and rate card.
The same saving at other volumes
How much you save depends on how much of the data you read back.
Read the table across: pick a site size on the left, then pick how much of that month's S3 data training reads back. Reading all of it once would be 100 percent. Every figure is a reduction in your AWS bill for that month.
| Site size | Data stored per month | Saved if 10% is read back | Saved if 25% is read back | Saved if 50% is read back |
|---|---|---|---|---|
| Standard site, 20 TB per day | ~0.6 PB | ~$3,000 | ~$7,500 | ~$15,000 |
| Busy site, one shift a day | ~14.2 PB | ~$71,000 | ~$177,000 | ~$354,000 |
| Busy site, three shifts a day | ~42.5 PB | ~$212,000 | ~$531,000 | ~$1.06M |
Monthly savings, illustrative and rounded, at published AWS list pricing for US regions.
There is a second charge the private path avoids.
At tens of petabytes a month, pushing data in through a public cloud endpoint becomes its own engineering problem. Real designs end up adding transfer acceleration, extra regions, address translation or network processing, replication, or endpoint protection. Each of those is billed per gigabyte, and acceleration-class options alone list near $0.04 per gigabyte. The private path lands traffic straight into the target region with no public endpoint, so most of that never gets bought.
What this does not include
Private-connection port fees are not included in the figures above. They are small against these flows, and your cloud finance team can verify every number here against published list pricing.
Actual savings depend on your contractual cloud pricing, measured volumes, and how often training reads the data back.
Security, in short
- No public internet edge on the customer path at any site; one centrally governed security architecture instead of one review per site.
- Encryption on every transport segment, terminated only at access-controlled aggregation points; key custody, rotation, and audit rights defined in the security addendum.
- Incident notification on defined clocks, personnel and subcontractor controls, and an annual audit right.