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.
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.