Local PC vs VPS for a scheduled Python pipeline handling PII

Context: I've built a Python pipeline that processes client documents through the Anthropic API on a schedule. It handles PII, so I have compliance obligations. Right now it runs manually on my PC; the next phase adds a scheduler and a webhook receiver.

My problem: the plan assumes it runs on my local PC, and that's a bad fit — my internet isn't reliably stable and the machine can't be counted on to stay awake and connected through a busy season. The obvious alternative is a small VPS running everything, with my PC as the dev machine.

Questions: (1) Local vs. VPS for this — what would you do? (2) If VPS, what's the minimum competent setup for handling PII? (3) Anything about running a scheduled, webhook-driven Python pipeline in production that bites people who haven't done it before?

If it matters for #2 — I was leaning toward DigitalOcean, but open to other suggestions.

Thank you in advance. #Rookie

16 comments

Local PC vs VPS for a scheduled Python pipeline handling PII