1. Peter

    I don’t understand the usecase. Really. Can someone explain why i should develop on a local machine? I do all my work on my server.
    And doing a local docker container with wordpress is easy described here: https://docs.docker.com/compose/wordpress/


    • David

      If you create a plugin or theme I’m sure you won’t do this on live server. DevKinsta gives you an in-app MailHog, SSL and MyKinsta integration.


  2. Matt Rock

    Sounds promising. Looking forward to check it out. It took a bit of a struggle getting my local dev (Brew) to play nicely with Big Sur. Might be a thing of the past! Cheers


    • Matt Rock

      Didn’t realize on first read that DevKinsta currently only supports WordPress. I may still have to rely on my current Brew setup for non-WordPress websites, but I can certainly live with that. :)


      • Nick

        I’ve run non-WordPress sites on Flywheel’s Local. Just let it set up a WP site for you, delete everything, and you’ve got a clean slate if you just need the PHP, database, and nginx (or Apache, at least in the case of Local). I’d bet DevKinsta is about the same.

        That being said—if you like your setup, you can keep it!


  3. Naeem Muhammad Noor

    I’ll stick to Local


  4. Gince George

    I have switched to Local by flywheel from WAMP server and I’m loving it.
    Looking forward to trying DevKinsta.


  5. Ilija

    For windows users https://laragon.org is king and version 5 is on its way.


  6. Frank Schmittlein

    You can use ddev (https://www.ddev.com/) and my own extension (https://github.com/fschmittlein/WordPress-Distribution) for WordPress.


  7. John Jim

    This is a brilliant development as the devops workflow becomes seamless.


  8. Alen

    I am, as a Kinsta customer, very happy and excited for this. And, of course, I already installed it (already have Docker installed) but just about to test it. It looks promising, especially after fussing with my local WP/Nginx/MariaDB … :)


  9. Nick

    Looking forward to a real head-to-head with DevKinsta and Local. I’ve been a Local user for quite a while, but Kinsta is a name I trust.


    • John

      yes, I’d also see head-to-head comparisation. just don’t forget to calculate that Local has been developing for 6 years and DevKinsta max ~for 8 months.


  10. Mark Boudreau

    I am not a developer but a business person who has launched a small consulting business and knows just enough about WordPress (I have had a WordPress site in some form since WP 3.0) to get into trouble. I do a lot of the basic maintenance work and testing out of plugins and ideas for new site functionality on my own and then hand it off to my developer to deal with the details and implement the big stuff once I have an idea of what I want. I am also a new Kinsta customer and the workflow from this to the staging server and then live server flows seamlessly and instills confidence in someone like me. Well done in my books.


  11. Ben Turner

    Thanks for writing a great rundown of what DevKinsta has created!

    I wanted to chime in about Docker and in particular Local’s use of Docker. It’s true that older versions of Local made use of Boot2Docker (basically Docker running in a VM). This was done because, at the time, Docker’s support on non *nix operating systems was pretty bad.

    Things have definitely improved, and Docker on Windows and Mac has come a long way.

    That being said, Local no longer uses Docker and instead uses native processes for the server software (PHP/MySQL/nginx/Apache)

    We found two main issues with virtualization when Local reached scale:

    Virtualization in general and Docker, in particular, caused a lot of frustration during the onboarding experience
    The performance of virtualized software never reached the same performance as native processes

    For more details on why Local went this route, see this tweetstorm as well as this post within the Local Community Forums:




Comments are closed.

%d bloggers like this: