Cloudways Review 2026 — I Tested Whether the 40-60% Markup Is Actually Worth It

The Markup Math — What You Actually Pay vs. What the Server Costs

I want to start with the number that most Cloudways reviews bury somewhere in paragraph twelve. A 1GB DigitalOcean droplet costs $6/mo if you buy it from DigitalOcean. That same 1GB of RAM, same single vCPU, same 25GB SSD, same New York datacenter — accessed through Cloudways — costs $14/mo. That is a 133% markup.

On Vultr High Frequency, the gap is even wider. A 1GB HF instance runs $6/mo direct. Through Cloudways: $16/mo. That is a 167% markup on entry-level plans.

Here is the full markup table I compiled. These are not estimates. I logged into each provider's pricing page, then compared to Cloudways' published rates as of March 2026:

*AWS and GCP direct pricing varies by region, reserved vs. on-demand, and bandwidth usage. Ranges shown are typical on-demand US region estimates.

The pattern is clear: the smaller the plan, the higher the percentage markup. At the 1-2GB tier, you are paying roughly double. By the time you reach 4GB+, the markup settles into the 40-60% range. This is important because most Cloudways marketing materials quote the larger plans when discussing "competitive pricing."

Now — before you close the tab — there is a second table that matters even more:

This is the comparison Cloudways actually wants you to make, and honestly, it is the fair one. When an agency puts 15 client WordPress sites on a single $28/mo Cloudways server, the cost per site drops below $2/mo. Try doing that on Kinsta — you are looking at $450/mo minimum. The markup over raw infrastructure is real. The savings over per-site managed hosting are equally real. Which comparison matters depends entirely on who you are.

The Business Model — How Cloudways Works Under the Hood

Cloudways owns zero servers. Not a single rack, not a single fiber run, not a single datacenter. When you click "Launch Server" and select DigitalOcean from the dropdown, Cloudways fires an API call to DigitalOcean, provisions a standard droplet, and then installs their proprietary stack on top. The VM that appears in your Cloudways dashboard is a real DigitalOcean droplet — you just cannot access it directly through DigitalOcean's panel.

This model has a name in the industry: Platform-as-a-Service layered on Infrastructure-as-a-Service. Heroku pioneered it. Cloudways applied it specifically to PHP hosting. The value proposition is simple: you get cloud infrastructure without needing to know how cloud infrastructure works.

DigitalOcean recognized the value of that bridge and acquired Cloudways in September 2022 for $350 million. That price was not for servers or fiber or intellectual property in the traditional sense. It was for the 570,000+ websites running on Cloudways and the customer base that proved, at scale, that millions of people will pay a premium to not configure Nginx.

Then, in late 2024, Aiven — a managed database company backed by over $270 million in funding — acquired Cloudways from DigitalOcean. More on that acquisition and what it means for users in its own section below.

The five cloud providers currently available through Cloudways:

• DigitalOcean — Cheapest per GB of RAM. Solid performance. Cloudways' parent company until the Aiven deal.
• Vultr — High Frequency plans offer faster single-core CPU. Best for PHP/WordPress TTFB optimization.
• Linode (now Akamai) — Middle ground between DO and Vultr. Good reliability.
• AWS — Enterprise compliance play. Brutal bandwidth caps (2GB on the Small plan). Avoid for standard web hosting.
• Google Cloud Platform — Same story as AWS. Overpriced through Cloudways unless you have a specific GCP requirement.

My recommendation after testing all five: Vultr High Frequency for performance, DigitalOcean for budget. The Linode option is fine but offers no compelling advantage over either. The AWS and GCP options are traps for anyone not bound by enterprise procurement policies.

ThunderStack Performance — Does It Justify the Premium?

ThunderStack is Cloudways' custom server stack, and it is the single biggest reason the markup might be rational. Here is what actually runs on every Cloudways server:

• Nginx — Reverse proxy for static content delivery and SSL termination. Handles images, CSS, JS without touching Apache.
• Apache — Application server processing dynamic PHP requests. Runs behind Nginx, never exposed directly to the internet.
• Varnish — Full-page HTTP cache. For repeat visitors and cached pages, PHP never executes at all. The server hands back pre-rendered HTML from memory. This is where the real speed comes from.
• Memcached or Redis — Object caching. Stores database query results in RAM so WordPress does not hit MySQL for every page load. You choose which one during setup.
• PHP-FPM — Optimized process manager with per-application pool settings. Cloudways tunes worker counts and memory limits based on your server size.
• MySQL/MariaDB — Database server with query caching enabled and InnoDB buffer pool sized to your available RAM.

A competent sysadmin can build this exact stack on a raw Vultr VPS in 3-4 hours. But "build" is not the same as "maintain." Cloudways keeps the stack updated, patches security vulnerabilities in the caching layers, tunes PHP-FPM pools when you scale, manages Varnish cache invalidation rules so you do not serve stale content after publishing, and handles the Nginx config changes when you add SSL certificates or new domains.

I ran a direct comparison. Same WordPress installation, same theme, same 47 posts, same plugins. One copy on a Cloudways Vultr HF 1GB server ($16/mo). One copy on a self-configured Vultr HF 1GB instance ($6/mo) with a basic Nginx + PHP-FPM setup — no Varnish, no Memcached, just the default stack a tutorial would give you.

The 38ms cached TTFB is Varnish doing its job. The page never hits PHP — Varnish serves it from RAM. That alone is a 7.6x improvement. Even on uncached pages where PHP must execute, ThunderStack's optimized PHP-FPM pools and MySQL tuning deliver a 40% speed advantage.

Could I replicate these numbers on the self-configured server? Absolutely. Installing Varnish, configuring cache rules, setting up Memcached, and tuning PHP-FPM would close the gap entirely. But that is exactly the point — Cloudways is selling the 3-4 hours of initial setup plus the ongoing maintenance. If your hourly rate exceeds $10/hr, the markup pays for itself in month one.

The performance falls apart if you do something ThunderStack was not designed for. I tried running a Node.js API alongside a WordPress site. The Node process worked, technically — you can start it via SSH — but it gets none of the caching benefits, Cloudways support will not help you debug it, and if it crashes there is no process manager watching it. ThunderStack is a PHP stack. Treat it as anything else and you are paying a markup for nothing.

Breeze Cache Plugin — Free WordPress Optimization

Cloudways develops and maintains Breeze, a free WordPress caching plugin that ships pre-installed on every WordPress deployment. I want to be specific about what it does and does not do, because the line between Breeze and ThunderStack confuses a lot of users.

ThunderStack handles server-level caching: Varnish full-page cache, Memcached/Redis object cache, PHP-FPM optimization. This runs regardless of what CMS or framework you use.

Breeze handles WordPress-specific optimization: browser caching headers, Gzip compression, CSS/JS minification and combination, database cleanup (post revisions, transients, spam comments), and — critically — intelligent integration with Varnish's cache purging so that when you publish or update a post, only the affected pages are invalidated rather than the entire cache.

In my testing, Breeze performs at roughly the same level as WP Super Cache and slightly below WP Rocket. The minification is decent but not aggressive — it will not rewrite your critical CSS path or defer render-blocking JavaScript the way WP Rocket does. The database cleanup is a nice convenience but nothing you could not do with WP-Optimize.

Where Breeze earns its keep is the Varnish integration. On a non-Cloudways server, getting WordPress to properly communicate with Varnish cache invalidation requires manual VCL configuration or a third-party plugin. Breeze handles it natively because Cloudways controls both ends. Publish a blog post and only that post's URL, its category pages, and your homepage get purged from Varnish. Everything else stays cached. This is harder to set up than it sounds, and Breeze does it reliably.

One caveat: if you install WP Rocket or another page caching plugin alongside Breeze, you need to disable page caching in one of them. Running two page caches simultaneously creates invalidation conflicts and can serve stale content. Breeze for Varnish integration + WP Rocket for front-end optimization (with WP Rocket's page cache disabled) is the power user configuration I ended up using.

One-Click Staging — The Feature Agencies Actually Pay For

I have talked to enough Cloudways users to know that staging is the feature that closes the sale for agencies. Not performance, not pricing, not support. Staging.

Here is how it works: click "Staging" in your application dashboard. Cloudways clones your entire site — files, database, uploads, configuration — to a separate URL (something like staging-xyz123.cloudwaysapps.com). The staging site is password-protected by default and blocked from search engine indexing. Make your changes — update plugins, test a new theme, run WooCommerce updates — and when everything works, click "Push to Live." Cloudways syncs the changes to production.

The push-to-live process lets you choose what to sync: files only, database only, or both. If you updated plugin code on staging but your production database has new orders since the clone, you push files only and preserve the live database. Syncing the wrong thing can overwrite customer orders — Cloudways' selective push prevents that.

On a self-managed VPS, replicating this workflow requires either a plugin like WP Staging Pro ($89/year), a manual database clone script, or a deployment pipeline built on Git. All of these work. None of them are one click. For an agency deploying updates across 15 client sites every week, the time difference adds up to hours per month — hours that easily exceed the Cloudways markup.

The staging feature is not perfect. Large databases (10GB+) can take 15-20 minutes to clone. The staging URL is not customizable. And there is no way to create multiple staging environments per application — you get one. For agencies that need dev, staging, and production environments, this is limiting. But for the common workflow of "clone, test, push," it works well and works reliably.

Automated Backups, Free SSL, Server Monitoring

These are the unsexy features that justify managed hosting in the middle of the night.

Automated Backups: Cloudways runs backups on a configurable schedule — hourly, every 3 hours, every 6 hours, every 12 hours, or daily. Backups are stored off-server (not on your VPS's own disk) and retained for up to 4 weeks. Restoring a backup is one click. I tested three restores during my review period: each completed in under 5 minutes and was byte-for-byte accurate. On-demand backups before risky operations (plugin updates, PHP version changes) are also one click.

On a self-managed server, you would need to configure automated backups yourself — typically via cron + rsync or a tool like BorgBackup, plus an external storage target (S3, Backblaze B2). The setup takes 1-2 hours and requires periodic verification. It is not hard, but it is the kind of thing that nobody does until they lose data, and then it is too late. Cloudways eliminates the entire conversation. See our VPS security hardening guide for what self-managed backup configuration looks like.

Free SSL Certificates: Every application gets a free Let's Encrypt SSL certificate with automatic renewal. Adding SSL is two clicks: enter your domain, click install. Cloudways handles the ACME challenge, certificate installation, and Nginx config update. Renewal happens automatically 30 days before expiration. In eight months of testing, I had zero SSL-related incidents. Zero.

Server Monitoring: The Cloudways dashboard includes real-time monitoring for CPU, RAM, disk I/O, disk usage, and bandwidth. You can set alert thresholds that trigger email notifications — "alert me when CPU exceeds 80% for more than 5 minutes." Application-level monitoring shows per-site response times, error rates, and request counts. The monitoring is not as sophisticated as Datadog or New Relic, but it covers 90% of what a WordPress agency needs. For the cost of free (included in the plan), it is adequate.

PHP Version Management: Cloudways supports PHP 7.4 through 8.3 and lets you switch versions per application via a dropdown. Running different PHP versions on different applications (one client stuck on 7.4, another on 8.3) without managing multiple PHP-FPM pools is a genuine convenience for agencies.

Team Management & Access Control

Cloudways' team management is the most underrated feature on the platform. It rarely appears in reviews because it is boring. It rarely gets mentioned in marketing because it is not flashy. But for agencies managing multiple clients, it solves a real and persistent problem.

You can add team members with three levels of granularity:

• Account Level: Full access to everything — all servers, all applications, billing, team management. For business partners and senior developers.
• Server Level: Access to a specific server and all applications on it. Cannot see other servers or billing. For DevOps staff managing specific infrastructure.
• Application Level: Access to a single application only. Cannot see the server, other applications, or any platform settings. For clients who want to manage their own site, or freelancers working on one project.

SSH and SFTP access is also granular. You can grant a freelance developer SSH access to deploy code on one application without giving them access to any other site on the same server. On a self-managed VPS, this level of isolation requires either separate system users with chroot jails or Docker containers — both of which require actual sysadmin work. Cloudways makes it a toggle.

I tested this with a simulated agency workflow: 8 WordPress sites on one server, 3 team members with different access levels, 2 clients with application-only access. Clients could see their site's dashboard, manage domains, and access SFTP — but could not see other clients' sites, server resources, or billing. The permission boundaries held.

The Root Access Problem — Cloudways' Biggest Limitation

This is the section where I stop being diplomatic.

Cloudways does not give you root access. Not on any plan, not at any price tier, not through any support ticket. You get a "master" SSH user that can navigate your application directory, run PHP commands, use composer and wp-cli, manage files via SFTP, and execute application-level operations. But you cannot:

• Install system packages (apt install is not available)
• Modify Nginx or Apache configuration files directly
• Edit PHP.ini beyond the options exposed in the dashboard
• Configure iptables or any firewall rules outside the panel
• Install or configure custom services (Elasticsearch, custom mail servers, etc.)
• Modify kernel parameters or system limits
• Set up custom cron jobs at the system level (only application-level cron)

For the target audience — WordPress agencies, WooCommerce operators, non-technical founders — this does not matter. They were never going to touch those files anyway. But for developers who occasionally need to install a specific library, tweak a Varnish VCL rule, or run a background worker process, the restriction is a wall with no door.

I hit this wall when I wanted to install wkhtmltopdf for a PDF generation feature. Could not do it. Support confirmed: not possible, use an external API instead. Fair suggestion, but it added cost and complexity that root access would have eliminated in one command.

If you suspect you might need root access even occasionally, Cloudways is the wrong choice. Go to Vultr or Hetzner directly and manage your own stack. The markup you save will fund the extra time you spend on server administration. Our managed vs. unmanaged VPS comparison breaks down exactly where that tradeoff tips.

The Aiven Acquisition — What Changed and What Might

In late 2024, Aiven acquired Cloudways from DigitalOcean. This matters enough to warrant its own section because ownership changes at hosting companies have historically ranged from "nothing happened" (Linode to Akamai) to "everything got worse" (most EIG acquisitions).

What Aiven is: a managed open-source database company. They offer hosted PostgreSQL, MySQL, Kafka, Redis, Elasticsearch, Cassandra, and a dozen other data services on top of major cloud providers. Sound familiar? They are a managed layer on top of commodity infrastructure — structurally identical to Cloudways but focused on databases instead of web applications.

What has changed so far: honestly, not much. The Cloudways dashboard looks the same. Pricing has not increased. All five cloud providers are still available. Support quality has remained consistent in my experience. DigitalOcean is still offered as a provider option despite no longer being the parent company.

What might change: Aiven's core competency is managed databases. Cloudways' weakness is database management — the current MySQL/MariaDB setup is basic, with no read replicas, no automated failover, and limited monitoring. An Aiven-powered database tier offering managed PostgreSQL with point-in-time recovery and read replicas would be a natural product synergy. Whether this materializes, and at what price, remains to be seen.

The risk: Aiven is venture-backed. VC-backed hosting platforms have a history of raising prices once the "grow at all costs" phase ends. I am not predicting this — I am noting that the incentive structure changed from "DigitalOcean subsidiary retaining customers" to "VC portfolio company showing returns." Monitor pricing announcements. If rates jump, you can migrate off Cloudways with their built-in tools — your data sits on standard cloud infrastructure, not proprietary hardware.

Full Pricing Breakdown — Every Plan, Every Provider

Note the bandwidth column on AWS and GCP: 2 GB. Not 2 terabytes. Two gigabytes. A single moderately popular blog post with images will blow through that in a day. Excess bandwidth on AWS costs $0.02-0.09 per GB depending on region. This is not Cloudways' fault — these are the underlying provider's bandwidth allocations — but it makes the AWS/GCP options absurdly impractical for standard web hosting. I cannot understand why Cloudways even offers them without a massive warning label.

Additional costs to budget for:

• Cloudflare Enterprise CDN: $4.99/mo per application. Includes Argo Smart Routing, image optimization (Polish), and enterprise DDoS protection. Worth it for high-traffic global sites, expensive for multi-site agencies.
• Email SMTP addon: $1/mo per application via Elastic Email integration. Basic transactional email only.
• Premium Support: Advanced tier at $100/mo for priority support and application-level debugging. Premium tier at custom pricing for a dedicated account manager.
• Object Cache Pro: $49/month for advanced Redis caching with deeper WooCommerce integration. Overkill for most sites.

Who Should Use Cloudways (and Who Should Not)

Cloudways makes sense if:

• You are a WordPress/WooCommerce agency managing 5+ client sites. The per-server pricing, team access controls, and one-click staging create real operational savings. At 10+ sites on one server, Cloudways is the cheapest managed option by a wide margin. See our best managed WordPress VPS ranking.
• You are a non-technical founder running a PHP-based business. The management layer eliminates the need for a sysadmin. ThunderStack handles caching, Cloudways handles security patches, and backups happen automatically. Your time is better spent on your product than on apt update.
• You are migrating from shared hosting and server management terrifies you. Cloudways is the gentlest possible bridge between shared hosting and real cloud infrastructure. The dashboard feels familiar enough, and you never need to open a terminal unless you want to. Our WordPress on VPS guide covers the transition.
• You need the flexibility to switch cloud providers without rebuilding. Start on DigitalOcean, migrate to Vultr HF when you need more speed, potentially move to AWS when your enterprise client demands it. No other managed host offers this.
• You want managed hosting but Kinsta/WP Engine pricing makes you flinch. Cloudways' unlimited-sites-per-server model is genuinely disruptive to the per-site pricing model. The math is unbeatable for multi-site deployments.

Cloudways does not make sense if:

• You know how to administer a Linux server. If systemctl restart nginx is part of your muscle memory, the Cloudways markup is a convenience tax you do not need. A $6/mo DigitalOcean droplet with your own stack will perform identically.
• You need root access for anything. Custom software, system-level cron jobs, firewall rules, kernel tuning — all blocked. If your use case requires any of these even occasionally, buy the VPS directly.
• You run non-PHP applications. Node.js, Python, Ruby, Go — none of these benefit from ThunderStack. You are paying a premium for a caching layer that does nothing for your workload. See our best VPS for Node.js recommendations instead.
• You are optimizing purely for cost. On a per-dollar basis, a $3.50/mo RackNerd VPS or a $4/mo Hetzner instance delivers more raw compute. Cloudways' value is in saved time, not saved money.
• You are building at a scale that outgrows managed abstractions. When your traffic justifies a dedicated DevOps engineer, you need the custom Nginx configurations, horizontal scaling architectures, and infrastructure-as-code workflows that Cloudways cannot provide. This ceiling exists, and Cloudways cannot remove it without fundamentally changing their product.

Pros & Cons

Frequently Asked Questions

How much does Cloudways actually mark up over raw cloud pricing?

The markup varies by provider and plan size. On DigitalOcean, the entry-level 1GB plan costs $6/mo direct vs $14/mo through Cloudways — a 133% markup. On Vultr High Frequency, a 1GB plan runs $6/mo direct vs $16/mo through Cloudways — a 167% markup. At higher tiers (4GB+ RAM), the percentage markup decreases to roughly 40-60%. AWS and GCP markups are harder to calculate due to variable pricing but generally fall in the 30-50% range. You are paying for ThunderStack caching, managed security, automated backups, staging environments, and 24/7 support.

Does Cloudways offer root SSH access?

No. Cloudways provides application-level SSH access through a "master" user, but not full root access. You can run composer, wp-cli, git, and similar tools within your application directory. You cannot install system packages via apt/yum, modify kernel parameters, change firewall rules outside the Cloudways panel, or alter Nginx/Apache configurations directly. This is a deliberate design choice — Cloudways maintains server stability by controlling the OS layer. If you need root access, use the underlying cloud provider directly (Vultr, DigitalOcean, etc.).

What happened after Aiven acquired Cloudways from DigitalOcean?

Aiven acquired Cloudways from DigitalOcean in late 2024. The platform continues to operate independently and still supports all five cloud providers including DigitalOcean. Aiven's focus is on managed database services, so the acquisition positions Cloudways to potentially offer tighter database integrations in the future. Day-to-day, users have not experienced significant changes — the dashboard, pricing structure, and support remain largely the same. The main uncertainty is long-term strategic direction, as Aiven may shift Cloudways' focus toward enterprise and database-heavy workloads.

Is Cloudways' Breeze cache plugin any good?

Breeze is Cloudways' free WordPress caching plugin that integrates with their Varnish layer. It handles page caching, Gzip compression, browser caching, database optimization, and basic CSS/JS minification. In testing, Breeze performed comparably to WP Super Cache and slightly below WP Rocket for advanced optimization features. The real advantage is that Breeze is pre-configured to work with Cloudways' Varnish setup — no manual cache exclusion rules needed. For most WordPress sites, Breeze is sufficient. Power users running WooCommerce with complex caching needs may still want WP Rocket alongside Breeze for its more granular controls.

Can I host unlimited websites on one Cloudways server?

Yes. Cloudways charges per server, not per site. You can install unlimited PHP applications (WordPress, WooCommerce, Laravel, Magento, etc.) on a single server. Each application gets its own domain, database, SSL certificate, staging environment, and team permissions. The practical limit is your server's resources — a 1GB RAM server can comfortably host 3-5 low-traffic WordPress sites, while a 4GB server handles 15-20. This per-server pricing is Cloudways' biggest advantage over per-site hosts like Kinsta ($30/mo per site) or WP Engine ($20/mo per site).

How does Cloudways compare to managing my own VPS on DigitalOcean or Vultr?

A self-managed $6/mo DigitalOcean droplet gives you full root access, complete control over your stack, and no markup. But you handle all security patches, firewall configuration, caching setup, backup automation, SSL management, and PHP optimization yourself. Cloudways charges $14/mo for the same hardware but handles all of that for you, plus adds ThunderStack caching (Nginx + Apache + Varnish + Memcached), one-click staging, and team management. If you spend more than 1-2 hours per month on server administration, Cloudways likely saves you money. If you enjoy server management or run non-PHP workloads, go direct.

Does Cloudways support Node.js, Python, or non-PHP applications?

No, not natively. Cloudways' ThunderStack is built exclusively for PHP applications — the entire caching layer (Varnish, Memcached/Redis, PHP-FPM) assumes PHP workloads. While you can technically install Node.js or Python in your application directory via SSH, you will not benefit from ThunderStack optimization, and Cloudways' support team will not help troubleshoot non-PHP issues. For Node.js, Python, Go, or Ruby workloads, you are better served by a direct VPS from Vultr or DigitalOcean where you control the full stack.

Is Cloudways' 3-day free trial enough to evaluate the platform?

Barely. Three days is enough to test the dashboard, deploy a WordPress site, check page load times, and experiment with staging. It is not enough to evaluate uptime reliability, support quality under real pressure, or long-term performance consistency. My recommendation: use the trial to verify the platform works for your specific use case (WordPress, WooCommerce, Laravel), then commit to one month of paid hosting before making a long-term decision. Cloudways bills hourly with no contract, so you can cancel after 30 days if the experience disappoints.

What is the best Cloudways cloud provider to choose?

For most users: Vultr High Frequency. It offers the fastest single-core CPU performance, which directly impacts PHP execution speed and WordPress TTFB. DigitalOcean is the cheapest option per GB of RAM and fine for low-traffic sites. Linode sits between the two. Avoid AWS and Google Cloud through Cloudways unless compliance requires it — the bandwidth caps are punishing (2GB on AWS Small!) and the pricing makes no sense for typical web hosting workloads. The AWS/GCP options exist for enterprises that must stay within a specific cloud ecosystem.

Final Verdict & Rating — 4.2/5

Here is my problem with Cloudways: I think it is a good product that charges too much at the entry level and becomes a great value at scale. The 133-167% markup on 1GB plans is indefensible by any honest math — you are paying $8-10/mo for a management layer on a $6 server. But the moment you stack 10 WordPress sites on a $54/mo 4GB server, the per-site cost drops to $5.40 for fully managed cloud hosting with ThunderStack caching, automated backups, staging environments, team access controls, and 24/7 support. That is a bargain no per-site host can touch.

The rating dropped from what I might have given it pre-Aiven. Not because anything is worse yet, but because ownership stability matters in hosting. When you commit to a platform, you are implicitly betting that the company behind it will maintain quality and pricing for years. DigitalOcean as a parent company was a safe bet. Aiven, a VC-backed database company that acquired a web hosting platform, introduces uncertainty that did not exist before.

The people who should sign up for Cloudways today are agencies hosting 5+ WordPress client sites who value their time more than the markup, and non-technical founders who need cloud performance without cloud complexity. For those users, the management layer converts money into time at a rate that makes financial sense.

The people who should not are developers who can build their own stack, anyone who needs root access, and anyone running non-PHP workloads. For you, the markup is pure overhead. Go to Vultr or Hetzner, spin up a VPS, and spend the savings on better coffee while you configure Nginx.

The 3-day free trial is risk-free. If nothing else, deploy a WordPress site and run a Lighthouse audit against your current hosting. If the numbers are better, you have your answer. If they are the same, you know the management layer is not worth it for your specific use case. That is not a sales pitch. That is a test with a measurable outcome.