I completely agree with this suggestion. For multi-tenant SaaS environments, manual retrieval of database credentials becomes difficult to scale and introduces unnecessary security risks. API-generated temporary access tokens would provide a much safer way for applications and deployment pipelines to access databases when needed. Additionally, API-based credential rotation would help organizations follow security best practices without requiring manual intervention. Event or webhook notifications on application creation would further streamline automation workflows, allowing provisioning systems to react instantly. These enhancements would significantly improve Cloudways' support for modern SaaS architectures while reducing the need to expose long-lived database credentials.

That’s a smart proposal. In multi‑tenant SaaS environments, exposing raw MySQL credentials is risky and hard to automate securely. If Cloudways supported API‑generated temporary tokens, credential rotation via API, and event/webhook triggers on app creation, developers could automate onboarding without ever handling permanent credentials. This would align with modern SaaS security practices, reduce manual steps, and make Cloudways more attractive for teams building scalable, multi‑tenant apps. Posting this in their feature request forum would be a strong way to push for adoption. https://www.greensky-online.com