Cloud

Squish Managed Cloud Review: CyberPanel Hosting, Tested

Once you outgrow shared hosting, you either run a cloud server yourself or pay someone to run it for you. Squish Managed Cloud is the second kind: a managed cloud server with CyberPanel, Squish DNS and a Bunny CDN edge already wired together. Plans run from $30 to $550 a month, and we tested the $50 Studio plan with 2 vCPU and 4 GB of RAM. That price includes DNS, a CDN edge, a control panel, daily backups and a support team, all set up before you first log in.

Original content from computingforgeeks.com - post 189578

For this Squish Managed Cloud review we tested DNS, SSL, WordPress, speed, security, backups, support and Squish’s MCP server from Claude Code. Setup takes minutes and cached pages are fast. Squish says every new server now ships with fail2ban, a ModSecurity firewall in logging mode and a dashboard Backups screen; ours got all three while we were testing. We also cover the few settings to change on day one. Prices and results were checked in November 2026.

Sponsored: Squish paid for this review. We ran every test ourselves, and details we couldn’t test are marked as Squish’s.

1. What the Squish Managed Cloud Studio plan gives you

Studio is a cloud server of your own, not shared hosting, with Squish’s panel, DNS and CDN on top, and the dashboard shows the exact server size, so you know what hardware you’re renting. The dashboard still labels the plan Cloud Essentials, an older internal name. Squish picked the plan and the New York region for us. This is what you get on day one:

ItemWhat we found
Server2 shared vCPU, 4 GB RAM, 2 GB swap file, New York region
Disk and transfer80 GB disk, 4 TB transfer a month
OSUbuntu 24.04 LTS, unattended upgrades on
Panel and stackCyberPanel 3.0 on OpenLiteSpeed, PHP 8.1 to 8.5, MariaDB on localhost
EdgeBunny CDN pull zone, Squish DNS
Root accessSSH with your own key, password login off
BackupsDaily whole-server backups kept 7 days, restored from the dashboard
Price$50/mo, no introductory rate that jumps at renewal

A quick sysbench and fio pass gave 785 CPU events per second on one thread, 44.3k random-read IOPS at 4K and about 2 GB/s on sequential reads. Read these as a baseline for this plan rather than a comparison.

Squish Managed Cloud dashboard showing the Studio server, labelled Cloud Essentials, in the New York region with 2 vCPU and 4 GB, an open support case and two-factor on

The dashboard is one page with domains, sites, support cases and a two-factor card. Manage on the server row opens CyberPanel, Backups, Upgrade, Add-ons, Credentials and Cancel. Credentials shows the server IP, the panel password behind a Reveal button and a box for your SSH public key.

2. From welcome email to a live HTTPS site

Getting from the welcome email to a second site on HTTPS took us under two minutes of waiting, and every step happened while we watched:

  1. Welcome link to dashboard, about 5 seconds: the one-time link asks for a password and signs you in. Choose a long one, since this account controls a server, and turn on two-factor once you’re in.
  2. Root SSH key, under 6 seconds: paste a public key in Credentials and ssh root@ works on the first try.
  3. DNS record, about 10 seconds: a new A record answered on both Squish nameservers, Google and Cloudflare 10 seconds after we clicked Add.
  4. New site with SSL, about 35 seconds: CyberPanel’s Create Website finished in 30 seconds and the Let’s Encrypt certificate was serving 5 seconds later.

Squish DNS runs on Bunny’s DNS network, the same company behind the CDN, so the edge records are created for you. New zones also come with SPF -all, DMARC p=reject and CAA records for Let’s Encrypt. That’s a safe default for a domain that sends no mail, but mail from the Postfix server that runs on the box will fail SPF until you edit the record.

Squish DNS records editor listing PullZone, SPF, DMARC and CAA records for the test domain

For the new site we used CyberPanel’s Create Website form, which defaults to PHP 8.1, the oldest version on offer. Pick a newer one before you click, because 8.1 no longer gets upstream security fixes and you do not want to migrate PHP later.

CyberPanel Create Website form on a Squish Managed Cloud server with PHP 8.1 preselected

There is no SSL checkbox for you to tick, because CyberPanel requests the certificate on its own. Check what the new site serves:

echo | openssl s_client -connect wp.testsquish5.xyz:443 -servername wp.testsquish5.xyz 2>/dev/null | openssl x509 -noout -subject -issuer -dates -ext subjectAltName

A Let’s Encrypt certificate for the new name only, valid for 90 days:

subject=CN=wp.testsquish5.xyz
issuer=C=US, O=Let's Encrypt, CN=YR2
notBefore=Nov 12 17:57:30 2026 GMT
notAfter=Feb 10 17:57:29 2027 GMT
X509v3 Subject Alternative Name:
    DNS:wp.testsquish5.xyz

Each site also gets its own page in CyberPanel with a file manager, Git and SFTP tools, its logs and the certificate status, so routine site work doesn’t need SSH. The red notice shows up because the panel is opened by IP address; its browser terminal only works on a hostname with a valid certificate, so use SSH for shell work.

CyberPanel website manager on Squish Managed Cloud with file manager, Git and SFTP tools and a valid Let's Encrypt certificate

Two jobs renew the certificate: acme.sh runs four times a day from cron and CyberPanel has its own weekly renewal job. If you’d rather build this stack yourself, our guide to installing CyberPanel with Let’s Encrypt covers the same panel on a bare server.

3. Bunny CDN speed and the cache setting to change

The domain Squish set up for us sits behind a Bunny pull zone on its apex and www records (a site you add with a plain A record, like our wp. test site, goes straight to the server). A cached page came back in 0.03 to 0.07 seconds from Germany and about 0.2 seconds from Nairobi. The one setting to change is how long it caches. WordPress does not send a Cache-Control header on pages, so the edge adds its own public, max-age=2592000, which is 30 days, for the edge and for every visitor’s browser. If you want the background on edge caching, our explainer on how a CDN caches covers it.

We hit this on day one. After we changed a post title in WordPress, the edge kept serving the old title while the origin already had the new one, and visitors could have seen it for up to 30 days. Purging the edge fixes the CDN but not browsers that already stored the page. Logins and search are handled well: a wordpress_logged_in cookie gets BYPASS, so editors see live pages, and search results that send no-store aren’t cached.

The fix is to send your own header so the edge stops inventing one. A small must-use plugin sets a 10-minute edge TTL and tells browsers to revalidate. Add it once WordPress is installed (section 4). Find the site’s owner first, since CyberPanel runs each site as its own user:

stat -c %U /home/testsquish5.xyz/public_html

Ours was tests9216; yours will be named after your domain, so swap your own domain and site user for testsquish5.xyz and tests9216 in the commands below. WordPress does not ship a mu-plugins folder, so create it:

mkdir -p /home/testsquish5.xyz/public_html/wp-content/mu-plugins

Create the plugin file:

sudo vim /home/testsquish5.xyz/public_html/wp-content/mu-plugins/edge-cache-ttl.php

Paste this, the exact file running on our server:

<?php
/* Plugin Name: Edge cache TTL */
add_action( "send_headers", function () {
	if ( is_user_logged_in() || is_admin() || ( defined( "DOING_AJAX" ) && DOING_AJAX ) ) {
		return;
	}
	header( "Cache-Control: public, max-age=0, s-maxage=600" );
} );

Hand the folder and file to the site user, so WordPress, LiteSpeed Cache and WP-CLI running as that user can manage them:

chown -R tests9216:tests9216 /home/testsquish5.xyz/public_html/wp-content/mu-plugins

The plugin does not skip password-protected posts, so add a check for the wp-postpass_ cookie if you use them. Purge the CDN once after adding it, because pages the edge already holds keep their 30-day lifetime: our /hello-world/ copy from before the plugin was still being served more than a day later. Then check any page’s headers:

curl -s -o /dev/null -D - https://testsquish5.xyz/ | grep -iE '^(cache-control|cdn-cache):'

You should see public, max-age=0, s-maxage=600 with a MISS on the first request and a HIT after it. When we shortened the TTL to 20 seconds to test it, the edge served the stale copy once after expiry while it fetched a fresh one in the background, so visitors never waited on the refresh.

Ten minutes suits most blogs, and the plugin is a one-time change: after it, every edit reaches visitors within ten minutes while cached pages stay fast.

4. Installing WordPress on CyberPanel 3.0 with WP-CLI

CyberPanel 3.0 moved its WordPress Manager behind a paid entitlement, so on a fresh server Deploy WordPress, WordPress > List and the per-site 1-Click button all redirect to /websites/pricing. That is a change in CyberPanel itself, and it applies to any CyberPanel 3.0 server without the paid add-on.

CyberPanel WordPress Manager sales page shown instead of the WordPress installer

Squish’s assistant offers to open a ticket so the team installs WordPress for you. Doing it yourself with WP-CLI over SSH took us 14 seconds end to end. WP-CLI is not preinstalled, so add it first:

curl -sSLo /usr/local/bin/wp https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar && chmod +x /usr/local/bin/wp

We installed it on the main site Squish provisioned (testsquish5.xyz, on PHP 8.5), not on the test subdomain. Create the database through CyberPanel’s CLI so the panel knows about it:

cyberpanel createDatabase --databaseWebsite testsquish5.xyz --dbName tests_wp --dbUsername tests_wp --dbPassword 'ChangeThisDbPass'

It answers with a one-line JSON status:

{"success": 1, "errorMessage": "None"}

Run the rest as the site user so file ownership stays right. A shell variable keeps the commands short:

W="sudo -u tests9216 wp --path=/home/testsquish5.xyz/public_html"
$W core download
$W config create --dbname=tests_wp --dbuser=tests_wp --dbpass='ChangeThisDbPass' --dbhost=localhost
$W core install --url=https://testsquish5.xyz --title='Squish Lab' --admin_user=siteadmin --admin_password='ChangeThisAdminPass' --admin_email=[email protected] --skip-email
$W plugin install litespeed-cache --activate

The install and the LiteSpeed Cache plugin both report success:

Success: WordPress installed successfully.
Installing LiteSpeed Cache (7.9.3)
Downloading installation package from https://downloads.wordpress.org/plugin/litespeed-cache.7.9.3.zip...
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
Activating 'litespeed-cache'...
Plugin 'litespeed-cache' activated.
Success: Installed 1 of 1 plugins.

LiteSpeed Cache matters here, because OpenLiteSpeed’s page cache is where most of this server’s speed comes from (section 5). Our OpenLiteSpeed guide explains the server side if you want to tune it.

Error: “proc_open(): posix_spawn() failed: Permission denied”

Setting pretty permalinks with $W rewrite structure '/%postname%/' --hard saved the structure but died writing .htaccess with this error, and /hello-world/ then returned 404. OpenLiteSpeed on CyberPanel reads .htaccess, so add the standard WordPress block by hand:

sudo vim /home/testsquish5.xyz/public_html/.htaccess

Append it after the LiteSpeed Cache section:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Then run $W rewrite flush. After that, /hello-world/ and the other post URLs answered 200 on our server. If yours still return 404, restart OpenLiteSpeed with /usr/local/lsws/bin/lswsctrl restart. WordPress’s full version of this block also passes the Authorization header, which Application Passwords need, so copy that line from the WordPress docs if you use them.

5. Squish Managed Cloud speed and load test results

Cached WordPress pages are fast on this plan. Uncached PHP is where 2 vCPU runs out. We measured time to first byte with curl -s -o /dev/null -w '%{time_starttransfer}\n', five samples per path, from Nairobi and from a server in Germany, plus on the server itself with TLS excluded:

PathFrom NairobiFrom GermanyOn the server
Bunny edge, cached (HIT)0.19-0.22 s0.029-0.074 sn/a
Bunny edge, not cached (MISS)0.65-0.89 s0.47-0.53 sn/a
Origin, LSCache hit0.87-0.94 s0.28-0.37 s2-6 ms
Origin, uncached PHP1.04-1.13 snot measured179-215 ms

Then we put load on it from Germany with oha, for example oha --no-tui -c 25 -z 60s https://testsquish5.xyz/, keeping it moderate because it’s a live server:

RunConnectionsRequests/sSuccessp50 / p95Server CPU
Bunny edge25 for 60 s27299.56%9 / 20 msidle
Origin, LSCache hit50 for 60 s535100%93 / 95 msabout 15%
Origin, uncached PHP10 for 30 s9.7100%1037 / 1263 ms100%
Pages LSCache had already built served 535 requests per second, while uncached WordPress PHP topped out at 9.7 on the 2 vCPU server.Pages LSCache had already built served 535 requests per second, while uncached WordPress PHP topped out at 9.7 on the 2 vCPU server.
Requests per second by path, load from Germany

We kept the edge run at 25 connections, because at 50 our single test address started getting errors while the server sat idle, which looks like Bunny limiting one client; real visitors come from many addresses. The LSCache run is bound by distance: 50 connections at about 93 ms round trip to New York caps out near 535 requests per second while the CPU barely moves.

Plan capacity around the uncached run. At about 180 ms of PHP per page, two vCPUs top out near 10 requests per second, and the CPU hit 100% at 9.7. If your blog stays cached, you will be fine. Logged-in members, WooCommerce carts and search all skip the cache, so if most of your traffic looks like that, budget for the 4 vCPU plan.

6. Squish Managed Cloud security: defaults and what to add

We scanned the server as it was handed to us with nmap, probed it and ran a login test. Much of it is already locked down: root SSH is key-only, unattended upgrades are on, PowerDNS refuses recursive queries, the edge refuses TLS 1.0 and 1.1 and sends HSTS, X-Frame-Options and nosniff headers, and the dashboard offers TOTP two-factor. Squish says every new server now ships with fail2ban and ModSecurity, as ours did by day two. These are the items to tighten:

  • WAF in detection mode: ModSecurity with the OWASP rules logs attacks without blocking them. Before it reached ours, a SQL injection string, a <script> tag, a ../../etc/passwd path and an sqlmap user agent all got 200. One line turns blocking on, covered below.
  • Login limits count per address: the fail2ban WordPress jail bans an address after ten failures. Before it reached ours, 60 wrong passwords in a row got no lockout, and /wp-json/wp/v2/users still lists the admin username, so add a per-username limit too, covered below.
  • Panel on a public port: CyberPanel listens on 8090 to the world with a self-signed certificate, so your browser warns when the dashboard opens it. Locking it to your IP takes a few firewalld commands, also below; Squish’s support team works over SSH (its key is in root’s authorized_keys), so the lock doesn’t get in their way.
  • Emailed panel password: the provisioning email carries the panel login. Rotate it over SSH with adminPass followed by the new password; after that the emailed one no longer worked.
  • Mail, FTP and DNS ports open: 21, 25, 53, 110, 143, 465, 587, 993 and 995 answer from the internet, which is handy if you run those services and best closed if you don’t.

Squish’s brute-force protection

Squish says new servers ship with fail2ban. Ours got it during the test, 68 minutes after we asked about brute-force protection in a support case (section 9). You get three things:

  • An SSH jail: six failed logins and the address is banned for an hour through firewalld. It banned two SSH scanners within seconds of starting, from attempts already in the log.
  • A WordPress jail: ten failed POSTs to wp-login.php or xmlrpc.php within 10 minutes earn a one-hour ban, which OpenLiteSpeed enforces as an access-control deny. The filter counts every xmlrpc.php POST, good or bad, so Jetpack or the WordPress mobile app can get a real user banned.
  • Real visitor IPs: OpenLiteSpeed now trusts the CDN’s forwarded-for header, and the Bunny edge addresses sit on fail2ban’s ignore list, so a ban hits the attacker and not the CDN.

We tested the WordPress jail from Nairobi, through the CDN, with eleven wrong passwords in a row. fail2ban logged the ban within 9 seconds. It took effect about a minute later, because the script that writes bans into OpenLiteSpeed restarts the web server from a once-a-minute cron job. From then on our address got a 502 on any page the CDN hadn’t cached, while cached pages still loaded and a second machine in Germany saw the login page as normal.

Real traffic showed where any per-address jail stops. A bot working from one /24 network found our admin username through /?author=1, then made 21 login attempts from 17 different addresses over 42 minutes, no more than three per address. A rule that counts to ten per address never fires on that pattern, so pair the jail with a WordPress login limiter that counts failures per username, or two-factor on wp-admin. To see what a bot can learn about your own site, run the user enumeration check from our WPScan guide.

Turning on ModSecurity blocking

Squish says new servers come with ModSecurity 3, the OWASP Core Rule Set and its WordPress exclusions; ours received them the day after our support case. It ships in detection-only mode, so attacks are logged to /var/log/squish/modsec_audit.log but still served. See what it would have blocked before you switch it on:

grep -o '"uri":"[^"?]*' /var/log/squish/modsec_audit.log | sort | uniq -c | sort -rn | head -8

Six hours of log on our server were bots hunting for credential files, phpinfo.php and backups, plus xmlrpc.php POSTs and our own probes on /:

     22 "uri":"/
     15 "uri":"/xmlrpc.php
      4 "uri":"/google-credentials.json
      4 "uri":"/gcp-credentials.json
      4 "uri":"/credentials.json
      3 "uri":"/www/phpinfo.php
      3 "uri":"/wp-config.php.bak
      3 "uri":"/wp-admin/phpinfo.php

Nothing in it came from normal visitors or wp-admin, so we switched the rule engine from detection to blocking and restarted OpenLiteSpeed:

sed -i 's/^SecRuleEngine DetectionOnly/SecRuleEngine On/' /usr/local/lsws/conf/squish-modsec/main.conf && /usr/local/lsws/bin/lswsctrl restart

The same probes that got 200 on day one now got 403 through the CDN, and so did a request for /wp-config.php.bak. Posts, search, the REST API and the wp-admin login kept working, and saving a draft whose content held a SQL query and a curl | bash line went through. The file is marked as generated by Squish, so check that line again after Squish pushes updates, and leave it in detection mode for a few days first if your site runs plugins that post unusual form data.

Locking the CyberPanel port to your IP

You’ll also want to close the panel port to the world. The server runs firewalld, and CyberPanel’s Firewall page shows the rule that opens 8090 to every address:

CyberPanel Firewall Management page on a Squish server with the panel rule allowing port 8090 from 0.0.0.0/0

A second rule opens it to IPv6 as well and isn’t listed on that page, so use the shell. An allow rule for your IP changes nothing while those two exist. Add an allow rule for your address before you reload, so you don’t cut off the panel you’re logged in to, using your own public IP in place of 203.0.113.50:

firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="203.0.113.50/32" port port="8090" protocol="tcp" accept'

Then drop the two rules that open the port to everyone:

firewall-cmd --permanent --remove-rich-rule='rule family="ipv4" source address="0.0.0.0/0" port port="8090" protocol="tcp" accept'
firewall-cmd --permanent --remove-rich-rule='rule family="ipv6" port port="8090" protocol="tcp" accept'

A reload applies them, but it also throws away runtime-only rules, and that’s where fail2ban keeps its SSH bans. Restart fail2ban straight after so it puts them back:

firewall-cmd --reload && systemctl restart fail2ban

On our server the panel still opened from our address and timed out from a second server in Germany. If your home IP changes later, SSH still works, so you can fix the rule from the shell. Our Fail2ban guide covers writing extra jails if you want to tune Squish’s.

Kernel updates install but wait for you to reboot

Unattended upgrades patch packages, but automatic reboots are off, and on our server a newer kernel was already installed and waiting for a reboot. Check for a pending reboot with:

cat /var/run/reboot-required.pkgs; uname -r

The marker dated from provisioning, the night before we first logged in:

linux-image-6.8.0-149-generic
linux-base
linux-image-6.8.0-147-generic
linux-base
6.8.0-147-generic

We rebooted and timed it. The origin stopped answering 36 seconds after the command and served pages again at 60 seconds, so the outage was about 24 seconds. OpenLiteSpeed, MariaDB, CyberPanel, PowerDNS and fail2ban all came back on their own, and fail2ban restored its active bans. Schedule a reboot for a quiet hour after kernel updates, because the server won’t do it on its own.

7. Squish Managed Cloud backups: daily, with one-click restore

Every Managed Cloud server is backed up daily and each backup is kept for 7 days, as Squish confirmed in our support case. The list sits under Backups in the server’s Manage menu, and by our second day it held two system backups, one per day:

Squish dashboard Backups dialog listing two daily system backups of the Managed Cloud server, each with a Restore button

Each one is a full copy of the server, taken at about 16:00 UTC; the second was 8.16 GB. Restore is one click, and Squish warns that it swaps in the whole disk from that day, so everything written since is lost. Use it to recover the whole server; for one deleted post, a per-site copy is quicker.

Squish server add-ons with Managed Backups Plus, Managed Monitoring, Night Shift and AI Visibility prices

If 7 days isn’t enough history, Managed Backups Plus costs $9 a month and keeps daily snapshots with restore points going back 30 days. For per-site copies that can live off the server, CyberPanel’s own backup tool is free to use:

cyberpanel createBackup --domainName testsquish5.xyz

It took 12 seconds for our WordPress site and left a 35.7 MB archive in the site’s home folder:

-rw------- 1 tests9216 tests9216 35715168 Nov 12 19:20 backup-testsquish5.xyz-11.12.2026_19-20-10.tar.gz

That archive sits on the same disk as the site, so it will not survive if you lose the server. Add a remote destination and a schedule on the Destinations and Schedule pages under CyberPanel’s Backups menu before you put anything real on the box.

8. Managing the server from Claude Code with the Squish MCP server

Squish runs an MCP server with 59 tools by its developer page’s count (37 read, 22 write) that lets Claude Code, Claude Desktop, Cursor or any MCP client read and change your account. It worked on the first try. For Managed Cloud the useful tools are CDN purge and stats, DNS records and a server health check; the file and backup tools only cover Squish’s shared hosting. Because it covers the whole account, the CDN, DNS, the health check and previewed writes sit behind one key.

Squish Assistant tab with the Connected assistants key form for Claude Code and other MCP clients

Keys come from the Assistant tab: tick Let the assistant act on my account, pick Read, Read and write, or Read, write and buy domains, then Create key. Keys last 90 days, you can hold 10, and a write key needs two-factor on your login. A separate switch lets the assistant pay for domains on your saved card, with per-purchase and per-day caps; it is off by default and we left it off.

Error: “Couldn’t start setup. Please try again.”

Two-factor setup failed with this message while we were signed in through the one-time welcome link. The browser console showed Firebase’s UNSUPPORTED_FIRST_FACTOR. Signing out and back in with email and password fixed it, so if you came in through the welcome email, do that before enabling two-factor.

With a key in hand, give Claude Code the server in a config file. Our Claude Code MCP setup guide covers the other ways to add one. Create the file:

vim ~/squish-mcp.json

Add the endpoint and your key:

{"mcpServers":{"squish":{"type":"http","url":"https://api.squish.co/mcp","headers":{"Authorization":"Bearer sq_mcp_your-key-here"}}}}

The file holds a key that can change your account, so keep it private with chmod 600 ~/squish-mcp.json. Run Claude Code with that file, pre-approving only the three read tools. This is the prompt we used:

claude -p "Using only the squish MCP tools: list my hosting, then for the Managed Cloud server on testsquish5.xyz get the CDN stats and run diagnose_my_server. Report the raw facts each tool returned in a short list. Do not change anything." --mcp-config ~/squish-mcp.json --strict-mcp-config --allowedTools "mcp__squish__list_my_hosting,mcp__squish__get_my_cdn_stats,mcp__squish__diagnose_my_server"

Claude called the three tools and answered in 15 seconds. The health check was useful: CPU at 29% of 2 vCPUs, memory at 28% of 3.8 GB, disk at 12% of 76.4 GB and “upgradeSuggested false”. The CDN stats gave a 50.4% hit rate over 30 days and a 272 ms average origin response. The hosting list gives the panel address with port 8443, while CyberPanel answers on 8090, so open the panel from the dashboard’s Manage menu.

Writes take two steps, so an AI can’t change your account by accident. Asked to purge the CDN, Claude first called purge_my_cdn_cache with confirm:false and got a preview:

{"ok":true,"result":{"applied":false,"preview":true,"confirmed":false,"domain":"testsquish5.xyz","message":"Preview: clear the edge cache for testsquish5.xyz. Visitors fetch fresh files on their next visit; nothing on the site changes. Confirm with the customer, then call again with confirm:true."}}

Only the second call with confirm:true purged the hostname. The stale page from section 3 came back with the new title about 6 seconds later. If you already work in an AI coding tool, that saves a trip to the dashboard: edit in WordPress, then ask Claude to purge the CDN.

9. Squish support: the AI assistant and support cases

The dashboard’s AI assistant answers in under a minute and can open a support case for you. Asked how to install WordPress, it suggested WP-CLI over SSH and offered to have the team do the install, which is what works on CyberPanel 3.0. Some of the panel routes it named lead to CyberPanel’s pricing page on this version, so stick with the WP-CLI steps in section 4 or take up the offer of a hand install.

For questions that need a human, the dashboard has support cases. We opened one about backups and brute-force protection on a Thursday at 19:18 UTC. The confirmation promised an email from a person within one business day. The answer came 1 hour and 23 minutes later in the case thread on the dashboard. fail2ban (section 6) was already on the server when it arrived, and the Backups screen (section 7) appeared later that evening.

Squish support case reply confirming daily backups kept 7 days and fail2ban for SSH and WordPress

The reply was signed by Casey, who is also our contact at Squish for this sponsored review, so your own reply time may differ; the promise is one business day. Use the assistant for “where is the button” questions, and open a case for anything about what your plan includes.

Squish says accounts that spend $1,000 or more a year also get a dedicated account manager, a named person who knows the setup.

10. Squish vs Cloudways

Cloudways is the closest managed alternative at this size, with the same 2 vCPU, 4 GB and 80 GB, so the difference is what each adds on top. Prices are from Squish’s plan catalogue and Cloudways’ published pricing on the day we tested:

Squish Managed Cloud StudioCloudways Flexible Medium, 4 GB
Price$50/mo$54/mo
Server2 vCPU, 4 GB, 80 GB2 vCPU, 4 GB, 80 GB
Transfer4 TB4 TB
Control panelCyberPanel, or Plesk for $25/mo moreCloudways’ own platform
CDNBunny, on by defaultOptional add-on
Firewallfirewalld, fail2ban jails for SSH and WordPress, and ModSecurity in logging modeBuilt-in firewall with IP blocking listed
BackupsDaily, kept 7 days, whole-disk restore; 30 days for $9/mo moreOffsite at $0.033 per GB

At list price, excluding promotions, Squish comes in $4 a month cheaper with the CDN on from day one. Cloudways lists a built-in firewall and offsite backups on its pricing page, so compare the two if those matter most to you.

Studio sits second in a five-plan line-up, all of them managed by Squish. Squish’s catalogue lists these monthly prices, with a lower locked-in rate for longer terms: 5% off for 24 months and 10% off for 36 months.

PlanvCPURAMDiskTransferPrice
Nook12 GB50 GB2 TB$30/mo
Studio (tested)24 GB80 GB4 TB$50/mo
Workshop48 GB160 GB5 TB$110/mo
Warehouse816 GB320 GB6 TB$250/mo
Factory8 dedicated16 GB100 GB6 TB$550/mo

Nook comes with CyberPanel or no panel; Studio and up can swap in Plesk for $25 a month more, and a custom build starts at $75. Squish says you can move a Studio server up to Workshop, Warehouse or Factory yourself, with the charge prorated, so starting on the smaller plan doesn’t lock you in. If the Upgrade screen tells you to contact support instead, as it did on our review account, Squish says that’s a known bug being fixed. For teams that outgrow Factory, Squish also offers Managed AWS from $5,000 a month, deployed into your own AWS account and quoted to fit; we didn’t test it.

What to set up on a new Squish server

None of these takes long, and each has its fix earlier in this review:

  • Install WordPress with WP-CLI: CyberPanel 3.0 charges for its own installer, so use the commands in section 4, or ask support to do it.
  • Lock port 8090 to your IP: the panel listens to the world with a self-signed certificate until you add the firewalld rules from section 6.
  • Add a per-username login limiter or two-factor: Squish’s fail2ban jail stops repeat offenders, and a WordPress plugin catches bots that rotate addresses.
  • Switch ModSecurity to blocking: it arrives logging only, and the one-line change in section 6 makes it block.
  • Set a cache header: without one, the edge and browsers keep pages for 30 days. The mu-plugin in section 3 fixes it.
  • Add per-site backups to a remote destination: Squish’s daily backups restore the whole disk, and a remote CyberPanel destination gives you per-site copies.
  • Reboot after kernel updates: they install on their own and wait for you.

Who should pick Squish Managed Cloud

Squish fits people who want their own server without assembling DNS, CDN and a panel themselves, and who’ll do a little hardening on day one. Start from what your site does:

  • A blog or brochure site that leaves shared hosting: Squish Studio. Cached pages were fast from both places we measured, setup takes minutes, and $50 covers what a beginner would otherwise spend a weekend on.
  • You live in Claude Code or Cursor: Squish. The MCP server with preview-then-confirm writes is the most useful extra we found on this plan.
  • A store or members site where most pages skip the cache: the 4 vCPU Workshop plan gives uncached pages the headroom they need.

If you pick Squish, the day-one setup list takes about half an hour. After that, it’s a quick, well-connected server at a fair price, run by a team that acts on feedback.

Keep reading

PHP2Shell on End-of-Life PHP 8.1, 8.0 and 7.4 (WHMCS, ionCube) Php PHP2Shell on End-of-Life PHP 8.1, 8.0 and 7.4 (WHMCS, ionCube) Install Nextcloud on Ubuntu 26.04 LTS Cloud Install Nextcloud on Ubuntu 26.04 LTS How To Install GLPI on Ubuntu 24.04 / 26.04 LTS Debian How To Install GLPI on Ubuntu 24.04 / 26.04 LTS Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Cloud Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Install CyberPanel on Ubuntu 26.04 / 24.04 with Let’s Encrypt Ubuntu Install CyberPanel on Ubuntu 26.04 / 24.04 with Let’s Encrypt Install Immich on Ubuntu 26.04 LTS Cloud Install Immich on Ubuntu 26.04 LTS

Leave a Comment

Press ESC to close