Hacker News Reader

The people who need this most are not going to want to use an external MCP server. This is a pretty unusual model for a narrowly scoped product offering like this. I was excited until I realized it’s not something I can run locally.

View on HN

Fair point. For editing local files I'd want local too. Disclosure: I work on Elva, where hosting is deliberate because the use case is a team's own APIs. Agents call the same endpoints teammates test, with access governed in one place rather than on each laptop. It's a tradeoff, not a fit for everything. https://getelva.ai/

I think it's a valid point. A few reasons we went this way. - The teams we're building for don't want to touch DOCX at all. They just want to plug in their agents and move on, so we went for a smooth hosted experience instead of an open-source lib they'd have to set up and tune themselves. - We run a fine-tuned model under the hood, and it needs a GPU, so running it locally isn't really practical for most folks.

I agree privacy matters a lot. Because of that, we offer zero-data retention for teams, and there's also a self-hosted option if you want everything running in your own cloud.

Reply on news.ycombinator.com