Developer Workflows

Every Kinsta plan includes SSH, SFTP, WP-CLI, and Git, so developers can work the way they’re used to. Here’s which tools fit which jobs, from editing a single file to fully automated deployments.

Connect with SFTP and SSH

Why it matters: SFTP gives you secure access to your site’s files. SSH gives you a command line on the server, where you can run Git, Composer, and WP-CLI.

How to start: Find your connection details in MyKinsta; see SFTP and SSH. For a quick edit without connecting, use the File Manager in MyKinsta.

Manage WordPress from the command line

Why it matters: WP-CLI handles tasks like updating plugins, managing users, and running search and replace far faster than the WordPress dashboard, and it can be scripted.

How to start: Connect over SSH and run wp commands; see WP-CLI.

Deploy with Git and CI/CD

Why it matters: Deploying from version control gives you a history of every change and a repeatable process. It also makes rolling back a bad release straightforward.

How to start: See Git, then set up automated deployments with GitHub Actions, GitLab CI/CD, or Bitbucket Pipelines. Deploy to staging first, then push to live; see Make Changes Safely.

Automate with the Kinsta API

Why it matters: If you manage many sites, repeating the same steps in MyKinsta takes time. The API lets you script tasks such as creating sites, clearing caches, or running backups.

How to start: See Kinsta API and the API reference.

Other tools worth knowing

• Database management: Run queries and edit data directly in MyKinsta.
• Cron jobs: Schedule server-level tasks.
• PHP constants and PHP modules: Check what’s available and configurable on the server.
• New Relic and Blackfire: Use your own monitoring tools alongside Kinsta’s APM.

Watch out for bot protection

If a site’s bot protection is set above the default level, deployment scripts, API integrations, and self-hosted monitors may be blocked. Add an exception for your tools’ IP addresses or user agents; see Protect Your Site.