# Midjourney’s Hardware Shift and AWS Strategy

Page: https://stenobird.com/podcast/ai-in-business-6751487/midjourney-s-hardware-shift-and-aws-strategy
Text version: https://stenobird.com/podcast/ai-in-business-6751487/midjourney-s-hardware-shift-and-aws-strategy.md
Podcast: [AI in Business](https://stenobird.com/podcast/ai-in-business-6751487)
Published: 2026-06-19T19:03:59+00:00
Episode link: https://rss.com/podcasts/ai-in-business/2928948
Audio file: https://content.rss.com/episodes/365077/2928948/ai-in-business/2026_06_19_18_59_06_10d3b941-73de-4f3a-b81e-c1479d3a2ce5.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/ai-in-business-6751487/episodes/midjourney-s-hardware-shift-and-aws-strategy
Duration seconds: 865

## Resource

In this episode, we discuss Midjourney's surprising pivot to hardware with their full-body ultrasound scanner, a game-changer in preventative healthcare. Additionally, we explore Anthropic's federal ban turning into a marketing narrative, the drama surrounding Amazon's film 'Artificial', and the competitive landscape of AI chips involving AWS, NVIDIA, and Intel. Chapters 00:00 Introduction 00:00 Midjourney's Ultrasound Pivot 00:25 Anthropic's Federal Ban 00:44 Amazon's Film 'Artificial' 00:49 AWS and Tranium Chips 11:32 Intel's Stock Surge Show Links Get the top 80+ AI Models for $8.99 with the AI Box MCP: ⁠⁠ https://aibox.ai /mcp How I Grow and Scale My Business with AI: https://www.skool.com/aihustle Get the AI Chat Daily Newsletter: https://www.aichatdaily.com/newsletter

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/ai-in-business-6751487/episodes/midjourney-s-hardware-shift-and-aws-strategy/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/ai-in-business-6751487/midjourney-s-hardware-shift-and-aws-strategy.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.