TwelveLabs raises $100M to bet video deserves its own foundation models

TwelveLabs raises $100M to bet video deserves its own foundation models

Good morning ๐Ÿ‘‹ A $100M round just staked a claim that video needs its own foundation models, not a bolt-on to whatever text model you're already running. Amazon liked the bet enough to write a check into the same deal that made it the preferred cloud.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐ŸŽฌ TwelveLabs raises $100M to bet video deserves its own foundation models

TwelveLabs closed a $100M Series B co-led by NEA and NAVER Ventures, with Amazon among the backers, pushing total funding past $207M. The money locks in two bets: more work on Marengo and Pegasus, the video-native models behind what TwelveLabs calls its "Video Cognition System," and a multiyear AWS deal making it the preferred cloud, with new models launching first on Trainium. That's a real wager, that video deserves dedicated foundation models instead of becoming just another modality Gemini or GPT absorb by default. Amazon writing a check into the same round where it becomes the preferred infra partner tells you who actually wanted this deal closed. Whether Marengo and Pegasus can stay ahead of general multimodal models that get better at video every quarter is the open question, and $100M only buys TwelveLabs time to answer it.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿš€ AI STARTUPS


๐Ÿ›๏ธ POLICY & REGULATION


๐Ÿ› ๏ธ TRY THIS

Give your multi-agent stack a front door before you add a video agent

TwelveLabs just raised $100M on the bet that video needs its own foundation model, not a vision plug-in bolted onto a text agent. If that's right, your agent roster is about to get one more member, and it needs somewhere to live.

1. Stand up a serverless gateway (API Gateway + Lambda works) that path-routes /agents/{agentId} to your existing agents plus a placeholder video agent.

2. Point a standard A2A client at the gateway's single domain and confirm discovery and routing work with zero client-side changes, per AWS's writeup.

3. Give the video agent its own memory store in AgentCore, tagged with tenant and content-type metadata so its context can't bleed into your text agent's retrieval, following this pattern.

4. Fire one query that should route to video and one that shouldn't. If the router guesses wrong, fix the path config before you plug in a real video model.

Prompt: Sketch a serverless A2A gateway with path-based routing for a text agent and a video-understanding agent, plus AgentCore-style memory scoped by tenant and content-type metadata.

Worth a look


๐Ÿ”— QUICK LINKS


That's the signal worth your time today.

Pradeep Perugu

Get inovAIte in your inbox.