I have used Kinsta for multiple Trellis installs, on sites both bigger (half million visits p/month) and tiny (hundreds p/month).
Here is a list of things they have helped me with when needed:
- Updating the document root
- Helping me understand how to purge individual page caches via get requests
- Modify SSL rules for redirects per domain to work
- Check on DB instances for remnants of incorrect urls
- Troubleshoot staging to live deploys
- Troubleshoot terminal output when the issue was my fault (wrong or missing key/values in vault or host configs)
Some of these things i could do myself, but it’s nice to know when I have to juggle, they are ready to help.
I moved the majority of my work from WP Engine after I found their help desk getting slower and slower and having to ‘escalate’ the issue up the chain (note: to be clear there are very talented people at WP Engine, and they have better than average service, it just became less consistent that you would get a great tech on support)
The SSH access and Remote DB access along with a sane deployment compared to the flaky git based deploys of WP engine helped make the switch (along with some other issues with their ‘secret sauce’ caching on files pushed from live/staging that were deal breakers).
I have nothing but good things to say about the Kinsta team and their willingness to help with admittedly Trellis related issues.