If you need full infrastructure control, you can self-host the same capability model used by soul-upload.com.
Core components
- API runtime for backup upload, download redirect, and delete endpoints
- Object storage for encrypted backup files (with public read access)
- Relational index for backup metadata
Required behaviors
- Accept single file upload (encrypted tar.gz, e.g. openssl)
- Store in object storage with predictable key
- Return stable download URL
- Support deletion by backup ID
noindex, nofollow on download endpoints
Minimal schema
backups(backup_id, object_key, size_bytes, sha256, created_at)
Deployment notes
- Configure object storage for public read access
- Keep R2 public URL in environment config
- Audit logs for frequent 4xx/5xx responses
- Add lifecycle and retention controls before scale-up
When to self-host vs use hosted
- Self-host if compliance or data residency is mandatory
- Use hosted if operational simplicity is the priority
Next reading