FlyinghostReviews of flyinghost.com

I just migrated my site to Flyinghost and Rajin made the experience seamless. He kept me in the loop throughout the day until the migration was fully complete. Two thumbs up for Rajin!

I migrated one of our fairly sized Woo websites with over 23k+ products to FlyingHost. To give full context and transparency, I had been using FlyingPress with the website for over 2 years and FlyingCDN since September 2025. The site was hosted on a Dedicated CPU Optimised DigitalOcean Droplet and still had performance issues, especially on checkout/cart pages. The Database and PHP workers were also fairly optimised, and Redis Cache was also active. The website is connected to multiple inventory management tools and Shipping platforms via APIs. I was contemplating trying out xCloud or even a radical migration to Shopify for better performance. When the beta of Flying Host was announced, I decided to give it a try and contacted Gijo (FlyingWeb Founder). At that time, the servers were only available in the US and EU. Since we are based out of India, I preferred a server in India and within 3-4 days I was informed that the India location was also live, and I decided to do join the beta program. Over the last 3 months or so, there have been a few pointers that I have liked about FlyingHost and their team, which have made me continue with them for a foreseeable future. 1. Migration and Support Team: The migration happened at 2 AM IST, and the team was active and assisted along the way. It took a couple of hours for a website of our size, and after a bit of data sanitisation checks, by 6 in the morning the site was live. Our setup had the blog and learning platform hosted on a separate server and served as a subfolder using a reverse proxy. It was an absolute must, and Gijo and his team delivered the custom Nginx function in the FlyingHost Panel in a couple of days 2. Pricing and Speed: Since the site was already on a beefy server, I did save decent dollars while getting better performance. Since FlyingCDN was already active on the website, the additional bandwidth costs are similar, so I won’t be counting that, but basic server costs are quite a saving. For larger websites with loads of images, the bandwidth costs may add up, so keep that in mind. I have tested it with EWWW EasyIO CDN, so I assume for other CDN providers it should work for image offloading. This method has its own pros and cons, and you can make a measured call based on that. 3. Works Brilliantly with FlyingPress. Single cache clearing clears all cache - Object, full page, as well as CDN. Less need for manual interventions 4. Uncached Pages like Cart / Checkout / My Account and even WordPress Admin are blazingly fast. 5. During the beta, the team added PatchStack for Security and a FlyingPress License. Better security, and I freed a license too . 6. Support responsiveness. The team is very responsive in case you see unwanted bots/services hitting your server. They quickly identify and patch/throttle them as needed. The average response time has been in minutes on weekdays via chat. 7. Performance Metrics: PageSpeed metrics have improved drastically. TTFB on Mobile is under 0.8s. LCP improved from under 4600ms to under 1360ms There are a couple of points where FlyingHost may improve in their future releases 1. O2O with Cloudflare. I hate to ping the FlyingHost team for every IP whitelisting or to block a specific bot. This would ease out managing rules and traffic for everyone. This is a good-to-have. 2. Database Management - To be honest, FlyingHost does have phpMyAdmin built in. For almost 99% of users and use cases, that works fine. But when it comes to large databases, web-based tools aren’t cut out for that. They lag and time out. Detailed use cases have been shared with the team, and hopefully they will work something out for the remaining 1% of users like me. Again, not a showstopper. Overall, I have been extremely happy with FlyingHost, and am glad I took part in the beta of an extremely new platform. To be honest, I was expecting some speed improvements since the website was already using two of FlyingWeb’s flagship products, but the improvements have been drastic. Congratulations to Gijo and his team for this, and thank you for building this.

I manage two fairly large and complex websites (70+ plugins, WooCommerce, LearnDash, lots of users and existing data) for my company. Over the past 7 years or so, I've tested or used a variety of hosts, including Kinsta, Servebolt, Cloudways, GridPane (with Vultr), Rapyd.cloud (now called Levamo), and ScalaHosting. I've had mixed results with these hosts, particularly as they relate to five factors: performance, usability, security, support, and price. Some hosts excel at one or more of these factors, but struggle with the others. I was excited when FlyingHost was announced because I've been a fan of the founder (Gijo Varghese) and his work around improving WordPress performance for years. After migrating one of my sites to FlyingHost, I'm now a HUGE fan of their hosting. FlyingHost hits the sweet spot for all of the factors important to me: 1) It has some of the best speed and performance (both frontend and backend) of any host I've tested. Benchmarking tools (such as plugins like atec Hosting Check, Hosting Benchmark tool, and PHP Vitals) and core web vitals scores support this. 2) It has great security features (with Cloudflare Enterprise and Patchstack built in). 3) The pricing is very fair and straightforward. It may not be the most economical if you're looking to host 100 brochure sites, but it's very competitive if you have dynamic sites (e.g., LMS, membership, or ecommerce) that require significant resources. 4) The user interface is terrific, making the most common website management and development tasks easy (with full access to databases, files, SSH terminal, etc.). 5) Support is available via live chat or email and has been quick to respond and resolve my issues (even with more technical or complex problems requiring escalation). I'm very happy with FlyingHost so far and plan on moving my other large site to them soon!

The first good decision i made was to move from other cache plugins to Flyingpress. The way Flyingpress evolved is exceptional. Keeping things simple and meaningful. The best decision was to move to Flyinghost. Been using Clost* and many others since a decade from time to time. But it looks like the search has finally come to an end with Flyinghost. Kudos to the team and Gijo ofcourse.

Some preface: FlyingHost is built by the team behind FlyingPress, which is included at no extra cost, and builds on what FlyingCDN was, also included. The driving force behind FlyingPress is Gijo Varghese, someone I consider among the very best in WordPress performance optimization. I’ve followed his work since the earliest Flying plugins, discussed plenty of ideas with him over the years, and I’m proud to call him a friend. TLDR: Give FlyingHost a try. I genuinely don’t think you’ll be disappointed. The long praise follows; I was invited to test FlyingHost in early June and immediately jumped at the opportunity. I started with two small domains, comparing FlyingHost directly against my own optimized VPS setup using Redis, HTTP/3, Nginx and PHP-FPM. Despite being relatively small sites, they use custom paths, constants and React/Vue-based backend functionality. I thought my VPS performed well. It did. FlyingHost simply performed way better. That convinced me to test something heavier: a WooCommerce installation with several thousand products, lots of custom development code and Elementor. On our shared hosting environment at work, tasks like bulk operations and admin-ajax add-to-cart requests struggled. FlyingHost simply handled them. Admin-ajax requests were around 100–200ms, WooCommerce product listings loaded in roughly a second, and Elementor opened in around 1–1.5 seconds. This was without Redis object caching or extensive optimization. Naturally, results will vary between websites, but I already knew FlyingHost was something special. I even demonstrated it at the agency where I work. The reaction was basically: once pricing is confirmed and the service leaves beta, we may start replacing some of our higher-end hosting setups and custom VPS configurations. Then came the real test. I moved my main site: a 70+GB WordPress installation with 10 custom post types, 60,000+ published items, 42,000 drafts, 48,000 published comments and a roughly 12GB database. It also runs WPML, SearchWP, FacetWP and a huge amount of custom configuration and code. There were a few small migration issues, but the FlyingHost team helped resolve them. About two days later, I moved it into production and cancelled the VPS that previously hosted all three sites. What makes this even more impressive is how much FlyingHost has improved since that initial test. FlyingPress is now included. Flyingpress now support Redis Object Caching out of the box FlyingHost. Pricing turned out to be excellent. Their Cockpit control panel gained useful resource insights, integrated Patchstack security with virtual patching, flexible backups that do not count towards your storage allowance and also incredibly fast manual backups. You also get a browser-based SSH terminal, while every site runs inside its own fully isolated container. SSH/SFTP, phpMyAdmin and multiple PHP versions are available, logs are refreshingly straightforward, and connecting domains is easy. The Cockpit itself sums up the philosophy nicely: clear, intuitive and without unnecessary clutter. I genuinely haven’t been this impressed by WordPress backend performance in a long time. FlyingHost has the potential to become a new benchmark for what managed high-end WordPress hosting should feel like. In my FlyingPress review (also here on Trustpilot) back in April 2024, I wrote: “I will always vouch for Gijo and the FlyingWeb team.” Now, in August 2026, I stand behind that statement even more strongly. Gijo and team: thank you for everything you do. I will always be right there with you all. PS: I was invited to the private trial and received credits for testing, but nobody asked me to write this review or influences anything on what I said. Everything above reflects my own experience and opinion and if you doubt that reach out.

The more features a WordPress site requires, the more plugins it needs. A site that includes both an e-commerce section and an e-learning section is even more demanding. The number of concurrent visitors requires a robust and powerful server. And with Google’s speed standardization requirements… Optimizing page load speed has become critical. With solutions for optimizing the cache, code, and the number of plugins loaded per page, among other things, you can quickly achieve a good score. The problem arises when users browse logged-in on dynamic pages that can’t be cached… or worse yet, when you’re working on your own site, editing articles, lessons, or products, and every time you save a page it takes at least 15 seconds… There are many solutions, but the foundation is having excellent web hosting. Over the past 8 years, I’ve tried many hosting solutions at various price points: Cloudways, Rocket.net, ScalaHosting. At best, I could load the WP admin dashboard in 12 seconds. With FlyingHost, it takes 4.7 seconds. I tested a few pages like this, and the results are consistent. FlyingHost is definitely faster (and I’m not even using their most powerful plan). I’ve been testing FlyingHost since June 2026 and I’m thrilled! FlyingHost includes the Patchstack security system, FlyingCDN, and FlyingPress: everything you need to optimize a WordPress site for both visitors AND admins!

It's the best WordPress hosting I ever tried. The have made everything inhouse, and better. All the things you need without having to pay extra for cpanel, etc Powerful system. I run a complete dynamic website with 200k monthly users and it works like a charm. Best wishes to the founders.