Hacker News Reader

> And hire 2 or 3 dev ops to keep it running

Not a devops but I'd say one full time is already too many.

Yes but zero is not enough and where do you get a fraction of a competent dev op from?

From the other dev-op work you’re doing.

Understood but sharing your existing devops resources with this will soon become a bottleneck especially when any major downtime will keep several engineers (and long-running agents) blocked from any meaningful work until availability improves.

Not my experience, from an SMB that maintains its own hardware and services. You have a certain contingent of competent engineers who distribute their work across projects, and it generally works out fine. Or course you plan with some redundancy and fall-back plans in your systems.

The top poster mentioned LLM spend of millions/month to justify the estimated capex of $6m to self-host Kimi on own infra.

Add to this number another $1.5m/yr in opex, so not sure I’d call such an enterprise wealthy enough to spend those kinds of sums on LLMs an “SMB”.

Now you're thinking like management!

colocate and split the cost with others.

Reply on news.ycombinator.com