# MotherDuck Acquires Tower: Agents Can Answer. Now They Can Build.

> Source: <https://motherduck.com/blog/motherduck-acquires-tower>
> Published: 2026-08-25 00:00:00+00:00

I’m excited to announce that MotherDuck has acquired Tower Computing Inc. Tower provides runtime infrastructure for data engineering tasks, and is ideally situated to help AI agents and vibe-coded pipelines run data engineering tasks. Tower powers MotherDuck Flights, our mechanism that makes rich data pipelines only a prompt away. The acquisition will enable MotherDuck to give Flights wings, by turning them into Data APIs and orchestrating data agents.

I’ve known Tower co-Founder Serhii Sokolenko since we worked together at Google. He was one of the most impressive PMs I had ever met. Serhii went on to Snowflake, where he met his Tower co-founder, Brad Heller. When I heard Serhii was starting Tower, initially I was disappointed because that meant I wouldn’t be able to hire him to work at MotherDuck. But I kept tabs on what Tower was up to. Brad was equally impressive as a technology leader and put together a strong technical team who proved they could move fast and ship.

The choice to use Tower’s technology for MotherDuck actually goes back before Flights; we were originally looking to whitelist a tool to help our customers ingest data more easily into MotherDuck. After all, if you can’t get your data in, it doesn’t matter how great the data warehouse is.

When AI suddenly became relevant for data teams, we realized we were thinking about the data-ingestion problem incorrectly. We didn’t need canned connectors; Claude can write the code to move data from one place to another. We shipped the ability to host, orchestrate, and schedule your LLM-written data pipelines as our Flights feature.

The parts that Claude didn’t provide-- the sandboxing, scheduling, and observability-- were exactly the functionality that Tower provided. By building on top of Tower, we were able to launch Flights in only a matter of weeks without compromising on features like observability and reliability.

Tower’s runtime will also allow us to evolve our Flights to provide flexible and robust data agents to our customers. Running a data ingestion pipeline isn’t fundamentally different from running a data cleaning or data investigation agent, so it feels like a natural next step to use Tower as an agent orchestrator. The infrastructure the Team has built will make it faster and simpler to launch these new capabilities.

The Tower feature that I’m especially excited about is the ability for a Tower job to expose a stable URL, making it callable from anywhere. What this means is that a MotherDuck Flight can become a custom data API. Moreover, if you combine this with MotherDuck Dives, our hosted data visualization technology, you can build a full-blown application with a single prompt.

To make it concrete, imagine that you’re building an app that lets you visualize user restaurant recommendations on a map; you can build a great Dive for that. But then let’s say you want your users to be able to add their own recommendations; you’d create a Flight that allows creation and modification of their own recommendations. By putting Flights and Dives together, you can build rich, secure, scalable applications.

Earlier this year, I predicted a future in which data engineering becomes an agent supervision problem. Tower will let us surf the wave of data agents by providing the platform on top of which the agents run. Then our customers can go further, faster, funner, and with more ducks.

If you’d like to give MotherDuck a try, you can sign up yourself on the site, or direct your favorite agent to https://new.motherduck.com/.
