A thank-you + one honest ask for the people who built Soup with me 🙏

[MakazhanAlpamys]

Hey everyone — Soup wouldn't be where it is without the people in this thread, and before I make a few product decisions I'd rather hear it straight from you than guess.

You're the folks who've actually been inside the code:

• @Deadpool2000 — Docker support, soup bench, soup cost, the doctor RAM/disk + --nccl checks. Honestly a huge chunk of the ops surface is yours.
• @csking101 — the FP8 rowwise recipes + the DPO example config & tests.
• @gittihub-jpg — the --track-energy → bom emit wiring and the soup build dotted-path transforms, both this month.
• @shivam2931120 — tokenized repetition scoring for the echo-trap detector.
• @VIVAAN-DHAWAN — the safetensors magic-bytes check that stops a malicious pickle sneaking in as weights.
• @mzl2233 — guarding the diagnose gate on distributed worker ranks (a real multi-GPU edge case).
• @huazi-007 — the cmaes-merge base-model caching fix.
• @dreamer0129 — catching the Rich-markup escaping bug in the legacy adapters commands.
• @Miriam-R-coder — taking on the real-time tool-outputs capture.
• @oasis-parzival — the synthetic-data-gen example + the DeepSeek-V3 GRPO recipe.

Quick one, genuinely not a sales pitch — I'm just deciding where the next month of work goes. Gut answers, one line each is perfect:

1. Are you running Soup on anything that actually matters — work / a product / a client — or mostly experiments right now?
2. The scariest part of fine-tuning was never the training — it's a new checkpoint quietly getting worse and nobody noticing until it's in prod. Soup's eval gate is built to catch that and block the bad model from shipping. If Soup could guarantee a bad checkpoint never reaches prod — is that something you'd pay for, or is free-and-good-enough the only version you'd ever use? Straight answer, even "I'd never pay" is gold.

Reply right here whenever. Thank you all — genuinely 🙏

[Deadpool2000]

Ahh... Thanks @MakazhanAlpamys for the mention 🙌 Really appreciate it!

Now talk about your questions -

1. Right now I'm mostly using Soup for experimentation, but I see strong long-term product potential. The features we're building and contributing toward could definitely evolve into something production-ready for real market use as the ecosystem matures.

2. Personally, I think the core capability should remain free because it's part of an open-source project. That said, I'd absolutely support a paid model around managed services, enterprise features, hosted infrastructure, or production guarantees. Many successful open-source projects like Frappe follow that approach.

In my experience, people often don't fully value or seriously adopt something that's entirely free, while a paid service with clear added value can increase trust and commitment without taking away from the open-source project.

[MakazhanAlpamys]

This is exactly the kind of straight answer I was hoping for — thank you @Deadpool2000 🙏

You nailed where my head's at: the CLI core stays free and open, always. The paid tier would be the production-guarantee layer on top — hosted eval gates, managed runs, the "this bad checkpoint never reaches prod" promise as a service. Frappe's a great reference point, I'll dig into how they structured it.

And totally agree on the "free isn't valued" trap — that's been my worry too. Really appreciate you taking the time to think it through, means a lot coming from you given how much of Soup you've built. 🙌

[Deadpool2000]

Really appreciate that!

I think that approach makes a lot of sense. Keeping the CLI and core functionality free while offering production-grade guarantees and managed services as a paid layer feels like a sustainable model for both the community and businesses.

Excited to see where Soup goes next, and happy to keep contributing wherever I can.

[Ercaner1988]

What you're building here is an absolute gem for the community, whether people realize it yet or not. With how fast Big Tech is moving, having accessible, open-source tooling is essential for keeping development democratized. Alongside tools like Unsloth, Soup feels like one of the most promising projects out there for lowering the barrier to entry and keeping knowledge accessible.

That said, an open-source repo can’t do everything, and maintainers shouldn’t have to carry the burden of hand-holding every user or solving edge cases on their own. People are still going to need hands-on technical guidance and proper compute/hardware to run this effectively. That's why @Deadpool2000's proposal makes a lot of sense—it fills that operational gap without putting all the weight back on the core devs.