Droplet resizing limits hinder cost‑optimization for low‑traffic workloads

Goal: Reduce costs for a low‑traffic site

Deploying a single Droplet on the nano plan is attractive for minimal traffic, but the platform’s resizing rules constrain scaling options. Resizing is only permitted within the same family (e.g., nano → micro) and disallows cross‑family changes such as nano → small. Additionally, nano instances are excluded from automated backups and snapshots, and attaching block storage prevents any size transition without detachment or migration.

Constraints & Uncertainty

• Same‑family resizing restriction limits rapid cost‑adjustment when traffic spikes.
• Nano Droplets lack built‑in recovery options, forcing manual backup processes.
• Block storage cannot coexist with a resizing operation, adding operational overhead for even the smallest workloads.

Open Questions

1. Is there a supported method to resize a nano Droplet to a micro while preserving attached block storage, or must storage be migrated first?
2. Will DigitalOcean introduce cross‑family resizing or a dedicated low‑traffic plan that includes backup capabilities?
3. What are the best practices for cost‑saving on low‑traffic workloads if resizing is constrained—e.g., switching to App Platform free tier and managing SSL termination?