Moving Forward Slowly and Steadily

With the increased writing and focus on CaptainCore, I’ve been receiving lots of feedback, which is great! Many individuals have been asking me when CaptainCore be ready to use or if I have an estimated time for launching. I don’t have an answer for either, however CaptainCore development is moving forward slowly and steadily. If you want to be the first to try things out you can add your name to my early access list.

CaptainCore isn’t ready for a public release.

There are many quirks and bugs that are actively being worked on. There also isn’t a documented way to setup a CaptainCore instance or even a walkthrough for how to use CaptainCore. CaptainCore currently only supports sites hosted with WP Engine and Kinsta. It should be possible to expand support for any web host which has SSH access, however that’s just another thing that needs to be developed.

I’m amazed at how far the project has come over the last few short years. Take a look at the really crude interface back in 2018 to what it’s looks like today. It’s night and day difference. To have a better understanding of why I’m making CaptainCore, you’ll need to understand a bit more about how I built Anchor Hosting.

CaptainCore – 2018 vs 2020

I built CaptainCore to help me manage hundreds of WordPress sites.

CaptainCore by itself it not the only thing that enables me to maintain so many WordPress sites. Sure, CaptainCore helps and is amazing, however another overlooked fact is that I currently only leverage one or two web host providers. As of today I have 1,232 WordPress sites hosted with Kinsta. That it. I’m not managing WordPress sites with any other host provider. Focusing on a single host provider is far more efficient than attempting to using many different providers. While my host provider of choice has changed over the years, this strategy of maintaining a single primary host provider has been a key to my success.

Adopt a WordPress maintenance strategy that involves a single host provider.

If possible I’d highly recommend WordPress maintenance providers only use a single web host, like Kinsta. If you’re a WordPress maintenance provider that might not be possible. Then again let me challenge your thinking. Would it really be so hard to require a hosting provider switch during the on-boarding process? I suspect you’d be preemptively solving many WordPress related issues by simply picking good web host.

As a web host reseller that’s preciously what I do. Check out my post Make Reselling WordPress Hosting Awesome 🌟. More than just hunting for better tools, it’s important to ask yourself how your business model is aligned with your core services. Okay enough of my talking, it’s back to CaptainCore development. Onward!