Connect over SSH · Kinsta
Connect a WordPress site over SSH: Kinsta
You run Kinsta. Adding WebCrew's SSH key takes ten minutes and unlocks the file-level checks, faster updates with a full restore point, and cleanup help when a site is compromised. The key goes to the site's own user, never root, and you revoke it from your dashboard at any time.
Free for one site. No card. Nothing on the site changes by connecting it.
Step by step
Adding the WebCrew key in Kinsta
Before you start: your WebCrew dashboard open at Add a site → SSH (that is where the public key is), and a login to Kinsta with rights on the site.
Read the SSH details
MyKinsta → Sites → your site → Info. The SFTP/SSH block shows host, port, username and path.
Add the WebCrew key
MyKinsta → your profile (User settings) → SSH keys → Add SSH key. Paste the public key from your WebCrew dashboard.
Note the port
Kinsta uses a non-standard port per site; copy it from the Info page.
Enter host, port, user and path in WebCrew
Path is /www/<site>_<id>/public, as shown on the Info page.
Good to know
Every Kinsta site has its own system user, so the key is scoped to the site by design.
Menu names follow Kinsta's current release. If yours looks different, the same setting lives in the panel's SSH or Security section.
Why SSH
What the key unlocks that the plugin cannot reach
The connector plugin sees what WordPress reports. SSH sees the files themselves.
Plugin and SSH side by side- File-level integrity. Every file compared, not only what WordPress reports; changed and added files listed with their time.
- Restore points at file and database level. The way back covers the whole site, not one plugin.
- Cleanup help when a site is compromised. Changed core files replaced, unknown administrators removed, the plugin that let the attacker in updated or removed, with a restore point before each step. No guarantee it stays clean; no tool can give one.
- Staging copies, when they ship.
Questions
Before you add the key
Does the key give WebCrew root?
No. You add it for the site's own user. WebCrew can do what that user can do in that user's folders, and nothing else. Every action taken over the key is in the site's log.
My host does not allow SSH on my plan.
Use the connector plugin. Monitoring, the security scan, vulnerability matching, updates with a restore point and the assistant all work through it. File-level cleanup then becomes a list of steps for you or the host.
Can I remove the key later?
Yes. Revoke it in your WebCrew dashboard, or delete it in Kinsta. The site keeps running exactly as before; only the deeper checks stop.
Do I still need the connector plugin?
Not for monitoring or updates. Keep it if you want the assistant inside wp-admin later; the two work side by side on one site.
Do I have to install anything besides Kinsta?
One of two things: the WebCrew connector plugin, uploaded in wp-admin like any plugin, or one SSH key for the site's own user. Nothing else changes on the site.
Can I use my own Claude or ChatGPT with a site that runs Kinsta?
Yes. Connect your tool to WebCrew over MCP and ask about the site from your own chat. Reading is instant; changes are made for you, logged, and undone in one click.
What does it cost for a site running Kinsta?
The first site is free, for as long as you like. Every site after that is billed per site per day, monthly, for the days it was on. Plugins are never counted.
Is my content or Kinsta's data used to train anything?
No. Your content is never sold and never used to train a model, by WebCrew or by a provider it uses.
What if Kinsta is a premium plugin with a licence?
It updates through its own licence. WebCrew shows the pending version, takes the restore point first and keeps the code difference, the same as for any other plugin.
Other panels
Not Kinsta? Pick your panel
Add the key now. The first file-level check is done within the hour.
Free for one site. No card.