Connecting your hosting: Cloudways, Kinsta, WP Engine and more
Link a hosting account so Destiny Manage can show server details, back up before WordPress updates, and clear the cache when they finish.
6 min read
What connecting a host adds
When a client site is matched to its hosting account, Destiny Manage shows the hosting context on the site (server or environment, primary domain, and PHP version), takes an on-demand host backup automatically before a WordPress update runs, and clears the host cache once the update finishes so checks and visitors see the new version. Everything is scoped to your own account: only your own hosting account and your own websites are used for matching.
Connect Cloudways
Open Manage, then Integrations, and find the Cloudways card. In the Cloudways Platform, open your profile and go to API to create an API key, then paste it here with your Cloudways account email. You never enter your Cloudways password. Once connected, your servers and apps sync and are matched to your monitored websites by domain.
Connect Kinsta
Find the Kinsta card on the Integrations page. In MyKinsta, go to your name, then Company settings, then API Keys, and generate a key. Paste the key here; it identifies your company by itself, so there is nothing else to enter. Live environments are matched to your websites by domain, and staging environments are kept separate.
Connect WP Engine
Find the WP Engine card on the Integrations page. In the WP Engine Portal, open the API Access page and generate credentials, then paste the API username and password here. Production installs are matched to your monitored websites by domain.
Hosts recognised automatically
Some hosts need no connection. When the Destiny Manage connector plugin sees SiteGround's Speed Optimizer, or a site hosted on Hostinger, the site is labelled with its host and its cache is cleared automatically after WordPress updates. There is no API key to enter for these; they work through the plugin already on the site.
Backups, cache, and safe updates
Backup before updates and cache clearing after updates are turned on by default and can be toggled per hosting account on the Integrations page, or overridden per website in that website's Hosting settings. Rollbacks never trigger an extra backup: the pre-update backup already covers that point, and for a full restore the site page links you to the host's own restore screen. Sites that are not on a connected host are never affected by any of this.