IONOS is a German hosting company, and its AI App & Site Builder is a newer chat-based tool, powered by a system called Momentum AI, that turns a plain description into a published website or web app. It sits inside IONOS’s broader “Web Projects” area alongside its older website and shop tools.
I built two separate projects from scratch, tested the support channels, and read through the actual terms of service to see whether it lives up to its “just describe it” pitch, or whether that promise breaks down once you ask for something more than a static page.
Before I get into what I found, here’s what I actually did, in order, so you can see exactly how I reached each conclusion below.
Readers coming to this review want one thing above all: does this tool build something you can actually use, or is it another AI website generator that produces a nice-looking page and nothing more? I built my testing plan around answering that directly.
| Parameter | Score | Why This Score |
|---|---|---|
| Prices | 9.5/10 | Plans are priced competitively for what’s bundled, but the pricing page’s blanket “30-day money-back guarantee” claim glosses over real exclusions I found in the actual terms. |
| Features | 9.6/10 | A live PocketBase backend, full code access, exportable projects, and point-and-click editing go well beyond what most AI site builders offer. |
| Performance | 9.0/10 | Both builds generated in under six minutes with working functionality, though I have not yet run a load test against the published live URL. |
| Ease of Use | 9.3/10 | Building and refining a site is fast and intuitive, but the recent rename of the dashboard category to “Web Projects” is a real point of confusion for existing customers. |
| Support | 8.0/10 | Phone escalation was offered instantly, but the AI assistant could not answer a fair product question and pushed an unrelated upsell, and live chat was down during my test. |
| Overall | 9.1/10 | A capable, functional AI builder held back by a support layer that is not yet matched to the product’s technical ambitions. |
IONOS AI App & Site Builder comes in three tiers: Starter, Plus, and Unlimited. All three include no-code building, hosting, SSL, and a claimed 1-year free domain, billed at a discounted rate for the first term before renewing at a higher monthly rate.
| 計劃名稱 | 空間 | CPU | RAM | 操作系統 | 價錢 | |
|---|---|---|---|---|---|---|
| AI App & Site Builder: Starter | 無限 | - | HK$71 | 詳細信息 | ||
| AI App & Site Builder: Plus | 無限 | - | HK$118 | 詳細信息 | ||
| AI App & Site Builder: Unlimited | 無限 | - | HK$149 | 詳細信息 |
| Plan | Best For | AI Credits/Month | Projects | Email Addresses |
|---|---|---|---|---|
| Starter | A single first project | 150 | 1 | 1 |
| Plus | Growing projects, freelance clients | 300 | 10 | 5 |
| Unlimited | Serious, multi-client work | Unlimited | 25 | 10 |
What I think: the credit allowance matters more than the project count for most buyers. My four-page bakery site cost about 9 credits to generate, and a functional booking tool with a live database cost closer to 6.
Starter’s 150 credits will cover a handful of builds and revisions in a month, not much more, so anyone planning to iterate on design the way I did should look at Plus first.
The 30-day money-back guarantee, read from the actual terms, not the marketing bullet:
A compliance term worth knowing before you build: IONOS’s AI Services Terms of Use require that any AI-generated content used publicly, meaning your published site, must be clearly disclosed to visitors as AI-generated or AI-assisted. That is not mentioned anywhere on the marketing or pricing pages I reviewed, and it is a real legal obligation for anyone publishing a site built here.
Payment methods accepted: IONOS supports credit cards (Visa, Mastercard, American Express), PayPal, and SEPA Direct Debit across its services, with Klarna, Apple Pay, Google Pay, and Amazon Pay available depending on your region and the specific service.
Overall Verdict on Plans and Pricing: Pricing is competitive and the checkout flow is more transparent about contract terms than most, but it’s also longer and more upsell-heavy than the simple three-card pricing page suggests, and a shopper needs to actively claim their free domain during checkout rather than assume it’s automatic.
I’m walking through this in the order a new customer actually experiences it: signing up and paying, finding the builder inside the account, describing a project, watching it generate, refining the result, and publishing it live.
I’ve pulled out the friction points and the details that impressed me at each stage, since that’s what actually tells you whether this product is easy to use, not just whether it eventually works.
I started where every new customer starts, on the public AI App & Site Builder marketing page, not inside an existing account.
Here’s the exact path I took:
What I think: the actual purchase experience is more layered than the pricing page lets on. None of the upsells are dishonest exactly, the Unlimited upgrade prompt and the MyWebsite Now Plus offer are both clearly labeled as optional, but a first-time buyer who just wants the $9 Starter plan has to click through two separate pitches for other products before reaching their cart. That’s friction the marketing page doesn’t prepare you for.
Once the purchase was complete, I moved into the account itself. The AI App & Site Builder lives inside a My IONOS dashboard category IONOS recently renamed from “Websites & Shops” to “Web Projects.”
The rename comes with its own in-product tooltip explaining the change to existing customers, a small but telling sign that IONOS knows this could confuse people who used the old name.
I clicked through and landed on a clean chat-style entry screen: “Your idea deserves to be [x],” a prompt box, a file-upload option, and four quick-start categories (Personal site, Small business, App landing page, Event page).
What I think: renaming a category customers already know is always a bit of a gamble. IONOS mitigated it well with the tooltip, but I’d expect a small wave of “where did my Websites & Shops go” support tickets regardless.
It’s also a slightly disorienting handoff; you buy the product on ionos.com’s main shop, then land in a completely different-looking dark-themed builder interface to actually use it, with no visual thread connecting the two.
I skipped the quick-start chips both times and typed fully custom prompts instead, once for a bakery marketing site and once for a yoga studio booking tool.
Neither prompt triggered any clarifying questions before generation started; it went straight to building both times.
The bakery project auto-named itself “Wheat & Sage,” and the yoga project auto-named itself “Yoga Studio Booking Tool” in the project header, without me setting a name myself.
Next, I watched both builds work through a series of labeled stages: “Looked something up,” “Organized files,” and finally “Now let me build the full multi-page site,” each with its own running timer.
The bakery site’s final build stage alone ran 3 minutes 42 seconds, with earlier setup stages pushing the total logged step time closer to 5 minutes.
The yoga booking tool moved faster start to finish, 2 minutes 13 seconds logged.
Then I tested a refinement to see how the tool handles changes after the initial build. I asked it to change the bakery’s color scheme from terracotta to sage green.
It moved into a “Responding” phase and disclosed its full plan before executing, a complete list of every hex code it intended to swap, then applied the change consistently across every page, the navigation, the footer, and even the browser tab icon, in 59 seconds.
Two editing tools sit directly in the live preview, and I tried both:
A Code tab also gave me the full file tree and an editable code view, including a floating window that overlays the code editor on top of the live preview so you can check your change against the design without switching tabs.
What I think: the transparency during refinement, showing me the exact color swaps before making them, is the kind of detail that builds trust in a tool that’s otherwise a black box. I’d like to see that same disclosure happen during initial generation, not just refinements.
Once I was happy with the design, I moved to publish. That surfaced a live preview URL on an IONOS subdomain before going live.
I then tried to connect a custom domain, which opened a modal that searched my account and returned “No domains found,” offering only “Buy a new domain” as the next step.
Having since walked the checkout flow, I now know why: the free domain isn’t provisioned automatically, it has to be actively claimed on its own screen during purchase, and if that step gets skipped with “Proceed without domain,” there’s genuinely nothing waiting to connect later.
That’s a real usability gap either way. Whether it was skipped on this test account or the domain simply isn’t syncing into the builder, a first-time buyer following the “1 free domain for 1 year” promise on the pricing page has no clear signal, at the point they’re ready to publish, about which of those happened to them.
Building and refining a project here is fast, visual, and low-friction once you’re inside the tool, and the point-and-click editing is a real time-saver.
The friction sits earlier and later than the builder itself, at checkout, where two upsells and a domain-claim step stand between “pick a plan” and “start building,” and again at publish time, where it’s not obvious whether your free domain actually followed you into the project.
This is the section that decides whether “AI App & Site Builder” is an honest name or a marketing stretch. I ran two separate builds because a marketing site and a functional booking tool test very different capabilities.
I described a bakery website with a homepage, menu page, order inquiry form, and location page, in warm rustic tones.
What came back was a four-page site with real bakery stock photography, an order enquiry form wired to save submissions, and hours that auto-highlight today’s day on the Visit Us page.
It also invented specific opening hours I never gave it, a small but real reminder that this tool fills gaps with plausible-sounding specifics rather than leaving placeholders or asking first.
Next, I described a yoga studio booking tool: a weekly class schedule, class selection, name and email capture, and a confirmation message.
The result was a real weekly schedule across all seven days with distinct class names, times, and levels.
Selecting a class auto-scrolled to a booking form that dynamically confirmed the chosen class and time, and submitting it produced a genuine confirmation screen addressed to the email I entered.
I decided to verify this wasn’t just a convincing front end, so I checked the builder’s own Database tab. The submission was sitting there as a real record in a bookings collection, with a generated ID, timestamp, and every field I’d entered. This is not a static form, it writes to an actual backend.
One limitation worth flagging clearly: switching from the Test database to the Live database view showed “Live database not set up,” meaning nothing persists to a production database until the project is actually published.
What works in the editor is running against a sandbox, not your live site, until you hit publish.
| Build | What It Was | Generation Time | Credit Cost |
|---|---|---|---|
| Build 1 | 4-page bakery marketing site | ~5 minutes logged | ~9 credits |
| Build 1 refinement | Site-wide color palette change | 59 seconds | Less than 1 credit |
| Build 2 | Yoga studio booking tool with live database | 2 min 13 sec | ~6 credits |
Functional complexity did not translate into higher cost here, worth knowing if you’re budgeting credits against Starter’s 150-per-month allowance.
What I think: the yoga booking build is the strongest evidence I found that this tool can produce a genuinely working small application, not just a good-looking page. A lot of AI website builders stop at static output. This one wrote real data to a real database on a form I built entirely by typing three sentences.
Both builds produced working, publishable output, and the booking tool proved the “app” half of the product name is not just marketing language. The gap between Test and Live databases is a real distinction to understand before you rely on this for anything transactional.
I tested support with a real two-part technical question: whether custom code, like an existing booking widget script, can be added on any plan, and what happens to projects over your new limit if you downgrade from Plus to Starter.
I asked the question directly in the in-product AI Assistant chat. It did not attempt an answer to either half.
It restated the plan tiers I already knew from the pricing page, said it could not confirm the custom code or downgrade behavior, and directed me to contact support, then closed with a promoted link to “MyWebsite Now Plus,” a different IONOS product entirely from the AI App & Site Builder I was testing.
I then asked, “Can I please talk to a human?” That triggered one clarifying question, whether I had anything else the agent should know, then handed off with a phone number, a customer ID, and a temporary phone PIN, plus an “Arrange a callback” option.
Wanting to see if chat was available instead of a phone call, I asked twice more, just for a live chat option, and got the identical phone and callback handoff both times.
No chat option was ever surfaced in that flow, even after asking directly.
I checked IONOS’s live chat page directly to rule out a flow-specific issue. It showed “Temporarily unavailable, sorry, all our advisers are currently helping other customers, try again later,” despite IONOS’s own marketing describing support as available 24 hours a day, 365 days a year.
I cannot confirm from a single test whether this was a temporary volume spike or a more consistent gap, but it is what I found at the time of testing.
Since the AI assistant and live chat both came up short, I checked whether the public Help Center could answer the same question on its own.
Searching “AI App Builder” returned a small, relevant set of results directly in the autocomplete: “What is the AI App & Site Builder?” and “Deleting a web project.”
Opening the full results page turned up more depth, including “Your first project: From idea to finished website” and “Connecting a domain and SSL certificate to your project,” alongside a couple of results that were only loosely related, like an AI Receptionist configuration article and a MyWebsite Now migration guide surfacing in the same search.
The core article, “What is the AI App & Site Builder?”, actually answered questions my AI assistant chat could not:
None of that page mentioned custom code or downgrade behavior either, so my original two-part question remains unanswered by any channel I tried.
But it did resolve two other real concerns, ownership and exportability, that most readers will want settled before committing.
What I think: the phone and callback escalation path worked immediately and gave me real credentials to reference, which is a good sign for the eventual human interaction.
But an AI assistant that cannot answer a fair question about its own product’s plan mechanics, and instead surfaces an unrelated upsell, undercuts confidence right at the moment someone needs a real answer. The Help Center is genuinely useful for the questions it does cover, but it has the same blind spot on custom code and downgrades as the AI assistant.
Human escalation is fast to reach and the public Help Center answers more than the AI assistant does, but the AI layer in front of both needs to answer basic product questions honestly instead of redirecting to a different product’s checkout link.
Yes, I’d recommend IONOS AI App & Site Builder, with a clear eye on where it still has rough edges. The core promise holds up under real testing: I described a functional booking tool in three sentences and got back a working form that wrote real records to a real database, not a static mockup dressed up to look functional.
The color refinement transparency, the point-and-click editing, and the full code and export access all point to a tool built by people who understand what serious users will eventually want to do with it.
What stood out most was the gap between the product’s technical maturity and its support layer’s readiness to talk about that maturity. A tool sophisticated enough to expose PocketBase collections and a live code editor deserves a support system that can answer a real developer’s question about custom code, instead of an AI assistant that punts to a different product’s sales page.
This is best for freelancers and small business owners who want a working site or simple app fast, and are comfortable digging into the Code or Database tabs themselves, or checking the Help Center, when the AI assistant can’t answer. It is not yet the right fit for agencies planning to batch-produce many client sites, both because of the Human Use restrictions in the AI Services Terms, and because the support experience I found is not yet built for people who need fast, technical answers on a deadline.
Yes. In my testing it generated a booking tool with a live database that saved real submissions, not just a static page. It runs on a real PocketBase backend with a code editor you can inspect directly.
The pricing page lists a free domain for 1 year on every plan, but in my test the domain connection screen found no domain available on the account and offered only to buy a new one. Confirm this directly with IONOS before assuming it’s automatic.
Neither IONOS’s AI assistant nor its public Help Center could confirm what happens to projects over your new plan’s limit after a downgrade, for example from Plus’s 10 projects to Starter’s 1. This needs a direct answer from a human support agent before you downgrade with multiple active projects.
The builder itself gives you a full code editor with file-level access on the plan I tested, which strongly suggests custom code is possible. Neither IONOS support nor its Help Center could confirm whether this applies identically across every plan tier when I asked directly.
Yes, a 30-day money-back guarantee applies, but only to certain setup fees and your first billing cycle, filed through customer support. It excludes professional services, already-spent third-party budgets, and any package you’ve already switched away from.
