Founder here. Thanks for the interest! We built Moose because we were tired of the complexity involved in setting up and maintaining data pipelines.
What makes Moose different is how it simplifies the entire workflow - from ingestion to processing to serving data through APIs. We've found teams spend too much time wiring together different tools rather than focusing on the actual data insights.
The local development experience was a big focus for us. You can instantly test your changes with real data without waiting for deployments. And we've made sure the same code runs identically in production to eliminate those frustrating "works on my machine" moments.
Happy to answer any questions about our technical approach or how we're handling specific use cases. We're particularly interested in hearing about pain points you've experienced with existing data systems or any feedback you might have on Moose.
We are going towards 1.0 from an API perspective, we have just landed what we internally call DMV2 which is the latest iteration of the abstraction level for the api. Think SST / Terraform CDK vertically integrated for Data.
If you are looking to work with Moose in production we would love to chat with you :)
Hi Zephyr! I'm the Head of Engineering at F45 Training. We had early access to moose, and we've been using it in production since last year with thousands of our members. We use moose to manage the backend for LionHeart - our heart rate tracking system in studio. We also use Moose's paid hosting service called Boreal. It's a new product so still a bit rough around the edges - but it has scaled really well for us and the 514 Team has been terrific.
Very cool to see what used to take a team years to build in a simple, intuitive OSS package. Getting a stack like this up and running in 20 lines of python out of the box would have been unthinkable 10 years ago. Congrats to the team. Can't wait to see where you take this!
Honestly, I was just so over the nonstop ETL and data wrangling grind. I just wanted to build stuff that actually shows results and not waste half my day setting up pipelines. That’s how I ended up using Moose in one of my prototypes. It’s been awesome seeing it cut through the noise and let me skip the annoying setup so I can get straight to building features that actually matter. Cool stuff - cheers!
Founder here. Thanks for the interest! We built Moose because we were tired of the complexity involved in setting up and maintaining data pipelines.
What makes Moose different is how it simplifies the entire workflow - from ingestion to processing to serving data through APIs. We've found teams spend too much time wiring together different tools rather than focusing on the actual data insights.
The local development experience was a big focus for us. You can instantly test your changes with real data without waiting for deployments. And we've made sure the same code runs identically in production to eliminate those frustrating "works on my machine" moments.
Happy to answer any questions about our technical approach or how we're handling specific use cases. We're particularly interested in hearing about pain points you've experienced with existing data systems or any feedback you might have on Moose.
Do you guys have examples of people actually using this in production? I'm curious how it scales beyond dev.
We are currently in Production on Boreal https://www.fiveonefour.com/boreal, our hosting solution for Moose with F45 https://f45training.com, a global studio fitness studio brand. We wrote a case study with them here: https://www.fiveonefour.com/blog/case-study-f45. So we Have a 24/7 consumer facing deployment that we have been running for the last 5 months.
We are going towards 1.0 from an API perspective, we have just landed what we internally call DMV2 which is the latest iteration of the abstraction level for the api. Think SST / Terraform CDK vertically integrated for Data.
If you are looking to work with Moose in production we would love to chat with you :)
Hi Zephyr! I'm the Head of Engineering at F45 Training. We had early access to moose, and we've been using it in production since last year with thousands of our members. We use moose to manage the backend for LionHeart - our heart rate tracking system in studio. We also use Moose's paid hosting service called Boreal. It's a new product so still a bit rough around the edges - but it has scaled really well for us and the 514 Team has been terrific.
Does it support Timescale(DB)?
Not yet, but if you are interested in using we could chat and add support for it. We want to expand support eventually for all major OLAP provider.
Very cool to see what used to take a team years to build in a simple, intuitive OSS package. Getting a stack like this up and running in 20 lines of python out of the box would have been unthinkable 10 years ago. Congrats to the team. Can't wait to see where you take this!
Very cool, going to try this in our next internal build sprint :)
I’d brand this OS Tinybird.
;)
Impressive team behind this. Excited to see what they cook up.
I think Moose is onto something—it simplifies data pipelines by abstracting away the complexity. I really like it. Very clever!
Impressive work done by Team!
This is sick, insane shipping speed from these guys
[dead]
[dead]
Honestly, I was just so over the nonstop ETL and data wrangling grind. I just wanted to build stuff that actually shows results and not waste half my day setting up pipelines. That’s how I ended up using Moose in one of my prototypes. It’s been awesome seeing it cut through the noise and let me skip the annoying setup so I can get straight to building features that actually matter. Cool stuff - cheers!