--- title: "MotherDuck acquires Tower.dev" url: https://daily.dev/posts/motherduck-acquires-tower-dev-n8be1sjcl source_url: https://motherduck.com/blog/motherduck-acquires-tower type: article source: "MotherDuck" published: 2026-08-25T14:33:40.191Z updated: 2026-08-25T14:35:30.280Z tags: ["devops", "ai-agents", "data-engineering", "acquisition"] reading_time: 3 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # MotherDuck acquires Tower.dev **[MotherDuck](https://daily.dev/sources/motherduck)** · 3 min read · 1 upvotes · 0 comments ## Summary MotherDuck has acquired Tower Computing Inc., the runtime infrastructure provider that already powers its Flights feature for hosting, scheduling, and orchestrating LLM-written data pipelines. Tower supplies sandboxing, scheduling, and observability that MotherDuck used to launch Flights quickly. With the acquisition, MotherDuck plans to expand Flights into data agents and expose Tower jobs as stable URLs, turning pipelines into callable data APIs that can be combined with MotherDuck Dives (its data visualization tool) to build full applications from a single prompt. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What does MotherDuck's acquisition of Tower.dev mean for its Flights feature? MotherDuck acquired Tower Computing Inc. to expand its Flights feature, which hosts, schedules, and orchestrates LLM-written data pipelines. Tower already provided the sandboxing, scheduling, and observability behind Flights, and the acquisition lets MotherDuck evolve Flights into data agents and expose Tower jobs as stable URLs, turning pipelines into callable data APIs. _Track how data warehouses are absorbing agent tooling like this on daily.dev._ ### How can I combine MotherDuck Flights and Dives to build an application from a prompt? A Flight can handle data ingestion and modification (for example, letting users add their own recommendations), while a Dive provides hosted data visualization (like a map of those recommendations). Combining a Flight for write access with a Dive for visualization lets you build a rich, secure, scalable application from a single prompt, according to MotherDuck's own example. _Developers piecing together agent-built data apps follow tooling shifts like this on daily.dev._ ## Similar posts on daily.dev - [Introducing Flights: Agent-Native Ingest in MotherDuck](https://daily.dev/posts/introducing-flights-agent-native-ingest-in-motherduck-ztnhq0181) · MotherDuck · 4 upvotes · 0 comments - [Flight Plans: Templates for AI-Native Data Pipelines](https://daily.dev/posts/flight-plans-templates-for-ai-native-data-pipelines-ddyz3xd88) · MotherDuck · 0 upvotes · 0 comments - [What if a full data pipeline was one prompt away?](https://daily.dev/posts/what-if-a-full-data-pipeline-was-one-prompt-away--ijzjm147i) · MotherDuck · 0 upvotes · 0 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#ai-agents](https://daily.dev/tags/ai-agents), [#data-engineering](https://daily.dev/tags/data-engineering), [#acquisition](https://daily.dev/tags/acquisition) [View this post on daily.dev](https://daily.dev/posts/motherduck-acquires-tower-dev-n8be1sjcl)