Full disclosure: I was an early beta tester for Pressmatic and was provided a license key for testing purposes. Screenshots and information in this post may change as the software changes, but this is my 100% honest opinion of the product.
Update: Pressmatic has been acquired by the hosting provider Flywheel, and renamed “Local by Flywheel”. It’s also been made freely available! The rest of this review still holds fairly accurate as the product was virtually unchanged upon acquisition.

My history with development environments is probably like most PHP developers. Always finding something that got us most of the way there, only to have a few shortcomings (or a lot in some cases) that just didn’t make it the most efficient of all work flows. I’ve either used or purchased close to 5 environments in the past few years, including MAMP Pro, Vagrant configurations, DesktopServer, XAAMP, and even just the local versions of the binaries installed with OS X. None of them met my needs to the fullest. MAMP Pro was very close until payment gateways started requiring strong encryption to talk to their APIs (yay!), and MAMP Pro ships with Apache 2.2, which doesn’t support this protocol (TLS 1.2).

Enter Pressmatic


I was hit up by a friend already in the testing group to join in and see what this thing Pressmatic was. The developer of Pressmatic was looking for developers to use it out and see if it met their needs for local Development. I was pumped to try something new, but pretty skeptical that it would be right, as most things aren’t perfect. Pressmatic was pretty damn close to perfect. I won’t go into the nitty gritty details as those are on the site, and are pretty boring…but here’s some of the highlights that sold me.

Site Defaults

With the `New Site Defaults` setting, you can define all of the basic setup information for when you create a site. You have the opportunity to change these upon creation, but it will be pre-filled with this info. saves me so much time when I quickly need a WordPress install.

Multisite Support

When setting up a new site, you have the option to choose if you want multisite, and not just subdirectory support either!

Nginx, Apache, PHP versions, oh my!

You have the ability to use (and swap out at any time) either Apache or Nginx as your web server, and you also can choose from 5 versions of PHP (at the time of writing 5.2.4, 5.2.17, 5.3.29, 5.6.20, and 7.0.3).

Site templates

Do you have a base install that you use for every new WordPress development environment? Me too. Anytime I work locally I install a handful of plugins, and with site templates, it’s done for me. Basically how it works is you setup what you want your template to look like, and then you can tell Pressmatic to make it a template. Then when adding a new site, you can choose it as an option and a few minutes later, you’re up and running without having to install any of those utilities. It’s beautiful.

Don’t want WordPress? That’s fine, I’ve made a non-WordPress template, by basically creating a base WordPress install, deleting all the parts of WordPress, and making a template out of it. Now I just have a quick an easy site that’s ready with PHP and MySQL based off Apache or Nginx.


This is the first time I’ve worked with Mailcatcher, and it’s amazing. Many times I’ll use email addresses that aren’t valid, in order to test things on my local environments. Things like admin@local.dev or customer@local.dev. Obviously these won’t get sent to me, so when I want to test what emails look like when they arrive I have to configure a real email address, which ends up cluttering my inbox. I hate that. Mailcatcher, is basically a local loopback for emails sent via your sites.
This essentially gives us an inbox for all the emails that the site sends, in a single window. Beautiful!

One-click, Self-Signed Certificate Trusting

This is a huge one I didn’t even know I was missing. Being that I develop a lot of code that’s eCommerce based, thanks to Easy Digital Downloads, I tend to always want my local development environments to be over HTTPS with a self-signed certificate. When doing this in MAMP, I’d always be met with the ‘Do you want to trust this certificate!?!?!?’ warning in Chrome and other browsers. Well, Pressmatic made this easy, with a single click.
After ‘trusting’ the cert, I can be fully HTTPS locally without any weird warnings.

Other things I like:

  • Ability to set the default terminal app.
  • One click access to SSH and MySQL for any single site
  • Add-On management (not many available now, but in the works)
  • Automatic Updates to the application
  • Quick site duplication

So, overwhelmingly a positive experience. As always there are some things I am either missing aren’t quite what I expect, but that list is pretty small, and a bit picky if you ask me…

A few things to improve on:

  • Does not have the ability to change the path to the web root on an existing site.
  • Cannot pick WordPress version at new site creation, some sites I like to run nightly.
  • WordPress debug constants are not set on installation (but I hear an add-on is coming for that).
  • It’s only OS X (for now)

Those are the only ones I can think of at the moment. Pretty small eh? So far this is the most comprehensive change to my development environment in a while, and it’s pretty much changed it completely. The speed at which I can replicate, create, and destroy sites makes my testing and development much faster and efficient, and repeatable. Which is key.

The features of Pressmatic allow me to test and replicate environments much faster. Click To Tweet

The precieved elephant in the room…price

Pressmatic comes in at $129. There are no renewals with Pressmatic. Licenses are valid for all 1.X releases and you will be able to upgrade at a discount when new major versions are released. This is a pretty standard platform. MAMP has been using it for years with its Pro version.

One might argue that MAMP Pro is only $59, and you are 100% right. You also get what you pay for. MAMP is running outdated software versions, doesn’t have the template features, and isn’t geared towards WordPress development, which I feel is a huge selling point here. The other major improvement this has over other ones I’ve used is it’s design. It’s just clean, and easy to use as a native OS X app. It’s also not running in such a container platform, which is a huge benefit in my opinion. You have to approach financial decisions about development tools with one thing in mind: “How much time will this save me.” The answer with Pressmatic, is a ton.

Posted by Chris Klosowski

Chris Klosowski is the Director of Technology at Sandhills Development, LLC, creators of fine WordPress plugins, and ecommerce solutions.


  1. This looks really good. How did you find the ram consumtion when running it comapred to Vagrant?

    Have you switched to it as your main development envoirnment?

    Is it possible to share the envoirnment template with your coworkers so that you are all using the same envoirnment?


    1. @ulrich

      As far as RAM Consumption I don’t notice an uptick or impact to performance. I believe (sparing details) it’s using a virtualbox headless to handle the docker containers. Clay might be able to give more detail on that if you ask. I’m on a 2013 11″ MacBook air with 8GB of RAM.

      I’ve changed this over to my main environment yes. My MAMP environment exists solely for me to go grab things I needed that I forgot to move yet.

      You can share your templates. They are located in ~/Application Support/Pressmatic/site-templates. There will be a .zip file with the template name located there and you can share it.


  2. What options are available for deploying the site to the clients server? Right now I am using DesktopServer which has Direct Deploy and Quick Deploy.


    1. At the moment there isn’t a method of doing this like Desktop server does, however I hear there is integrations with some of the more popular site migration solutions in the works.

      Worst case scenario moving from development to a live server is exporting the Database and the files and putting them on the server. Not something terribly difficult.


  3. […] Local WordPress development with Pressmatic. A Review. MAMP Pro, Vagrant, Desktop Server… dad la bienvenida a un nuevo contendiente a la hora de crear entornos de desarrollo para trabajar con WordPress de manera sencilla: Pressmatic. Varios desarrolladores han estado hablando maravillas de esta nueva herramienta (de momento sólo para OS X) y ya hay alguna review. […]


  4. Hi Chris,

    How does this compare to say, Homestead by Laravel? Also, how does it compare to say, vanilla vagrant?


    1. @Leo,

      While I haven’t used Homestead yet, from my quick research the one thing I notice is there isn’t a GUI out of the box? So that’s a major difference, this is a 100% Electron (for OS X anyway) interface to access the features and add-ons.

      As far as Vagrant, I’ve found this far easier to maintain multiple different environments and configurations because of the interface. With single clicks to access the DB, the File System, the SSH etc I find it easier to navigate around to the different projects.

      Performance wise I’ve had zero problems wth this, it’s built around a docker container system via VirtualBox.


  5. Thanks Chris! Just got myself a copy too 🙂


  6. Thanks for the review. I’m currently using Theme Juice which is kind of like Pressmatic/Flywheel, but might switch since Flywheel seems more popular. Does Flywheel do deployments?


  7. Hey I am so thrilled I found your site, I really found you by
    error, while I was searching on Digg for something else,
    Nonetheless I am here now and would just like to say cheers for
    a incredible post and a all round thrilling blog (I also love the theme/design),
    I don’t have time to look over it all at the
    minute but I have bookmarked it and also added in your RSS
    feeds, so when I have time I will be back to read more, Please do keep up the fantastic work.


  8. When someone writes an piece of writing he/she retains
    the plan of a user in his/her mind that how a user can understand it.
    Therefore that’s why this piece of writing is great.



Leave a reply

Your email address will not be published. Required fields are marked *