How to support
- Contribute features, bug fixes, or performance improvements and bench-marking (especially around offline/online store integrations, scalability, and infra).
- Improve documentation.
- Share feedback from production deployments.
- Help review PRs (this is very valuable).
A small brief about your project
Feast is an open-source feature store that sits at the center of modern ML systems. It standardizes how features are defined, stored, and served - bridging offline training and online inference. It enables teams to reuse features, ensure consistency between training and serving, and scale ML systems using existing data infrastructure.
One FOSS maintainer lesson for your younger self
Design for contributors, not just users. Clean abstractions and good docs matter more than clever code if you want a project to grow.
Why do you do it? Why do you bother maintaining a FOSS project?
Because ML infrastructure shouldn’t be reinvented in every company.
Feast solves a real, recurring problem and building it in the open means better ideas, broader adoption, and real impact across teams and industries.
If your repo had a theme song, what would it be?
Harder, Better, Faster, Stronger
(It’s basically what every feature pipeline is trying to become.)
Which file in your project would you most like to set on fire?
secrets.baseline - always cause conflicts
What's your open-source villain origin story?
Started by fixing a small bug… At some point, you stop fixing bugs and start redesigning the system.
If you had to use one emoji to convey what it is like to be a FOSS maintainer, what would it be?
🧩 (You’re constantly fitting together pieces from users, infra, and ideas - while new pieces keep showing up.)
