Original Summary

The thing nobody warns you about when you open source the product and let people self-host: your support surface becomes every environment on earth, and you cannot see any of them. With a hosted product, when somebody says it is broken, you look. Logs, config, actual state. With self-hosted you get a screenshot and a description, and the cause is about as likely to be their reverse proxy or their Postgres version as anything you wrote. Three things helped more than I expected. Ship one deployment shape and keep it boring, so there is a compose file people can diff theirs against. Put section for the version and the config that matters, so your first reply is not a request for it. And write the docs failure-first: not how to configure a thing, but if you are seeing this symptom, here is the thing that causes it. I would still do it. The people who self-host are the ones evaluating seriously, and one question from somebody who already has it running is worth ten from people who never got that far. For others doing open source did you end up gating self-host support behind something, or keep it fully open?   submitted by   /u/Slight_Republic_4242 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/28 23:08:03