When PlainShip fits
- Several people need to deploy, roll back or open a shell without editing CI
- You want secrets in a vault instead of spreading deploy keys across workflows
- Schedules and playbooks should live next to releases, not only in Actions cron
- You want one-click rollback and release history in a product UI



