After the Acquisition: Flywheel in the New Year

Some WordPress developers and agencies were caught off guard when WP Engine announced it had acquired Flywheel in June last year. Flywheel had quickly become a trusted web hosting company for many that specifically catered to the needs of developers and agencies. For some, they questioned whether such a buyout would change the company culture and whether the good things about Flywheel’s services would be swallowed by WP Engine’s offerings.

The move had also come only a month after Flywheel closed its $15 per month Tiny plan. There was some initial confusion that the two events were linked.

“With any acquisition of this scale, there is going to be an initial wave of confusion, skepticism, and a bit of shock,” said Dusty Davidson, CEO and co-founder. “People had come to know, love, and trust Flywheel, and when it was announced that two well-known WordPress companies (and former competitors) were joining forces, they weren’t sure where we would stand as a company.”

Davidson said the company fielded more questions that were concerned about the future than outright pushback against the move. Most such questions centered on whether Flywheel would continue offering their existing services and tools.

“It’s now been six months since one of the largest acquisitions in WordPress history, and we’re happy to report that things remain ‘business as usual,'” said Davidson. “We’ve remained true to our word, and Flywheel is continuing to live out our mission to help creatives do their best work. The community may have been skeptical about how this acquisition was going to pan out, but the fact is that nothing has really changed and our products have only improved!”

How Flywheel would be folded into WP Engine was not clear early on. The two companies approached the change by learning from each other and gathering feedback. “We announced that we were acquired back in June, and it took about six months to figure out the logistics of the acquisition and the relationships between both companies,” said Davidson.

After working out the details, it was decided that Flywheel would operate as a separate division within WP Engine with its own services.

Bringing the Tiny Plan Back

Some users expressed disppointment with the removal of the Tiny plan last year. It was an affordable tier for small sites at $15 per month.

The plan change was the first time Flywheel had changed pricing in the company’s history. “The changes to plans back in May 2019 were made to allow us to continue investing more into the future of our platform, existing and future features, and to offer up more solutions to better fit our customers,” said Davidson.

Based on customer feedback, Flywheel began to see that Tiny was a valuable plan for agencies who needed to offer a managed WordPress hosting solution for smaller clients. “When we joined forces with WP Engine, we were able to realign our goals as a business and refocus our efforts on the audience we’ve always catered to best: freelancers and small agencies,” said Davidson.

SOC Type 2 Certification

Earlier this month, Flywheel announced it had completed SOC 2 compliance and certification as part of their long-term plan in building a more robust and trusted company.

“Businesses using cloud service providers use SOC 2 reports to assess and address the risks associated with third-party technology services,” said Tommy Vacek, VP of Engineering. “When you boil it down though, it essentially means that Flywheel’s security practices are the best in the industry, and we’re one of the only WordPress hosts that has achieved it.”

“It’s a sign of maturity on almost all areas of our business, from finance to information technology, and it also allows us to assess risk in our business and make decisions based off of it,” he said. “It’s a stamp of approval to demonstrate Flywheel’s intentionality around security.”

The 2020 Roadmap and Beyond

Rick Knudtson, CPO and co-founder, feels like the acquisition will allow the Flywheel team to better cater to creative agencies in the WordPress space. “Our product team is working on an exciting update to our offering entirely focused on supporting the growth of agencies, and our marketing team is hard at work creating brand new resources for agencies aspiring to make 2020 a great year,” he said. “Joining forces with WP Engine has allowed us to accelerate our product initiatives.”

The company is now offering a free course on selling WordPress maintenance to clients. Themes by StudioPress, acquired by WP Engine in 2018, are all free for Flywheel customers. Flywheel is also working heavily on tools for WordPress developers.

“Developers drive WordPress forward and WP Engine is committed to supporting the future of WordPress through industry-leading developer tools,” said Knudtson. One such tool is Local, the company’s local development environment built for working with WordPress. “Since joining the WP Engine family, Local has become the standard local development and deployment tool for our customers across both of our platforms.”

Local is currently used by over 50,000 developers. The team spent the last few months re-architecting the tool from the ground up. Knudtson said it is now five times faster than before. They are expanding the team that is working on Local to help handled more advanced developer workflows.

“In 2020, we’ll introduce new ways to use Local so that all developers — novices or advanced, solo or within a team — can build their perfect development on top of Local,” said Knudtson. “Whether you just want to connect to your host and deploy, or you’re integrating into your existing CI/CD workflow, Local should be the solution.”

The Local turnkey products, such as Local Pro and Local Teams, will be available to developers across both platforms in the future.

Since the acquisition, Flywheel has included a new technology called Smart Refresh as part of their in-house caching engine. The system watches for updates made to a WordPress install and clears the cache when needed. Knudtson claims the updates to their system has increased backend performance on the platform by 50%.

The company also recently announced its new Performance Insights feature. The tool provides proprietary performance data for developers to make decisions with sites they control.

CSS-Tricks on Flywheel

I first heard of Flywheel through their product Local, which is a native app for working on WordPress sites. If you ask around for what people use for that kind of work, you'll get all sorts of answers, but an awful lot of very strong recommendations for Local. I've become one of them! We ultimately did a sponsored post for Local, but that's based on the fact that now 100% of my local WordPress development work is done using it and I'm very happy with it.

Now I've taken the next step and moved all my production sites to Flywheel hosting!

Full disclosure here, Flywheel is now a sponsor of CSS-Tricks. I've been wanting to work with them for a while. I've been out to visit them in Omaha! (👋 at Jamie, Christi, Karissa, and everybody I've worked with over there.) Part of our deal includes the hosting. But I was a paying customer and user of Flywheel before this on some sites, and my good experiences there are what made me want to get this sponsorship partnership cooking! There has been big recent news that Flywheel was acquired by WP Engine. I'm also a fan of WP Engine, being also a premium WordPress host that has done innovative things with hosting, so I'm optimistic that a real WordPress hosting powerhouse is being formed and I've got my sites in the right place.

Developing on Local is a breeze

It feels like a breath of fresh air to me, as running all the dev dependencies for WordPress has forever been a bit of a pain in the butt. Sometimes you have it going fine, but then something breaks in the most inscrutable possible way and it takes forever to get going again. Whatever, you know what I mean. At this point, I've been running Local for over a year and have had almost no issues with it.

There are all kinds of features worth checking out here. Here's one that is very likely useful to bigger teams. Say you have a Flywheel account with a bunch of production sites on it. Then a new person starts working with you and they have their own computer. You connect Local to Flywheel, and you can pull down the site and have it ready to work on. That's pretty sweet.

Local doesn't lock you into anything either. You can use Local for local development and literally use nothing else. Local can push a site up to Flywheel hosting too, which I've found to be mighty useful particularly for that first deployment of a new site, but you don't have to use that if you don't want. I'll cover more about workflow below.

Other features that I find worthy of note:

  • Spinning up a new site takes just a second. A quick walkthrough through a wizard where they ask you some login details but otherwise offer smart-but-customizable defaults.
  • Dealing with HTTPS locally is easy. It will create a certificate for you and trust it locally with one click.
  • You can flip on "Live Link", which uses ngrok to create a live, sharable URL to your localhost site. Great for temporarily showing a client or co-worker something without having to move anything.
  • One click to pop open the database in Sequel Pro, my favorite free database tool. Much easier than trying to spin up phpMyAdmin or whatever on the web to manage from there.

Flywheel's Dashboard is so clear

I love the simple UI of Local, and I really like how that same design and spirit carries over into the Flywheel hosting dashboard.

There are so many things the dashboard makes easy:

  • You need an SSL cert? Click some buttons.
  • Wanna force HTTPS? Flip a switch.
  • Wanna convert the site to Multisite? Hit a button.
  • Need to edit the database? There is a UI around it built in.
  • Want a CDN? Toggle a thing.
  • Need to invite a collaborator on a site? Go for it.
  • Need a backup? There are in there, download it or restore to that point.

It's a big deal when everything is simple and works. It means you aren't burning hours fighting with tools and you can use them doing work that pushes you forward.

Workflow

When I set up my new CSS-Tricks workflow, I had Flywheel move the site for me (thanks gang!) (no special treatment either, they'll do that for anybody).

I've got Local already, so my local development process is the same. But I needed to update my deployment workflow for the new hosting. Local can push a site up to Flywheel hosting, but it just zips everything up and sends it all up. Great for first deployment but not perfect for tiny little changes like 95% of the work I do. There is a new Local for Teams feature, which uses what they call MagicSync for deployment, which only deploys changed files. That's very cool, but I like working with a Git-based system, where ultimately merges to master are what trigger deployment of the changed files.

For years I've used Beanstalk for Git-based deployment over SFTP. I still am using Beanstalk for many sites and think it's a great choice, but Beanstalk has the limitation that the Git-repo is basically a private Git repo hosted by Beanstalk itself.

During this change, I needed to switch up what the root of the repo is (more on that in a second) so I wanted to create a new repo. I figured rather than doing that on Beanstalk, I'd make a private GitHub repo and set up deployment from there. There are services like DeployHQ and DeployBot that will work well for that, but I went with Buddy, which has a really really nice UI for managing all this stuff, and is capable of much more than just deployment should I ultimately need that.

Regarding the repo itself, one thing that I've always done with my WordPress sites is just make the repo the whole damn thing starting at the root. I think it's just a legacy/comfort thing. I had some files at the root I wanted to deploy along with everything else and that seemed like the easiest way. In WordPress-land, this isn't usually how it's done. It's more common to have the /wp-content/ folder be the root of the repo, as those are essentially the only files unique to your installation. I can imagine setups where even down to individual themes are repos and deployed alone.

I figured I'd get on board with a more scoped deployment, but also, I didn't have much of a choice. Flywheel literally locks down all WordPress core files, so if your deployment system tries to override them, it will just fail. That actually sounds great to me. There is no reason anyone from the outside should alter those files, might as well totally remove it as an attack vector. Flywheel itself keeps the WordPress version up to date. So I made a new repo with /wp-content/ at the root, and I figured I'd make it on GitHub instead just because that's such an obvious hub of developer activity and keeps my options wide open for deployment choices.

Maybe I'll open source it all one day when I've had a chance to comb through it.

For the same kind of spiritual reasons, during the the move, I moved the DNS over to Cloudflare. This gives me control over DNS from a third-party so it's easy for me to point things where I need them. Kind of a decentralization of concerns. That's not for everyone, but it's great for me on this project. While now I might suffer from Cloudflare outages (rare, but it literally just happened), I benefit from all sorts of additional security and performance that Cloudflare can provide.

So the workflow is Local > GitHub > Buddy > Flywheel.

And the hosting is Cloudflare > Flywheel with image assets on Cloudinary.

And I've got backups from both Flywheel and Jetpack/VaultPress.

The post CSS-Tricks on Flywheel appeared first on CSS-Tricks.

WPWeekly Episode 358 – Interview with Dan Maby, Founder of WP&UP

In this episode, Malcolm Peralty and I are joined by Dan Maby, Founder of WP&UP. WP&UP is a non-profit charity based in England that supports and promotes positive mental health in the WordPress Community.

Dan explains why he started the charity, what he’s learned and how he manages his own mental health, and how the donation funds are spent. He also shared some startling statistics from a recent mental health survey they conducted. The results of this survey are being put into a white paper that will be published later this year.

We finished up the show covering the news of the week. If you’re interested in supporting WP&UP, please consider donating.

Stories Discussed:

Matt Mullenweg’s Summer Update at WordCamp Europe 2019: Gutenberg’s Progress and a Preview of Upcoming Features

Free Event: Post Status to Live Stream Publish Online July 8-9

Contribution Time, Sponsored, and Teams Fields Added to WordPress.org User Profiles

WP Engine Acquires Flywheel

Transcript:

Episode358Transcript

WPWeekly Meta:

Next Episode: Wednesday, July 3rd 3:00 P.M. Eastern

Subscribe to WordPress Weekly via Itunes

Subscribe to WordPress Weekly via RSS

Subscribe to WordPress Weekly via Stitcher Radio

Subscribe to WordPress Weekly via Google Play

Listen To Episode #358:

WP Engine Acquires Flywheel

In a move that caught some people by surprise, WP Engine has announced that it has reached a definitive agreement to acquire Managed WordPress host, Flywheel.

While financial terms of the deal were not disclosed, Heather Brunner, WP Engine’s CEO confirmed to TechCrunch that the company needed to raise a small round of funding to finance the deal.

Dusty Davidson, Tony Noecker, and Rick Knudtson founded Flywheel in 2012 in Omaha, Nebraska. In 2012, there were already a handful of players in the Managed WordPress Hosting space but Flywheel was able to carve out a niche by focusing on Designers and Agencies.

In 2016, Flywheel became one of the few hosting companies added to the WordPress.org recommended hosting page. However, their listing was removed a few months later without an explanation.

Also in 2016, Flywheel acquired Pressmatic, a local WordPress development application for OS X from Clay Griffiths and rebranded it to Local by Flywheel. Representatives from both companies have stated that there are no plans to merge WP Engine Devkit with Local by Flywheel.

According to a frequently asked questions document, nothing much is changing in the foreseeable future for Flywheel customers.

Business will continue as usual! There will be no immediate changes to the Flywheel platform, plans, or experience. We’ll be spending the coming weeks and months on strategic innovation and integration planning, and are super excited to figure out how we can leverage all of our collective strengths, products, and brand assets in the best possible way.

Acquisition FAQ

Flywheel has generated a loyal following of happy customers over the years and some of them took to Twitter to express their concerns regarding Monday’s announcement.

Seeing these types of responses from customers is a testament to the level of service Flywheel provides. Many of them explained why they chose to host their clients with Flywheel over WP Engine.

Both companies have vowed to keep customers in the loop of any potential changes to plans, services, or products. While each company will operate independently as things are sorted out, it will be interesting to see how the two companies are integrated over time and how customers respond.

If you’re a Flywheel customer, please let us know what you think about the acquisition in the comments below.

To learn more about the deal, check out the following links.

Using Local with Flywheel

Have you seen Local by Flywheel? It's a native app for helping set up local WordPress developer environments. I absolutely love it and use it to do all my local WordPress development work. It brings a lovingly designed GUI to highly technical tasks in a way that I think works very well. Plus it just works, which wins all the awards with me. Need to spin up a new site locally? Click a few buttons. Working on your site? All your sites are right there and you can flip them on with the flick of a toggle.

Local by Flywheel is useful no matter where your WordPress production site is hosted. But it really shines when paired with Flywheel itself, which is fabulous WordPress hosting that has all the same graceful combination of power and ease as Local does.

Just recently, we moved ShopTalkShow.com over to Local and it couldn't have been easier.

Running locally.

Setting up a new local site (which you would do even if it's a long-standing site and you're just getting it set up on Flywheel) is just a few clicks. That's one of the most satisfying parts. You know all kinds of complex things are happening behind the scenes, like containers being spun up, proper software being installed, etc, but you don't have to worry about any of it.

(Local is free, by the way.)

The Cross-platform-ness is nice.

I work on ShopTalk with Dave Rupert, who's on Windows. Not a problem. Local works on Windows also, so Dave can spin up site in the exact same way I can.

Setting up Flywheel hosting is just as clean and easy as Local is.

If you've used Local, you'll recognize the clean font, colors, and design when using the Flywheel website to get your hosting set up. Just a few clicks and I had that going:

Things that are known to be a pain the butt are painless on Local, like making sure SSL (HTTPS) is active and a CDN is helping with assets.

You get a subdomain to start, so you can make sure your site is working perfectly before pointing a production domain at it.

I didn't just have to put files into place on the new hosting, move the database, and cross my fingers I did it all right when re-pointing the DNS. I could get the site up and running at the subdomain first, make sure it is, then do the DNS part.

But the moving of files and all that... it's trivial because of Local!

The best part is that shooting a site up to Flywheel from Local is also just a click away.

All the files and the database head right up after you've connected Local to Flywheel.

All I did was make sure I had my local site to be a 100% perfect copy of production. All the theme and plugins and stuff were already that way because I was already doing local development, and I pulled the entire database down easily with WP DB Migrate Pro.

I think I went from "I should get around to setting up this site on Flywheel." do "Well that's done." in less than an hour. Now Dave and I both have a local development environment and a path to production.

The post Using Local with Flywheel appeared first on CSS-Tricks.