For small client projects, reliability matters more than fancy infrastructure.
So instead of migrating everything to complex environments, I improved my existing setup:
- PostgreSQL on VPS via Coolify
- Automated daily backups to Cloudflare R2
- Uptime monitoring using Uptime Kuma
- Restore testing process
- Vercel free tier for frontend hosting
Total additional infrastructure cost: Almost negligible.
But reliability improved massively.
The Golden Rule of Backups
A backup strategy is incomplete until you test restore.
Most developers automate backups. Very few actually verify recovery. If you haven't restored it, you don't have a backup.
Small App Checklist for Small Production Apps
- [x] Offsite backups: Copy backups away from the primary server.
- [x] Daily automation: Don't rely on manual triggers.
- [x] Monitoring alerts: Get notified instantly via Discord, Slack, or Email.
- [x] Monthly restore testing: Keep verification routine.
- [x] Low operational overhead: Maximize margins and simplicity.
Simplicity First
I think a lot of developers overengineer infrastructure too early. Especially for small business apps, you probably don’t need:
- Kubernetes
- Multi-region replicas
- Expensive managed databases
You mainly need to guarantee one thing: "Don't lose client data."
This focus changes how you design systems. Simplicity and margins first.
#PostgreSQL #DevOps #WebDevelopment #SaaS #BuildInPublic