Keeping customer nightly jobs cheap and reliable
A real solo SaaS setup runs one on a single VPS to process each customer’s data every night. The setup is simple and low-cost while it works, but failures are not being caught through logs. The operator sometimes finds out only after a customer reports a problem.
and Redis are being considered as a way to move the work into a queue, but the goal is to avoid turning a small into a $500-per-month setup. The core issue is how to make repeated customer jobs more reliable without adding too much cost or complexity.
Key points
- One VPS is running nightly work for each customer.
- The depends on a single .
- Failures are discovered through customers instead of logs.
- and Redis are being considered for a queue-based setup.
- The main constraint is keeping the reliable without reaching about $500 per month.