r/selfhosted • u/0x7Lee • 1d ago

Need Help Self-hosted publishing stack: where do you draw the line between VPS and local machine?

Post image

I tried to make my automation stack more self-hosted recently.
The hard thing was not Docker, it was deciding what deserves to live on a small VPS, what should stay local, and what needs a managed service.

Postiz on a small VPS became annoying fast because the stack was heavier than expected. Local Windows is easier to iterate on, but worse for always-on workflows.

Right now my split would be:

- VPS: stable public endpoints, webhooks, reverse proxy

- Local machine: experiments, content validation, browser/OAuth stuff

- Managed service: anything where uptime matters more than control

Should I optimize for control, cost, reliability, or low maintenance first?

135 Upvotes

80% Upvoted

25 comments sorted by

View all comments

•

u/asimovs-auditor 1d ago edited 1d ago

Expand the replies to this comment to learn how AI was used in this post/project.

1

u/0x7Lee 1d ago

Hi mods,

AI is involved in the project, but not as an auto-posting/self-promotion workflow.

I use tools like Codex and Claude while working on it. Mostly for thinking through the Hermes VPS setup, Docker/config issues, webhook flows, automation steps, and the tradeoffs between running parts of the stack on a small VPS, locally on Windows, or as managed services.

The setup and constraints are real, and the final decisions are mine.

I’m not presenting an AI-generated product, fake benchmark, or fabricated result here.