AWS New Carlisle / Project Rainier
FJI source-qualified: four-document gate met, including project-specific government evidence. Qualification evidence and decisions →
Source qualification update · October 16, 2026
WSBT’s May 28, 2024 local report documents a committee recommendation on proposed tax abatement and construction context. It does not establish final approval, current campus capacity or a site-specific Rainier chip count.
Project status: Operating AI infrastructure; campus development continues. Capacity scope: Current comparable IT capacity not established in reviewed profile. How we verify evidence.
← Back to project index- Location
- Indiana / New Carlisle, St. Joseph County
- Readiness
- Operating
- Status
- Operating AI infrastructure; campus development continues
- Company
- Amazon Web Services and Anthropic
- Next milestone
- Indiana-specific delivered compute, utilization and contract economics.
- Reviewed
- October 6, 2026
Expanded analysis · Original disclosures linked below · Amounts in USD · Company claims attributed; analyst interpretations labeled.
The one-minute investment takeaway
New Carlisle provides a concrete link between infrastructure, a named AI customer and a proprietary accelerator platform. AWS supplies Trainium-based compute used by Anthropic. The investor question is whether that integration produces attractive economics after equipment, power, construction and ongoing software costs—not whether the cluster is impressive.
Readiness basis: Classification of evidence in the reviewed profile; strongest documented phase, not full-campus completion. Operating AI infrastructure; campus development continues Readiness source →
What the sources establish
- Operator / company disclosure Customer and compute evidence. Amazon describes Project Rainier as operational with Anthropic workloads and identifies St. Joseph County as one of its sites. Rainier spans multiple U.S. data centers; its nearly half-million Trainium2 chip count is not an Indiana-only inventory. Source ↗
- Operator / company disclosure Development commitment. AWS’s original Indiana announcement described an estimated USD 11 billion investment and a New Carlisle-area campus developed over the next decade. It is a development commitment, not a disclosed Rainier-only budget or a single-year expense. Source ↗
Who receives the money?
Our analysis of the disclosed company roles. Revenue routes below are business-model interpretations, not estimates of booked project revenue.
| Company / exposure | Economic role | What investors need to establish |
|---|---|---|
| Amazon / AMZN | AWS compute services, proprietary accelerator infrastructure and campus investment. | Potential service revenue and efficiency gains sit alongside depreciation, capital spending and operating costs. |
| Anthropic / private | Named workload customer and AI model developer. | Demand is documented, but contract rates, minimum payments and Indiana-specific billed usage are not provided. |
| Semiconductor and networking suppliers | Potential upstream manufacturing and system components. | Using Trainium does not establish a site-specific award to any unnamed public supplier; manufacturing attribution requires separate evidence. |
How financially meaningful is it? Analyst interpretation
Our analysis: Rainier offers AWS a chance to optimize hardware and software together, potentially improving cost per useful workload. That advantage is not the same as a disclosed gross margin. A large customer can accelerate utilization but also concentrates demand. Site-specific economics are unavailable, and Amazon-wide cloud growth cannot be attributed to this campus alone.
Realized compute revenue minus energy, operations, hardware depreciation, software support and infrastructure commitments defines the operating contribution. Proprietary chips matter when lower costs or better throughput create value beyond the development and migration effort.
Illustration: a 20% reduction in compute unit cost improves profit only on the costs it actually affects. If customers receive the entire saving through lower prices, the benefit may appear as competitiveness or demand growth rather than immediate margin expansion.
Milestones that would change the assessment
| Milestone / disclosed target | Evidence to watch |
|---|---|
| Operating evidence | Seek Indiana-specific workload and commissioning disclosures instead of reusing Rainier-wide counts. |
| Contract economics | Look for duration, minimum commitments and billing evidence; active workloads alone do not quantify economic protection. |
| Hardware lifecycle | Track upgrades and usable throughput against replacement spending. A future chip deployment should not be counted as installed today. |
What could break the investment case?
Our analysis: Customer concentration, software adaptation and accelerator obsolescence can weaken returns. A technically efficient cluster may still underperform financially if utilization falls or pricing passes all savings to customers. Power and building expansion may not progress in sync with equipment deployment.
What would change our view?
Our analysis: The thesis weakens if customer usage does not scale with available compute, if migration costs offset the claimed cost advantage, or if rapid replacements shorten asset payback. Evidence of sustained workloads, contract durability and better unit economics would strengthen it.
What remains unknown Not established in this review
No Indiana-only chip inventory, current campus IT load, realized prices, utilization, customer contract economics or project profit is established. Rainier-wide scale, Indiana development spending and Anthropic’s total AWS usage must remain separate.
This is project research, not a valuation model or a buy recommendation. Financial illustrations are assumptions, not management guidance. Review current company filings and valuation before making an investment decision.
Company investor information & quarterly statements
Amazon
Amazon Web Services and Anthropic
Official investor & shareholder information · Quarterly financial statements: Q2 2026 ended2026-06-30
Anthropic: Privately held or subsidiary with no standalone listed quarterly statements; do not invent ticker or investor disclosure.
Corporate disclosures provide company-wide context. They do not establish this project’s revenue, spending, profit, ownership share or operating capacity. Disclosure verification records →