
I tested Cloudways AI Website Builder by creating a five-page WordPress website for Cedarline Creative, a fictional branding and web design agency in Nairobi.
I evaluated its AI-generated designs, visual and code editors, WordPress integration, and publishing process. I also measured the finished website’s performance using GTmetrix from Germany and the United States.
Read on to see how Cloudways performed, where it impressed me, and what you should consider before using it.

I scored Cloudways AI Website Builder on setup, design quality, editing, publishing, performance, WordPress access and support. The ratings reflect my Cedarline Creative test, including the approximately 21-minute human support queue and conflicting guidance on website portability.
The criteria follow the HostAdvice hosting rating methodology, adapted for a website builder instead of a VPS.

Generous trial and useful AI credits, but hosting costs extra.
Read MoreWebsite creation was straightforward, although server setup required several choices.
Read MoreBoth AI editing requests succeeded, consuming one credit each.
Read MoreVisual and code edits saved successfully without using AI credits.
Read MoreBoth locations earned GTmetrix Grade A, with zero layout shift.
WordPress administration works, but AI-generated page editing and migration remain unclear.
Read MoreHuman support provided detailed answers, but the 21-minute wait and conflicting guidance affected the experience.
Read MoreFast website generation, flexible editing, and excellent performance, with some concerns about WordPress portability and support consistency.
Generous trial and useful AI credits, but hosting costs extra.
Read MoreWebsite creation was straightforward, although server setup required several choices.
Read MoreBoth AI editing requests succeeded, consuming one credit each.
Read MoreVisual and code edits saved successfully without using AI credits.
Read MoreBoth locations earned GTmetrix Grade A, with zero layout shift.
WordPress administration works, but AI-generated page editing and migration remain unclear.
Read MoreHuman support provided detailed answers, but the 21-minute wait and conflicting guidance affected the experience.
Read MoreFast website generation, flexible editing, and excellent performance, with some concerns about WordPress portability and support consistency.
Cloudways AI Website Builder uses a per-website subscription alongside separately billed managed cloud hosting. You can generate WordPress or WooCommerce websites, customize them using AI, and deploy them to an existing Cloudways server or a new hosting server.
Here’s what the plans include:
Cloudways also advertises a limited-time Black Friday discount covering both the AI builder and managed hosting. The offer expires on December 5, 2026. The product page emphasizes free trials and cancellation flexibility but doesn’t specify a standard money-back guarantee.

I approached the builder as a business owner with a website brief rather than an existing WordPress theme. Cloudways gives you a prompt-driven starting point, then moves through application setup, AI generation and editing.
Once the site exists, you can refine it in three ways: AI chat, direct visual controls, or source code. I tested all three on the same website so I could compare their behavior.

The Cloudways account dashboard had a dedicated Cloudways AI section and an AI Website Builder entry. Its landing page presented a large prompt box and several suggested prompts for portfolios, online stores, blogs and nonprofit sites. I entered a description of Cedarline Creative, specifying five pages, intended sections, images, navigation, design colors and content boundaries.

After I submitted the prompt, Cloudways asked me to select a hosting server, enter the website name and choose an AI builder plan. The account’s available server appeared as ‘builder’, and I selected the 10-day free trial with eight credits.
During the earlier configuration walkthrough I also saw the broader infrastructure options: DigitalOcean, Vultr, Linode, AWS and Google Cloud, with separate region, database, application stack and server-size controls. Cloudways offers considerable choice, but new users still need to understand that the website builder and the hosting server are related, separately priced parts of the setup.

The build happened in two distinct stages. The first screen said ‘Building your Website’ and completed the WordPress installation in 2 minutes 28 seconds. Cloudways then added Cedarline Creative to the Applications dashboard, displayed an installation confirmation and opened the AI builder in a new tab. The second stage generated the actual content and design in another 2 minutes 3 seconds.
Total elapsed time was 4 minutes 31 seconds from build submission to a usable website preview. The AI editor showed its work as it progressed, including site structure, src/main.tsx, src/App.tsx, Tailwind components and CSS. Once generation finished, the homepage appeared in the preview pane and the remaining AI credit counter still showed eight.

The first homepage was noticeably more complete than a simple hero section and a few placeholder cards. Cloudways gave Cedarline Creative a cream background, large dark type, navigation for About Us, Services, Portfolio and Contact, a Book a call action, and a professional photo of a designer at work. The copy referenced Nairobi and the agency’s branding and web-design services. It also included two prominent calls to action and several supporting badges.
Scrolling down revealed service cards, a company introduction, a process section, portfolio previews, another project inquiry panel and a complete footer. The Services page had six service cards and a separate engagement-process layout. About Us used three cards for Clear Direction, Careful Craft and Lasting Partnership.
Portfolio showed four sample businesses with images and technology labels, while Contact included name, email, optional company, service selection, project details and a Send message button.

I liked the visual coherence. The service, portfolio and contact pages felt as though they belonged to one agency website, with the same spacing, button treatment and cream-and-navy palette. Cloudways also created different layouts for different page purposes: case-study cards on Portfolio, more detailed service blocks on Services and a practical two-column form on Contact.
The AI was less precise about the details of the brief. I requested a four-step process, but the homepage advertised four steps and displayed five numbered stages. Portfolio included four examples rather than the three requested.
The Services page expanded the offering to six categories, and a secondary call-to-action area displayed an unfinished-looking button. The AI also generated a fictional phone number, email address, office location, studio hours and technology claims for fictional projects. Those details should be replaced or verified before a real business publishes the site.
I also clicked a View case link on the original Portfolio page. Instead of opening a detailed project page, it redirected to Contact. The link was functional, but it did not match the expectation set by its label. This gave me a useful real-world scenario for testing the AI editor’s ability to correct navigation and create a missing page.
For my first AI edit, I asked Cloudways to fix the homepage process heading. The request was deliberately narrow: replace ‘A clear four-step process from first call to launch’ with ‘A clear five-step process from first call to launch’, preserve all five cards and avoid changes elsewhere.
The AI completed the operation in 39 seconds. The updated heading appeared in the preview with the same size, typeface and spacing, while the content underneath remained in place.
Cloudways recorded the operation as ‘Change heading to five-step’, exposed a Code diff view and reduced the credit counter from eight to seven. This was a successful one-credit correction, but the task itself was simple enough to do manually. It demonstrated that AI can handle small mistakes precisely when the instruction defines the scope.

The second request was more demanding. Because ‘View case’ on Harbor Coffee Co. led to Contact, I asked Cloudways to build a separate case-study page, connect the existing link, describe the fictional project, include branding and website-design details, and label it as a demonstration. The AI worked through distinct tasks such as adding project-overview and design sections, updating the link, and generating a new page.
The job completed in 2 minutes 10 seconds and used one additional credit. Clicking View case then opened a dedicated Harbor Coffee Co. route instead of Contact. The new page retained the site’s overall visual system, with an introductory hero, cards for visual identity, packaging typography, and ordering flow, and a contact-oriented closing section. The case study was explicitly identified as fictional.

The second result also showed the limits of AI editorial precision. The headline introduced ‘Coastal Roasters’ as a descriptor for Harbor Coffee Co., and the generated section did not visually emphasize the requested coffee imagery as strongly as its summary implied.
I would review AI-created project stories, brand names and images closely before sharing them publicly. Still, the workflow solved the original missing-page problem without hand-coding a new route.
The two operations took a combined 2 minutes 49 seconds and cost two of the trial’s eight credits. Both had distinct revision entries and a restore option. For occasional multi-element changes, I found the AI editor genuinely useful; for small wording changes, I would generally use the visual editor to preserve credits.
I switched from Preview to the pointer-style editing mode and clicked the homepage hero heading. Cloudways immediately outlined the selected h1, placed an insertion cursor inside the text, and opened a property panel with the element’s content. It showed link controls, Default and Hover states, font family, weight, size, line height, letter spacing, alignment and text-decoration options.
The existing hero used a semi-bold heading at 60px with 75px line height and -2.1px letter spacing. I changed the copy to ‘Build brands that people remember.’ and reduced the font size to 56px. The preview updated immediately, and Save and Discard buttons appeared in the top-right corner. After saving, I returned to Preview and saw the new two-line heading beside the original image and calls to action.

This was the most efficient option for small layout and copy adjustments. I did not have to write a prompt or navigate a CSS file, and the page kept its intended spacing. The remaining AI credit balance stayed at six. Users who update headings, labels, buttons or simple styling regularly can reserve AI credits for more complex changes.
The third editing mode opened a real source browser rather than a limited custom CSS box. I could see a src directory with components, hooks, integrations, libraries, pages, reusable sections, global CSS and files such as main.tsx and Home.tsx. The editor supported several open tabs, file search and syntax highlighting. The generated site used React and TypeScript/TSX with libraries including Framer Motion and Lucide React.
To test that the code was editable rather than merely viewable, I opened Designstrategy.tsx for the Harbor Coffee Co. case-study page and changed the card title from ‘Earth Tones & Coastal Navy’ to ‘Warm Earth Tones & Coastal Navy’. I saved the edit, returned to Preview, and saw the updated title appear in the Visual Identity card. Cloudways added another modification entry and kept the AI credit balance at six.

I appreciated that the source editor made these changes accessible without leaving the builder. It also makes Cloudways more relevant to developers who want fine control over page components.
There is a learning curve. Seeing React imports, CSS modules and component files is very different from editing blocks in standard WordPress. A nontechnical user is likely to stay in Preview or visual mode.
I switched the editor’s device control to a narrow mobile viewport and inspected Home, About Us, Services, Portfolio and Contact. The site reorganized the desktop content sensibly. On Home, the hero heading wrapped across several lines, calls to action stacked vertically, supporting highlights moved below, and the designer image appeared after the main copy. The content remained within the viewport.
The navigation collapsed to a hamburger button. I opened it and saw links to About Us, Services, Portfolio and Contact, plus a Book a call action at the bottom. The menu closed normally, and I could reach other pages from it. On Services and Portfolio, card grids became vertical stacks. The About Us content retained clear headings and button spacing. Contact showed its fields in a single column, including the service selector and project-details textarea.


I did not see cropped text or horizontal overflow in these previews. The mobile version used the same visual language as desktop, which is a good starting point for a business site. I would still inspect an actual phone after major design changes, especially if replacing images or adding plugins, but the default generated layouts handled our five pages well.
Publishing used a clear two-step interface. I clicked Publish in the AI editor, reviewed a panel showing the Cloudways application URL, and selected Publish changes. The editor displayed a confirmation reading ‘Changes published’ after approximately 30 seconds. I then opened the live site and used that public URL for the GTmetrix measurements.

This separation between Preview and Publish was useful. I could make and inspect changes first, then deploy them deliberately.
The distinction also showed up in WordPress. The original five pages were already marked Published, while the additional Harbor Coffee Co. page appeared as a Draft before the final publish action. Cloudways’ editor therefore provides a publishing workflow layered on top of ordinary WordPress page statuses.

After generating the website, I opened its WordPress administrator dashboard from Cloudways. It was a real WordPress installation, with the familiar Pages, Posts, Media, Plugins, Appearance, Users, Settings and Comments sections. The dashboard showed WordPress 7.1.4 and an active Cloudways AI Website Builder Theme. I could also see Breeze caching controls, Object Cache Pro and a dedicated Form Data section.
Under Pages, WordPress listed six entries: Home, About Us, Services, Portfolio and Contact as Published, plus Harbor Coffee Co. as Draft before the later publish action. Home was explicitly tagged Front Page. All six entries carried a WVC Editor label. The main pages had been published together at 6:24 AM on November 16, 2026, according to the dashboard, and the extra case-study page reflected a more recent modification time.

Figure 14. WordPress recognizes the AI-generated pages individually, with five published pages and one draft case study at this stage.
Clicking Edit on Home revealed the most important integration detail. Rather than presenting the generated design as ordinary Gutenberg blocks, WordPress displayed ‘This page is built with Cloudways. Page content is managed in the editor’ and an Edit With Cloudways AI Builder button.
The page title, permalink, publication state and WordPress-level settings remained visible, but substantive layout editing was routed back to the Cloudways builder.

Figure 15. The WordPress page editor directs users back to Cloudways AI Builder for the generated page content.
In Installed Plugins, I found four normal plugins: Breeze and Object Cache Pro were active; Akismet Anti-spam and Hello Dolly were inactive. The plugin page also showed two must-use plugins and two drop-ins, confirming a broader managed WordPress stack. Breeze provides cache-management controls and Object Cache Pro describes itself as a Redis object-cache backend. No dedicated SEO plugin was shown in the installed-plugin list.
Appearance listed four installed themes. Cloudways AI Website Builder Theme was active, with Twenty Twenty-Five, Twenty Twenty-Four and Twenty Twenty-Three available as alternatives. The Media Library contained the design images and brand assets used on the site, including the hero photography, portfolio images and favicon assets. WordPress Users showed one administrator account, with the regular Add User and role-management controls.

Figure 16. The active Cloudways AI Website Builder theme appears alongside standard WordPress themes.
WordPress Permalink Settings was set to Post name, giving standard readable slugs for ordinary WordPress content. Form Data listed one registered form called Get in Touch, five fields and zero submissions at the time of inspection.
The form-management screen offered email notification settings, export tools and hooks, while email notifications and hooks were not yet configured. I left the site’s fictional contact form unsubmitted as planned.
The WordPress controls were genuine, but they did not resolve the question of portability. I contacted Cloudways support with a specific question: if the AI builder subscription ends while hosting remains active, can the pages still be edited through WordPress, and can the complete site move to another WordPress host?
The AI assistant said the WordPress application could remain hosted after AI subscription cancellation, but AI editing would stop. It treated moving, cloning and directly transferring an AI Builder application as unsupported workflows, suggesting a full files-and-database backup for manual migration.
When I escalated the question, human support agent Manahil gave a broader answer: the website would continue functioning, ordinary WordPress administration and editing would remain available, and a complete WordPress migration to another host would be possible. Those are two different descriptions of portability from the same provider.
The WordPress dashboard supports Manahil’s point about access to posts, plugins, settings, images and users. The Home page editor, however, showed a Cloudways notice directing me to Edit With Cloudways AI Builder rather than regular Gutenberg blocks. Manahil suggested using the WordPress editor or a free page builder after cancellation, but the chat did not demonstrate how the generated React/TypeScript design would become editable there or remain intact during migration. I would seek written steps for that exact workflow before canceling.

Cloudways provided a Support section with live chat, ticket creation, a community center and knowledge-base categories. The account displayed Standard support scope, with an upgrade option for premium features such as priority response times and application optimization help. I chose Live Chat and then Technical Help.
The conversation began with an AI agent that offered categories such as DNS, SSL, SSH/SFTP, backups, website errors, caching, databases and security. I selected Website / Application Errors because the question concerned the generated application’s WordPress integration, cancellation and migration. The chat accepted the full technical question without forcing me into a narrow troubleshooting script.

The AI assistant responded quickly and organized the issue into cancellation, editing and migration. It said the hosting application would stay in place, AI editing might end, and direct moving or cloning of AI Builder applications was not supported. It proposed downloading a complete files-and-database backup if I wanted to attempt a manual move. The answer was easy to follow, and it offered a route to a human when I asked for clarification.
I asked to speak to a human technical specialist. The bot accepted the request immediately and displayed ‘Waiting for a teammate’, but the human handoff itself was slow. In the same screenshot, the AI handoff message was labeled 31 minutes old and Manahil’s joining message 10 minutes old. That puts the queue at approximately 21 minutes.
Manahil opened politely, introduced himself as Cloudways Technical Support, and greeted me before I repeated the question about editing and migration after cancellation.

Figure 18. Manahil joined the chat after an approximately 21-minute human-support queue, then greeted me before I repeated the question.
Manahil told me that ending the AI Website Builder subscription would remove AI editing and prompts but would not interrupt the website while hosting stayed active. He said WordPress pages, posts, plugins, settings, images, text and menus would remain editable, and suggested the standard editor or free builders such as Elementor Free or Spectra.
He also said the complete WordPress website, including its design and functionality, could be moved to another WordPress host. I appreciated the specificity, but these were support assurances rather than actions demonstrated in the editor.

Manahil’s answer was clear and courteous, without sending me through more menus or requiring a ticket. He addressed both parts of my question in one message and explained that I would keep paying for hosting while losing access to the AI builder and its prompts.
The weakness was consistency rather than tone. His assurance that the complete site could migrate and remain manually editable did not match the AI assistant’s restrictions or the generated page editor I had inspected. I appreciated the direct answer, but I would ask Cloudways to clarify how those claims apply to the AI-built design.
The AI assistant routed me to the right technical topic and answered promptly, but the approximately 21-minute queue made the human escalation slow. Manahil was courteous and addressed both questions directly.
His assurance about ordinary WordPress editing and migration was more encouraging than the bot’s guidance, yet the two answers conflicted with each other and the WordPress page editor I inspected.
I scored support 8.5/10: helpful communication, but I would ask for written steps before depending on the portability claim.

Cloudways is easiest to understand as an AI site builder operating with managed WordPress hosting. Wix and Hostinger also offer AI-assisted site creation, but their product boundaries and underlying editing platforms differ.
I would compare them around the parts that affect ongoing ownership: where the website runs, how pages are edited after generation, how much source or WordPress access is available, and what happens when a subscription ends.
| Consideration | Cloudways AI Builder | Wix / Hostinger AI Builders |
|---|---|---|
| Underlying platform | Managed WordPress site with AI-managed page content | Primarily proprietary website-builder editing environments |
| Editing choices | AI chat, direct visual editor and React/TSX source editor | Visual and AI editing tools vary by product and plan |
| Hosting relationship | Requires a separate Cloudways hosting server | Hosting generally bundled with builder subscriptions |
| Portability question | AI cited limits; human said migration is possible | Export and migration options vary; verify before purchase |
Table 2. Practical platform comparison. Features and policies may change; confirm current plans before choosing a platform.
For a business that specifically wants a WordPress administrator dashboard and access to plugins, media and user management, Cloudways has a clear advantage over a fully proprietary website system.
However, our test also showed that the builder-generated page body is not ordinary Gutenberg content. If unrestricted WordPress theme editing and straightforward cross-host migration are priorities, I would verify those workflows before choosing this product.
A small service business is the clearest fit for the experience I tested. Cedarline Creative needed a homepage that communicated its services, a believable company introduction, project examples and a way for visitors to make contact. Cloudways produced those pieces from one prompt, and the generated pages shared the same navigation, typography and button styles. A business owner could update copy and basic styling in the visual editor without returning to AI chat for every adjustment. I would still budget time to replace fictional business details, check outbound links and configure form notifications before launching.
An agency could use the builder to turn a creative brief into a presentable first version for client feedback. During my test, the five initial pages arrived together, and the AI-generated Harbor Coffee Co. case study showed how the editor could extend an existing project without starting over. The revision history, code diff and restore controls make it easier to review what has changed. If an agency plans to hand the site to a client, I would settle the questions around continued editor access, subscription ownership and migration before the handover.
The TypeScript and CSS editor was more capable than I expected from an AI website tool. I could inspect the src tree, navigate components, and save a targeted source change that appeared in Preview. Developers familiar with React may appreciate this direct route to customization. The underlying WordPress relationship still deserves attention: the familiar WordPress Pages screen sends layout editing back to Cloudways, so a team expecting standard Gutenberg blocks for every design element will need to adjust its workflow.
Cloudways presents the product as capable of generating WordPress and WooCommerce websites. I focused this review on a five-page agency site instead of a checkout workflow. The server sizing choices, WordPress dashboard and source editor suggest a flexible starting environment, but store owners should validate product management, checkout, payments, plugin compatibility and the effect of AI credits on ongoing catalog work before using the builder for a live store.
The biggest launch risks in this test were editorial rather than technical. The AI gave us a polished layout but also invented a phone number, email address, business hours, client portfolio descriptions and technology claims. It created more examples and service categories than requested, and the original View case links led to Contact rather than proper case studies. I would walk through every page in both desktop and mobile Preview, confirm business details, inspect every button destination and test form routing. Only then would I publish and run the final performance check.
Yes, with a clear qualification about long-term editing and portability. Cloudways generated a professional-looking five-page WordPress site in 4 minutes 31 seconds, let me refine it through AI, visual controls and TypeScript, and published the final changes in about 30 seconds. The live site earned GTmetrix Grade A from Germany and the United States.
I recommend it most for small businesses and agencies that want a fast start, a managed WordPress environment and flexible editing tools. Before launch, I would correct the AI-generated business details and check every link. The human support agent was reassuring about continued WordPress editing and migration, but the AI assistant gave a different answer. I would ask Cloudways for clear instructions covering this specific AI-generated design before planning a cancellation or host move.
| Description | Expert Review |
|---|---|
| Управляван WordPress хостинг с бързина, сигурност �... | Read Wordpress Hosting Review |
| Гъвкав, високопроизводителен облачен хостинг ... | Read Cloud Hosting Review |
| Сигурен и ефективен хостинг за електронна пощ�... | Read Email Hosting Review |
| Оптимизиран Magento хостинг с бързи скорости и по�... | Read Magento Hosting Review |
| Read WooCommerce hosting Review | |
| Read VPS Hosting Review | |
| Управлявайте множество WordPress сайтов със сигур�... | Read Site Manager Review |
Yes. My test produced a WordPress installation with a dashboard, pages, posts, media, themes, plugins, users, permalinks and form-data controls. The five original website pages appeared as Published in WordPress. The main layout and page content, however, are edited through Cloudways AI Website Builder rather than ordinary Gutenberg blocks.
Yes. I used AI chat to change a homepage heading and create a new case-study page. I also changed headline content and typography in the visual editor and edited a TypeScript component directly in the code editor. All changes worked in Preview. Manual visual and source-code edits used no AI credits during my tests.
The 10-day free trial in my account included eight AI credits for one website. Pro advertised 20 monthly credits per website and paid top-ups. Both of my AI editing prompts used one credit each; the initial website generation and the manual edits did not lower the visible balance. Confirm current allowances and renewal terms in the checkout screen.
The generated pages used readable headings, relevant content and a mobile-responsive layout. WordPress was configured with the Post name permalink structure. I did not find a dedicated SEO plugin among the four standard installed plugins. Businesses should still review metadata, internal linking, content accuracy, image alternatives and search-console configuration before expecting search traffic.
Both support agents said the hosted website can remain online when the AI subscription ends and hosting continues. Human agent Manahil said regular WordPress editing and migration to another host would still be possible, but the AI assistant described unsupported direct transfer workflows. My WordPress page editor directed design changes back to Cloudways. Confirm how the original AI-generated layout would be edited or transferred before canceling.

Отговорете на няколко прости въпроса и намерете перфектното решение за вас!
Стартирай хостинг търсенеHostAdvice.com предлага професионални рецензии за доставчици на уеб хостинг, напълно самостоятелно и независимо от който и да е друг ресурс в индустрията. Нашите рецензии са безпристрастни, правдиви и ползват една и съща система на оценяване за всички рецензирани.
Въпреки че получаваме финансова компенсация от някои компании, които рецензираме, това не оказва влияние върху насоките или заключенията на нашите рецензии, нито повлиява по някакъв начин позиционирането на определени хостинг компании в нашите класации.
Тази компенсация покрива разходите за хонорари на авторите на рецензии, закупуване на акаунти и тестване.






