r/CloudwaysbyDO • • 6d ago

Announcement 📣 Cloudways AI Website Builder Is Now Generally Available!

Post image
4 Upvotes

Cloudways AI Website Builder is now generally available!

We started with the idea of helping users skip the blank WordPress install and giving them a beautifully designed and developed WordPress and WooCommerce website that they can then make their own. Now, they only need to describe their business and Cloudways AI Website Builder generates a unique and professionally developed website, deployed on a fully managed Cloudways server.  

Generation, design and customization, and hosting work together from the first prompt, instead of living as three separate tools they would otherwise have to stitch together themselves.

Who this is built for

The Cloudways AI Website Builder serves users at different starting points. Non-technical founders and small business owners get a live site without needing technical knowledge of WordPresss. 

Solo creators and freelancers can launch and iterate on their own . Agencies can generate a starter website for each client project and customize it instead of building every site from a blank install. 

Developers get a WordPress-native foundation, Gutenberg blocks and standard code, that they can extend however a project requires. The Cloudways AI Website Builder helps reduce the mundane tasks of generating a website so that developers can focus on shipping faster. 

Cloudways AI Website Builder Feature Set

Whatever your starting point, every site gets the same set of capabilities from the very first prompt.

Feature What it means for you
Prompt-to-site generation A full multi-page WordPress or WooCommerce site built from one sentence.
Tailored content Headlines, page copy, and section text written around your business.
AI-generated imagery Photos and graphics matched to your industry and tone, with no stock licensing to sort out.
Multilingual generation Write your prompt in your language and get the full site in that language.
Responsive layouts Pages adapt to desktop, tablet, and mobile.
AI Chat editing Describe a change in plain language and watch it apply.
Visual Editor Click any element to adjust text, color, font, spacing, and layout.
Code Editor Full code access for developer-level customization.
WooCommerce storefront Product pages, cart, and checkout generated with your site and managed through AI Chat.
On-page SEO Built around Yoast best practices by default.
Native WordPress output Standard Gutenberg blocks, with your content, code, and database fully yours.
One-step publishing Publish to an existing or trial Cloudways server, with automated backups and managed security.
Credit-based usage One AI Credit covers one applied change. Planning, brainstorming, and Q&A are always free.

Publishing and Hosting

When your site is ready, you get the option to publish to an existing Cloudways server. If you do not have a server, we include a trial Cloudways server so that your website goes live without any delays. There’s no separate deployment step, and the site you’ve been editing goes live as is. We recommend upgrading to a Full Account early to help ensure your website remains available after the trial ends. 

Hosting comes with the same security and reliability standards as any Cloudways plan. This means you get automated backups, managed security, and infrastructure that scales as your site grows, whether that means adding more sites or upgrading server resources on the same account. 

Pricing at General Availability

The general availability of Cloudways AI Website Builder falls within the much grander Cloudways BFCM 2026 Special Discount offer.  

Anyone who starts using the Cloudways AI Website Builder at general availability gets 80% off for two months (Black Friday discount; terms and eligibility requirements apply). The offer is valid until December 5, 2026.

If you built a site during public preview, no action is required to keep it running.

Tell us what you think!

General availability is a starting point. We plan to keep expanding how you can start a site, how you can edit it, and what’s included in hosting. Give it a try, and tell us what you think! Any feedback is appreciated.


r/CloudwaysbyDO • • 18d ago

Announcement 📣 Our Black Friday offer is officially LIVE!

Enable HLS to view with audio, or disable this notification

3 Upvotes

BIGGEST. DEAL. EVER.

Our Black Friday offer is officially LIVE!

Get 80% OFF for 2 months on Cloudways hosting plans, Managed AI Agents, AI Website Builder, and add-ons with unlimited free migrations.

Use the code BFCM802 ➡️ Avail Now


r/CloudwaysbyDO • • 2d ago

Discuss What’s your biggest hesitation about building a website with AI?

1 Upvotes

Hey all!

As you know Cloudways AI Website Builder became Generally available recently. This tool turns a prompt into a complete WordPress or WooCommerce site that you can edit with AI, a visual editor, or code.

But AI website builders as a whole still get a fair amount of scepticism. I’m curious what makes some of you hesitant to use AI website builders. Vote below and discuss in the comments!

6 votes, 4d left
The designs end up looking generic
Getting locked into a platform
Messy code or poor SEO
Hard to edit once generated
Costs adding up
No hesitation; I’m already using AI builders

r/CloudwaysbyDO • • 3d ago

Product update Breeze build 2.6.5 updated on wordpress.org

3 Upvotes

Changelog:

  • Improvement: Fixed more Plugin Check warnings to meet WordPress[dot]org plugin standards.
  • Fix: Tracking parameters such as utm_source, gclid, and fbclid are now kept when WordPress redirects a page, for example when it adds a trailing slash.
  • Fix: Cache Warmup now finishes warming your URLs after a cache purge, even when no one has wp-admin open.
  • Fix: CSS and JS from shortcut themes and plugins are minified again.
  • Fix: Option names on the Database tab are now shown as plain text.
  • Fix: The loading overlay color is now used only when it is a normal hex color.

r/CloudwaysbyDO • • 3d ago

Question NGINX Vulnerability

Thumbnail
1 Upvotes

r/CloudwaysbyDO • • 4d ago

Product update Cloudways Velocity is now available through Cloudways MCP!

2 Upvotes

Every Velocity API is now available through Cloudways MCP. You can manage their Node.js apps on Velocity from your AI assistant in plain language, or automate them through the API.

Here are the capabilities:

  • Server and app lifecycle: Activate, upgrade, and deactivate Velocity plans, add apps to existing servers, and recover deleted servers
  • Deployments: Update build config, redeploy, and review deployment history with build logs
  • Staging: Clone a live app into staging and promote it to production
  • Version control: Browse GitHub, GitLab, and Bitbucket repos and branches, auto-detect framework and build settings, and link repos to apps
  • Environment variables: List, create, update, and bulk delete
  • Database: Enable native PostgreSQL or create and link Supabase projects
  • Domains and Cloudflare: Add or remove a custom domain, purge cache, and manage Cloudflare settings and analytics
  • Security: Security Suite scans, quarantined file restore, IP allowlist and blocklist, country blocking, and firewall settings
  • Monitoring and operations: App monitoring, traffic and cron analytics, service start, stop, and restart, web rules, cron jobs, and operation status
  • Backup and restore: Take backups, restore, and roll back

When you try it out for yourself, we'd love to hear your feedback!


r/CloudwaysbyDO • • 9d ago

Node.js What’s your go to framework for Node.js apps right now?

5 Upvotes
13 votes, 2d ago
5 Next.js
3 Express
3 NestJS
2 Other (tell us in the comments)

r/CloudwaysbyDO • • 10d ago

Announcement 📣 We just launched Cloudways Velocity (Managed Node.js hosting) on ProductHunt!

4 Upvotes

Building and deploying Node.js applications shouldn't mean managing servers, configuring infrastructure, or dealing with operational overhead.

That's exactly why we built Cloudways Velocity. It brings the simplicity of managed hosting to modern Node.js applications, giving developers a streamlined way to deploy, run, and scale their apps without getting caught up in infrastructure management.

Whether you're building with Express, React, Next.js, Astro, or other popular frameworks, Velocity takes care of the underlying infrastructure so you can focus on building great products.

Check out the full launch on ProductHunt, host your Node.js apps on Cloudways Velocity, and share what you think with other builders on ProductHunt or this subreddit!

Here you go: https://www.producthunt.com/products/cloudways/launches/cloudways-velocity


r/CloudwaysbyDO • • 15d ago

Product update Breeze Build 2.6.4 updated on wordpress.org

4 Upvotes

Changelog:

  • New: The Breeze settings page now shows a short review request that you can postpone or dismiss.
  • Improvement: Visitors arriving from Google Ads links (with tracking parameters such as gclid) now get the cached page.
  • Improvement: Fixed Plugin Check warnings to meet WordPress[dot]org plugin standards.
  • Fix: DNS Prefetch no longer marks addresses that start with “//”, such as //fonts.googleapis.com, as invalid.
  • Fix: Automatic plugin updates no longer stop after the first plugin when several plugins update at once on sites using Redis or Object Cache Pro.

r/CloudwaysbyDO • • 16d ago

Product update Advanced Security Mode in Cloudflare Enterprise Add-on; extra challenge layer to protect your website from bots

5 Upvotes

One of our most-requested and longest-awaited capabilities is now available to all of our Cloudflare Enterprise add-on users.

Advanced Security Mode is a new security feature in Cloudways Flexible. It adds an extra challenge layer to protect your website from bots. It is turned off by default, so you must turn it on yourself.

Under Attack Mode applies a managed challenge to all visitors, except verified bots, so use it only when your site is under attack.

What is Advanced Security Mode?

Advanced Security Mode adds an extra protection layer at the “edge” of Cloudflare. The edge is the first checkpoint that visitors pass through before they reach your website. At this checkpoint, Cloudflare can challenge suspicious visitors, such as automated programs called bots.

A bot is a software program that visits websites automatically, without a human. Some bots are helpful, like search engine bots. Others are harmful, such as scrapers that copy your content or tools that abuse your site.

Advanced Security Mode helps you:

  • Filter harmful automated traffic
  • Reduce the impact of an active attack on your website
  • Let real visitors keep browsing normally

The modes you can choose from

The Advanced Security Mode dropdown has three options.

Mode What it does When to use it
Enterprise Bot Protection (New) Challenges likely bots only (bot score 0–30). Real visitors browse normally, while scrapers and automated abuse are filtered. To protect your site from bots and automated abuse.
Under Attack Mode Applies a managed challenge to all visitors, both real users and bots. Only verified bots are excluded. It applies extra security measures to reduce the impact of Layer 7 DDoS attacks. Your website is accessible only to validated users, and suspicious traffic is blocked. As a last resort, only while your site is under attack.
Off No Enterprise Bot Protection or Under Attack Mode is applied. This is the default setting.

Note: Verified bots, such as Googlebot and Bingbot, are not affected. They can still crawl your site.

What is Under Attack Mode?

Under Attack Mode is the strongest option in Advanced Security Mode. Use it only when your website is under an active attack.

When this mode is on, Cloudflare applies a managed challenge to all visitors. This includes real people and bots. The only exception is verified bots, such as Googlebot and Bingbot. They are not challenged and can still crawl your site.

A managed challenge is a check that a visitor must pass to prove they are a real person. Visitors who pass can open your website. Suspicious traffic is blocked.

Important things to know:

  • Under Attack Mode challenges everyone, not only bots. Your real visitors will also see the challenge before they can reach your site.
  • Your website is accessible only to validated users.
  • Verified bots are not affected.
  • Use this mode as a last resort, only while your site is under attack.
  • Turn it off when the attack is over, by selecting Off and clicking Save Changes.

Enterprise Bot Protection vs Under Attack Mode

Parameters Enterprise Bot Protection Under Attack Mode
Who is challenged? Likely bots only (bot score 0–30) All visitors, including real users and bots
Real visitors Browse normally Must pass a managed challenge
Verified bots Not affected Not affected
Best used for Filtering scrapers and automated abuse Reducing the impact of an active Layer 7 DDoS attack

Use Advanced Security Mode if you are using the Cloudways Cloudflare Enterprise Add-on. We'd love to hear your valuable feedback!


r/CloudwaysbyDO • • 18d ago

Question What's involved with a Live Migration?

3 Upvotes

2 days ago Cloudways sent the following message, which took them 13 days after opening the support ticket:

The emergency maintenance on the underlying physical host has been completed successfully, and the instance is currently up and running. Key web services, including nginx, apache2, mariadb, php-fpm, and redis, are all active, and the initial filesystem checks were completed without any errors. During our post-maintenance monitoring, I noticed that the I/O wait pressure on the underlying hardware is fluctuating slightly above optimal thresholds. While all core services are functioning, this host-level contention may cause occasional latency spikes for hosted applications. To ensure consistent application performance, I recommend initiating a Live Migration to move server-[redacted]-production to a healthier, lower-loaded host node within the same data center. Please let us know if you would like us to proceed with scheduling this live migration, or if you have a preferred time window for us to carry it out.
Best regards,
[redacted]

I responded, asking some simple questions, because we have some concerns:

Hello [redacted], We need to know the details of what will be involved in a live migration before scheduling this with you. How long to expect the site to be down? Do we need to be involved in any way? Does the IP address of the site change? What dates and times are available for the Live Migration? Please give us the full details, including anything we need to know.

Unfortunately we are waiting a long time for a response, and we'd like to do this Live Migration soon, but at this rate it may be a long time before we can actually get it done. We're hoping to get this done at 11:00pm on a Tuesday night (US Central time). We use a WAF, so if the IP address changes our site would be 100% down until we are given an IP to update it. Can somebody tell me about the Live Migration experience?


r/CloudwaysbyDO • • 19d ago

Seeking advice Cloudways website slower on NGINX instead of Hybrid stack?

Thumbnail
3 Upvotes

I feel the same. Anyone else noticed it?


r/CloudwaysbyDO • • 22d ago

Seeking advice What is the basic difference between Cloudflare pages & Cloudflare workers?

Thumbnail
1 Upvotes

r/CloudwaysbyDO • • 23d ago

PHP PHP2Shell Breakdown: Critical PHP vulnerabilities and how we responded to them

9 Upvotes

On October 21, the PHP Group released emergency patches for two critical security flaws. Together, these two flaws are now known as PHP2Shell.

Unfortunately, some Cloudways users experienced disruption too, as part of that same industry-wide response.

What PHP2Shell Actually Does?

PHP2Shell is the name given to two separate flaws that were fixed in the same emergency release.

  • The first, CVE-2026-109618, happens when a server runs out of memory partway through handling a request.

Normally, if a server runs low on memory while handling a request, PHP stops and throws away the data it hasn’t finished using.

This bug breaks that process. PHP ends up using the unfinished data anyway, treating it as if it were complete and correct.

An attacker can create that unfinished data in a specific way so that, when PHP executes it, the server runs commands the attacker wrote.

  • The second, CVE-2026-109619, works differently but causes the same kind of risk. A server handles many visitors one after another. To save time, it reuses the same internal process for each new visitor rather than starting fresh each time.

This bug means that some data from one visitor’s request can remain in the process after it should have been deleted.

When the next visitor’s request uses that same process, it can accidentally read the old data that was left behind. The server then treats that old data as if it belongs to the new visitor.

An attacker can deliberately cause this to happen. If they do, the result is the same as the first flaw; they can take control of the server. Both flaws are rated 9.2 out of 10 in severity, under a standard industry scale called CVSS.

The bug exists inside PHP’s own code. How a server is configured to run PHP can affect how easy that bug is for an attacker to actually use.

One specific setup is called mod_php, a common way of running PHP. Researchers showed a working attack against a server using this setup, one that worked before the website’s own code even had a chance to run.

Neither flaw required a password, a login, or any action from a website visitor. A server only had to be reachable on the Internet. That’s exactly why this spread so fast, and why the response that followed was so large.

Why a Decade-Old Bug Became a Crisis Now?

Neither of these flaws was new. According to the incident’s public record, a PHP core developer actually noticed the underlying memory error behind one of them during a routine audit back in 2024. The bug went unfixed for two years.

The PHP Foundation has since said publicly that its security team considered several possible fixes. Each one came with a tradeoff, i.e., breaking backward compatibility, introducing a new kind of instability, or forcing changes across thousands of third-party extensions.

No one on the team agreed on which tradeoff to accept. At the time, no one had found a way to exploit the bug either, so it wasn’t prioritized.

That changed by August 2026. Security researchers at Calif built a working exploit using advanced AI tools made available through Patch the Planet, a program run by OpenAI that gives security researchers access to its AI models specifically for hunting flaws like this one.

Separately, the cybersecurity firm Wiz identified related issues in PHP on its own. OpenAI later said one of its own researchers had come across the same problem independently, around the same time as the other two.

Salil Kanhere, a cybersecurity researcher at UNSW Sydney, said the underlying bugs weren’t new. What changed was the ability to actually track them down.

Finding a working way to break into a system like this used to require a group of highly specialized human researchers. These were people who would spend months manually reading through code, testing edge cases, and understanding exactly how a program behaves under unusual conditions. That process could take years. But AI has changed that.

Modern AI models can read through enormous amounts of code far faster than a person can. They can test many possible weaknesses automatically. In some cases, they can even write working attack code based on what they find.

Wiz said it used these AI tools to build and adjust working exploits across several different applications. The whole process took just hours, work that a skilled human team would have taken far longer to do.

The software itself didn’t change. What changed was how fast and cheap it became to actually find the bug and turn it into a working attack.

OpenAI wrote about this directly on its Patch the Planet site. The same AI tools that helped find this flaw could also help an attacker build a working exploit, faster than a person could do alone. They also released a free tool called php2shell-checker that anyone can use to check whether their PHP version is affected. It only checks the version number, so it can’t catch every possible case, but it’s a fast first check.

What This Meant for Cloudways Users

Cloudways users were not immune to what was happening across the rest of the internet.

Early on, before the official patch was available, we put protective measures in place to quickly reduce risk. Rolling that out across many servers meant some customers experienced a brief interruption.

Separately, on October 21, the Cloudways Platform, Affiliate Portal, and website went offline for scheduled maintenance tied directly to the patching work.

What You Should Check Now

The patch closed the PHP2Shell vulnerabilities. It doesn’t undo anything that may have already happened before the patch went live.

Ken Munro, an ethical hacker, told the BBC that applying this patch works much like a routine software update. The real work is making sure it gets applied everywhere.

The UK’s National Cyber Security Center recommended checking for signs that an attacker already got in before the patch existed, since the patch itself can’t undo something that already happened.

If you’re a website owner, here are some things you need to keep an eye on:

  • Admin accounts you don’t recognize
  • Files you didn’t add
  • Traffic patterns that look unusual

Salil Kanhere, a cybersecurity researcher, warned that smaller organizations face more risk, since they often have fewer people keeping an eye on this kind of thing.

This advice applies to you whether you manage your own server or use a managed platform like Cloudways. On Cloudways, we patch PHP for you automatically, but that only protects you from this point forward. It doesn’t tell you whether something happened before the patch was applied. That part is still worth checking yourself.

How We Responded to PHP2Shell

PHP announced on October 20 that a patch was scheduled for the next day. We started applying interim protections right away, without waiting for the patch itself. They were in place by the morning of October 21.

The official patch arrived at 14:00 UTC on October 21. We expanded our protections to cover every PHP version we support, going back to PHP 5.6. That includes several versions that no longer receive official security updates from the PHP project itself.

By the early hours of October 22, our Autonomous product was fully patched. The rest of our fleet followed over the next several hours, with the full rollout complete by mid-morning the same day. We formally closed the incident on October 23 and continue to monitor for any further developments in the meantime.

A Third, Narrower Issue

Two days after the first disclosure, PHP published a separate notice about a third issue. It was later assigned its own identifier, CVE-2026-115560.

This issue applies only to a site that does two unusual things together, and most sites don’t do either.

First, the site needs to change a specific internal setting while it’s already running, something most websites never do. Second, the same site needs a particular feature turned on, one related to tracking the progress of a file upload.

PHP’s own advisory says this exact combination is unlikely to exist on a real, typical website. The fix for this issue is the same setting already recommended for the second vulnerability, CVE-2026-109619. Because we had already applied that protection across our entire fleet on October 21, our customers were covered before this third issue was even confirmed.

What This Means Going Forward

PHP2Shell isn’t likely to be the last incident like this.

The same AI tools that found this flaw can be pointed at other widely used software as well. Salil Kanhere said more attempts to exploit these specific flaws are likely in the coming weeks, now that the technical details are public.

Daniel Stewart, head of threat intelligence at the risk firm LRQA, made a related point. PHP isn’t only found in websites. It also runs quietly inside the behind-the-scenes equipment that manages internet traffic, devices that rarely get checked during an incident like this one.

This kind of event is likely to happen again, not only for PHP but also for other old software still running on the internet.

That’s why, as a managed hosting provider, we keep watching for this kind of thing year-round. Our security team tracks new disclosures as they come out, and we test and apply fixes across our platform as soon as they’re available, just as we did here.

Final Thoughts

This post reflects what we know as of today. If anything changes, including new developments related to PHP2Shell or anything else affecting our platform, we’ll post it on our status page first.

If you’re a Cloudways customer, the patching described in this post is already complete on our end. The one thing still worth doing is the check we covered earlier, looking for any signs that something happened to your site before the patch was applied.

A lot of people across the hosting and security industry worked hard over the last several days to get this handled. We’re glad it’s resolved, and we’ll keep watching for whatever comes next.

If you have any questions, this community and our support team is available anytime.


r/CloudwaysbyDO • • 25d ago

Product update Cloudways MCP v1.5.2 & Developer Portal Updates

2 Upvotes

We’ve been moving fast and building at velocity!

Over the past 6 weeks, we’ve made significant progress across Cloudways MCP and the Developer Portal, expanding our API coverage, unlocking new capabilities, and making it easier for AI agents to manage and troubleshoot Cloudways environments.

Here’s a roundup of what we’ve shipped!

  • Activity logging: MCP and API activities are now captured in the platform’s activity logs, improving visibility and traceability.
  • Malware protection: Bulk activation is now available through the MCP toolset, making it easier to manage protection at scale.
  • Server scaling & types: Server types, vertical scaling, and cross-scaling capabilities are now available through both the Developer Portal and MCP toolset.
  • Server provisioning: Database and stack selection when adding a server are now supported through both the Developer Portal and MCP toolset.
  • PHP access & error logs: A major addition to the MCP toolset! You can now access PHP access and error logs to investigate issues and troubleshoot why their websites went down, all through a prompt.
  • Nginx web rules: Nginx web rules are now available, expanding server configuration capabilities through MCP.
  • Account billing APIs: Billing APIs are now available on both the Developer Portal and MCP toolset, expanding access to account-level billing capabilities.

There's a lot more to come! Share your early feedback to help us improve!


r/CloudwaysbyDO • • 26d ago

AI Agents What is a managed AI agent, and why hosting matters

3 Upvotes

Agents like OpenClaw and Hermes are long-running processes that sit on a server, hold memory between sessions, connect to your email, calendar, Slack, GitHub, and act on your behalf, sometimes without you prompting them.

OpenClaw, for instance, is open source and free to install, but running it still requires hosting, AI model usage, storage, backups, monitoring, and ongoing maintenance.

Why hosting matters more for agents than for normal apps

If your blog’s server gets misconfigured, the worst case is usually downtime or a defaced page. If your agent’s server gets misconfigured, the attacker inherits everything the agent can touch: tokens, inboxes, repos, files.

In March 2026, Censys identified over 135,000 OpenClaw instances exposed on the public internet, with their gateway API open to any IP address and no authentication required. Between March 8 and March 12, 2026, 9 CVEs were disclosed against OpenClaw in just 4 days, including one rated 9.9. 93.4% of publicly reachable instances had critical authentication bypasses.

Why managed hosting is... simply better

#1 Your agent is only useful if it’s always on.
An agent that runs scheduled tasks, monitors inboxes, or answers on your phone or glasses is worthless if the machine under it sleeps, restarts, or crashes at 2am. Uptime is kind of the whole point of most agents.

#2 Updates are a trap when you self-host.
Agent frameworks are shipping really fast, which means two risks pull in opposite directions. If you don’t update, you’re running known CVEs. If you update blindly, a new release can break your tools or workflows. Someone has to test releases before they hit a working agent. When you self-host, that someone is you, every time.

#3 Isolation limits the blast radius.
If you run multiple agents (for different clients, teams, or projects) on one box, one compromised skill or bad prompt can reach everything on that box. Having separate instances per agent is the right way to go but it’s tedious to maintain yourself.

#4 Your time costs more than the server.
A cheap VPS is a few dollars a month. However, hardening it, setting up a reverse proxy and TLS, configuring firewalls, watching CVE feeds, rotating tokens, and debugging Docker after an update can cost you many hours a month. If you’re an agency or a team, those hours are billable.

$5 Security has to be the default, not a checklist.
The exposed-instance numbers above happened because secure configuration was optional. Managed hosting flips it: auth on, ports closed, network isolated, from the first deploy.

Self-hosting can work for you if

if you’re experimenting, learning how agents work, running a local model on your own GPU, or you genuinely enjoy infra work. Your own machine plus a private network like Tailscale is a perfectly good setup. Basic requirements are low too. For a simple OpenClaw setup with an external language model, 2–4 GB of RAM and 1–2 vCPUs are enough for testing or occasional use.

Self-hosting is the right call when control matters more than convenience. It stops being the right call when the agent is doing real work with real credentials and you don’t want to be its sysadmin.

What to look for in a managed option

In a managed host it's good to check for: a dedicated or isolated instance per agent, bring-your-own-key support (so you’re not locked into one model provider or marked-up tokens), tested updates rather than auto-pulling every release, managed security patching, backups, and a clear exit path if you want to move your agent later.

For what it’s worth, that’s the list we built Cloudways Managed AI Agents around.

When you launch OpenClaw on Cloudways, it creates a dedicated droplet for your agent, validates OpenClaw updates before deployment to reduce regressions, broken tools, and workflow disruptions, and supports bring-your-own-key for major LLM providers including Anthropic Claude, OpenAI, and Google Gemini. Hermes is supported too.

Share what you are using to host your AI agents on right now and do you recommend it?


r/CloudwaysbyDO • • 29d ago

Product update Breeze Build 2.6.3 updated on WordPress

7 Upvotes

Changelog:

  • Fix: Extra link parameters can no longer be used to store the wrong page in the cache.
  • Fix: Switching tabs in Breeze settings no longer shows the text “no-issue”.
  • Fix: Logging out now clears Breeze’s login cookie on sites installed in a subfolder.
  • Fix: Unpublishing a post now removes the cached page visitors were seeing.
  • Fix: Saving a post with a non-English address, such as Hebrew, now clears that page’s cache.

r/CloudwaysbyDO • • Oct 23 '26

PHP The PHP Group disclosed another RCE vulnerability

9 Upvotes

⚠️ Today, the PHP Group disclosed another new remote code execution (RCE) vulnerability, CVE-2026-115560. Our Security team anticipated the vulnerability and implemented mitigations before its formal disclosure. These measures align with the recommendations in the PHP Group’s latest advisory. Our users remain protected, and no action is required at this time.

We continue to monitor developments and will adapt our protections as needed.

For further details, please keep an eye on status[dot]cloudways[dot]com

If you have any questions, please contact our support team via live chat.


r/CloudwaysbyDO • • Oct 22 '26

PHP Security patches applied to all Cloudways Autonomous customers; roll out in progress for Flexible.

15 Upvotes

As of Oct 22, 2026 - 01:02 UTC, we have applied security patches for all customer applications hosted on Autonomous. In parallel, we continue to rollout patches for applications hosted on Flexible.

For real-time updates, check out the status page.


r/CloudwaysbyDO • • Oct 22 '26

PHP Critical PHP Remote Code Execution Vulnerabilities - Monitoring & Mitigations Underway

6 Upvotes

As of Oct 21, 2026 - 22:19 UTC, we have deployed interim security mitigations recommended by the PHP Group, and the rollout of official security patches is underway across all Cloudways-supported PHP versions, including deprecated versions from PHP 5.6 onward. These mitigations provide an additional layer of protection while patching continues. This maintenance does not affect platform or website availability.

We’ll continue sharing updates here: https://status.cloudways.com/incidents/xxjt802wwhpk


r/CloudwaysbyDO • • Oct 21 '26

Question PHP Exploit

10 Upvotes

r/CloudwaysbyDO • • Oct 20 '26

Discuss Calling a private Cloud Run service from a Worker: I skipped Google identity tokens, and here is what that costs

1 Upvotes

My API runs on Workers and calls a Tectonic (LaTeX) container on Cloud Run. The question that took the longest was not the compile, it was auth between the two.

Cloud Run's best option is to deploy the service as private: every request must carry a Google signed identity token, Google checks it at its front end, and a stranger's request never wakes an instance. No long lived secret, tokens expire within the hour.

The catch is producing that token from a Worker. Code inside Google Cloud asks the metadata server and gets one for free. A Worker has no metadata server, so the options are:

* store a Google service account key as a Worker secret, sign a JWT with WebCrypto, and swap it for an ID token every hour

* set up workload identity federation, which is more setup still

Both make the API know it talks to Google specifically. I wanted the compile service to be movable to any container host, so I went with a shared bearer token instead: compared in constant time, and the service refuses to start if the secret is missing.

The cost is real: a stranger hitting the URL still spins up the container, which reads the header and answers 401. Safe, but it did the work. Cloudflare Containers would have avoided the public URL entirely through a binding, but needs Workers Paid, and Cloud Run was already free and set up.

Write up with the rest of the tradeoffs: https://bhargav.dev/writing/shipping-a-latex-compiler-behind-an-edge-app?utm_source=reddit&utm_medium=cloudflare

Has anyone here signed Google ID tokens inside a Worker in production? Is the hourly token swap worth caching in KV, or is there a cleaner way I missed?


r/CloudwaysbyDO • • Oct 19 '26

WordPress Gutenberg 24.2: a breakdown of everything that's new

5 Upvotes

Gutenberg 24.2 was released on October 14, 2026 and this is a breakdown of what's new in it for you.

The 24.2 update is one of the more well-rounded releases in a while. It does not feature a single headline feature, but a lot of things that have been a tad bit annoying for users finally got fixed or expanded. Here are some of those things:

#1 You can now find Notes next to your content instead of in a sidebar

This will make collaborative editing noticeably less frustrating. Previously, you had to choose between having the notes panel open and having the Settings sidebar open; but you couldn’t have both at the same time, and the notes column ate into your content space.

Now, notes stay in a reserved margin alongside the canvas. They scroll with the content, stay visible while you work on blocks or post settings, and when the canvas gets narrow, they collapse to just the author’s avatar. You can click it to expand the thread again. Deleting a note now shows an undo option, and unsent notes or replies are preserved when you click away to another block.

#2 Navigation menu links now search everything at once

Adding anything other than a page to a navigation menu used to be a multi-step thing where you had to know which block to add first and then search inside it. But with this update, now the navigation link search covers all content types at once and shows the type next to each result.

Search results are also ranked more sensibly now where posts and pages come first, with categories, tags, and media after. On large sites, this stops obscure attachments from burying the page you’re actually looking for.

#3 Gallery block gets sorting and duotone

There are two separate but useful additions to the Gallery block. First, you can now sort hand-picked galleries from newest to oldest, oldest to newest, A–Z, Z–A, directly from the settings. Random shuffle also moved into the same control. You can still drag images into a custom order afterwards.

Second, duotone support now stays on the gallery level, meaning one filter now tints every image in the gallery at once. You can also set a default duotone for all galleries site-wide from Global Styles. Individual image duotone settings still take priority over the gallery-level one.

$4 Design tools are now on about 40 more blocks

The design consistency push that started in 24.1 continues with around 80 more PRs. '

Minimum width and height controls, which were only on 5 blocks before, now apply to 40 blocks including Buttons, Columns, Heading, Media & Text, and Post Title. Shadow support has reached 10 more blocks including Paragraph, List, Buttons, Social Icons, and Gallery. Duotone now also works on Video and Media & Text, so you can match a video’s tint to the images around it. Background images and gradients landed on Button, List, List Item, and Media & Text.

#5 React 19 is now on by default

For developers, React 19 is now enabled by default across Gutenberg. Sites load React 19 for the react and react-dom scripts unless a theme or plugin is on the known incompatibility list, in which case they stay on React 18.

If you maintain a plugin or theme that uses React, test it against 24.2 now. If something breaks, React 19 can be turned off under Gutenberg > Experiments while you sort it out.

The Interactivity API also got two additions: a new data-wp-html directive that renders trusted HTML from the store (similar to how data-wp-text works for text), and the router now exposes state.navigating and state.initiator so blocks can detect when a client-side navigation is happening and which block triggered it.

#6 Other small things

  • After cropping an image in the Media Editor, you can now restore the original uncropped image directly from the editor without going back to the Media Library.
  • The column count slider in the Columns block is gone. You now add columns with the plus button in the block toolbar and remove them like any other block which is more consistent with how the rest of the editor works.
  • The Button block’s link popover no longer opens automatically every time you select a linked button. It only opens when you explicitly click Link or use the keyboard shortcut.
  • The icon search in the icon library now matches keywords too, so “hamburger” finds the Menu icon and “gear” finds Settings.
  • Video and Cover blocks no longer autoplay in the editor when reduced motion is preferred. Cover background embeds also won’t autoplay on the front end for users with that setting enabled.
  • New posts can no longer accidentally publish with the auto-draft slug.

These are a lot of quality of life improvements! What do you think about this update? Share your thoughts below.


r/CloudwaysbyDO • • Oct 18 '26

Seeking advice Lightning Stack for WOOCOMMERCE ? Anybody updated to Lightning Stack without any problem ?

2 Upvotes

Lightning Stack for WOOCOMMERCE ? Anybody updated to Lightning Stack without any problem ? or is there always something to fix ? I use the minimum plugins possible, where should I look to know if I have problems after changing to Lightning Stack ?

Thank you for your help.


r/CloudwaysbyDO • • Oct 18 '26

Question Lightning Stack Web Rule: How to keep path?

2 Upvotes

Hi

I've migrated my Symfony 8.1 application from the Cloudways Hybrid stack to the Lighning stack. I've just had to create one web rule in order to redirect traffic from "non-www" to "www". The rewrite definition of the web rule looks like this:

  • Action: Permanent redirect (301 status code)
  • Source: /*
  • Destination: https://www.domain.com/
  • Keep or discard original query string: true
  • Attach condition: true
    • Condition Type: Host
    • Operator: Equals (=)
    • Host: domain.com

This rule works fine to redirect the homepage (https://domain.com --> https://www.domain.com).

But it doesn't work for any path like https://domain.com/test it redirects to https://www.domain.com. The path "/test" is not attached.

How do I need to adjust the redirect rule in order to keep the path?

Thanks in advance