MotherDuck

“I've been doing this for five months now," Stan says. "And I can now, with fair confidence, go in and get questions answered.”

“We now have a doctor vibe-coding artifacts and tools that can talk to all the data that the company has, run processes, and then actually go and affect them directly.”

“Having that MCP server will allow them to dig into the data and answer questions for themselves without having to write SQL queries or really fully understand how SQL works.”

“The support from the MotherDuck team has been really valuable. I definitely haven't gotten that level of support with cloud data warehouses I've used in the past. I heavily used Snowflake at previous jobs and the support definitely wasn't as responsive or as knowledgeable with addressing issues.”

“MotherDuck is great with the service accounts. There is no login for a service account. It's just a token. Tokening is just a lot simpler and a lot more secure.”

“Snowflake's role-based access control turned into a nightmare at my previous job—managing all the different user accounts, the roles tied to those user accounts, what they could do at schema, table, and database levels. Not having to do that in MotherDuck has been a total game changer.”

“The more I worked with it, the more I was just like, oh my God, this is so much simpler than working with Snowflake.”

“"This isn't about building for complexity," Kristov notes. "It's about lowering the cost of iteration. When analysts and engineers can work from the same structure — and test ideas just as easily — that's where the edge compounds."”

“"You don't need to be a data engineer to explore ideas," says Charles. "And when you do, you're working from the same logic, the same facts, the same raw source — not someone's interpretation of it."”

“"At first, we planned to limit data access — a ‘walled garden’ with just a few curated metrics," says Charles. "But the opposite happened: our investment analysts — highly technical, but not data engineers — were the ones pushing to access more and more of our data. With most tools, that level of access would be risky. But with MotherDuck and Omni, it was frictionless. They didn't get lost. They got curious."”

“"We went from local to cloud infrastructure by changing two characters," says Charles. "I swapped in ‘md:’ and it just worked.”

““Omni gave analysts a way to explore the system holistically — linking live models, market context, and internal signals without code, training, or handoffs,” explains Charles. “It didn’t ask us to reshape our thinking to fit the tool — it fit the way we already think.””

““MotherDuck is insanely performant, and there’s no infrastructure to manage,” says Charles. “The cost of experimentation is incredibly low — which means we can afford to ask more questions and build more features, faster.””

“Product velocity is a hallmark of any hypercompetitor. MotherDuck & Omni ship product with incredible speed, and that’s why we trust them to move with us.”

“We're a tiny team doing what we think is a large amount of transactions every day, but it really pales in comparison to where we're going," Jones reflects. "We have a lot of comfort knowing that as we level up and need to grow within our data stack, we have a solid foundation.”

“By going with MotherDuck, we've been able to give the team ownership and let them stay in Metabase. We haven't had to make the full dive to a hugely expensive BI suite yet.”

“Before, I was less comfortable doing this," says Mike Moore, product manager at Reflex. "If we were doing this all through our follower databases, that would start to hit and we'd have long load times. Having MotherDuck means we can send reports more frequently and exactly when we want.”

“It's been really easy to take it from a platform that isn't really meant for these business analytics queries and move it to MotherDuck, which is much more suited for it,”

“MotherDuck has let us just focus on the analytics and the roll up, the actual querying portion of it, and has kind of kicked out all of the concerns and time and research on where are we storing this data long term? What about the costs? What about the latency? What about the scale? All of those are sort of afterthoughts now.”

“You'd be surprised — the create table or replace is one of the best tools DuckDB and MotherDuck has provided. It allows us to just shift data around so seamlessly.”

“The amount of data manipulation and transformation we have to do is going to decrease because the models themselves are getting better over time.”

“Our stance is: let's expose as much of the raw information as we can and let the models do the work. This leads to much more interesting analysis vs. trying to predict an endless number of possibilities.”

“The biggest win from using DuckDB locally has been speed of iteration on our dbt stack. Even our CEO Clint, he's a data guy by trade, so he's in there as well. It's really a velocity thing.”

“We couldn't make it work in a production cloud environment,”

“I think the thing that people underestimate is how much data DuckDB and MotherDuck can handle. The gut instinct may be like, I need a BigQuery, I need a Snowflake. But a lot of people would be surprised at how much can fit into these in-process OLAP engines.”