LoginSign Up
← Back to all sparks
K

Kinsta

INFRA · APIS
Velocity5.0

Managed WordPress, application and database hosting on Google Cloud with the MyKinsta dashboard

kinsta.com ↗

Kinsta is moving MyKinsta's controls into its API, one surface per month

managed-wordpresshosting-apibot-protectionbackupsobservability
◆Current state
Kinsta's feed is a blog, so releases arrive as truncated posts, but the pattern underneath is consistent: management surfaces that used to require the MyKinsta dashboard keep reappearing in the Kinsta API. Domains, HTTPS, logs, and backups moved in July; visitor analytics — user agents, browsers, request origins — followed in August. Around that sits a year of bot-traffic work and a file manager in the dashboard, and the newest post extends resilience past backups into a named disaster-recovery offering.
◆Where it's heading
The direction is toward WordPress hosting that can be operated entirely programmatically, with MyKinsta as one client among others rather than the control plane. Bot handling and now disaster recovery show the second thread: absorbing operational risk customers would otherwise manage themselves. The blog format hides scope — most posts are teasers — so direction is readable here but the size of any single release is not.
◆Prediction
Expect the next API release to pick off another MyKinsta-only surface on the same roughly monthly rhythm, with the file manager the obvious candidate. How far disaster recovery goes beyond scheduled backups is the open question these posts do not answer.

◆Recent moves

  1. 13d ago

    Go beyond backups with Kinsta disaster recovery

    A named disaster-recovery capability positioned explicitly beyond backups, opened with the 2021 Strasbourg data-centre fire as the motivating case. The post is a teaser, so the mechanism and its recovery guarantees are not visible here; what is visible is Kinsta continuing to take on failure modes customers would otherwise have to plan for themselves.

    View source ↗
  2. 19d ago

    Access more visitor data with the Kinsta API

    The API now reports which user agents and browsers are hitting a WordPress environment and where requests come from. It extends the API from control to observation, and pairs naturally with the bot-traffic tooling Kinsta has been building out since May.

    View source ↗
  3. 1mo ago

    Manage domains, HTTPS, logs, and backups with the Kinsta API

    Domain setup, HTTPS, logs, and backups became API operations rather than dashboard-only tasks. This is the clearest single step in the migration of MyKinsta's control surface into the API.

    View source ↗
  4. 1mo ago

    See exactly where your site’s traffic goes with bot protection

    A follow-up to May's general release of bot protection, adding visibility into where automated traffic actually goes on a site. Controls shipping first and reporting arriving later is the same sequence the API surfaces have followed.

    View source ↗
  5. 2mo ago

    Manage WordPress files in the MyKinsta dashboard

    A file manager inside the MyKinsta dashboard, framed around the reality that config.php is the file people edit most. It removes an SFTP round trip for small edits, and remains a dashboard-only surface the API has not yet picked up.

    View source ↗
  6. 3mo ago

    When bots go bad, Kinsta has your back

    The post that opened Kinsta's bot-traffic thread, arguing the good-bot/bad-bot split no longer holds. Everything in the traffic-control and traffic-reporting line since traces back to this framing.

    View source ↗