AI on a vetted kit
The AI plans the sitemap first, then builds on 40+ typed blocks — structured and fully editable, instead of hard-to-maintain markup.
Comparison
Why XICflow builds differently — and what you get.
This comparison isn't about products, it's about approaches. XICflow builds every website once, cleanly, and delivers it static, accessible and privacy-friendly.
Many website tools render in the visitor's browser first, build in a single language and treat privacy and accessibility as after-the-fact add-ons. XICflow makes the opposite the core of the product — not an option.
Two ways to build a website
Scroll table sideways
| Aspect | Common approach | XICflow |
|---|---|---|
| Creation | Hand-built kit or free-form AI markup | AI plans and builds on a vetted block catalog |
| Delivery | Runtime engine in the visitor's browser | Static per-domain build, Lighthouse 100 as the goal |
| Accessibility | Add-on to retrofit | WCAG 2.2 AA contrast check of the theme colours on save and before every publish |
| Privacy & consent | Extra module or third-party service | §25 TDDDG/GDPR consent and legal texts built in |
| Languages | Single language, translated later | English version in the same AI build, more languages can be added |
| Design scope | Small, fixed set | Full catalog in the editor, only what's used self-hosted in the build |
| Reach measurement | External service with its own cookie banner | Cookie-free measurement, directly embedded |
The difference
Why that makes the difference
Static, not runtime
Every website is rendered once at build time and delivered statically per domain. The aim: Lighthouse 100 across all four categories.
Contrast checked on save
A WCAG 2.2 AA contrast check measures the theme colours from “Brand & design” every time you save and automatically darkens text colours that are too weak until the contrast is sufficient. Before every publish it measures again and names every remaining violation as a notice, without holding back the publish.
Privacy built in
Consent per §25 TDDDG/GDPR and legal texts in German and English are generated automatically — no third-party service, no extra cost.
Multilingual by design
Every language version is its own version of the same page. If you start in German, the AI translates into English within the same build; you can switch on further languages and maintain them in the editor.
Full catalog, lean build
Fonts, icons, gradients and effects are all available in the editor; only what you use ships to the site — self-hosted, no third-party request.
Core, not option
Accessibility, privacy, speed and multilingual are part of the standard — not an add-on.
Questions & answers
Frequently asked
Everything you want to know before you start.
Do you compare yourselves to specific providers?
No. This comparison is about approaches, not products. It's about the difference between a runtime engine in the browser and a static per-domain build — not about names.
What does "static per domain" actually mean?
XICflow renders your website once at build time into plain HTML and CSS: critical CSS inline, fonts self-hosted, icons inline, assets pre-compressed. New versions go live atomically — visitors never see a half-finished state.
How does XICflow check colour contrast?
In two steps. When you save, a WCAG 2.2 AA contrast check measures the theme colours from “Brand & design” and automatically corrects text colours that are too weak. Before every publish it measures again and names every remaining violation as a notice instead of quietly letting it pass; it does not hold back the publish. Colours you give individual blocks yourself are not checked.
How can the design catalog be large and the site still fast?
Because the full catalog only lives in the editor. Only what you actually use ships to the delivered website — self-hosted and with no runtime request to third parties. So a wide choice and Lighthouse 100 are no contradiction.
Are the language versions really equal?
Yes. All language versions travel in the same configuration and are delivered together, with clean, separate language URLs. Plan, build and chat know the target languages from the start.
How is reach measured?
On request, cookie-free and directly embedded, described accordingly in the privacy policy — without an external service with its own cookie banner and without a third-party request that would loosen the Content Security Policy.
Start for free
See the difference on your own project.
Generate your website and view the difference live in the preview — static, accessible and multilingual. You only publish on your own domain once you subscribe.
PageSpeed 100 Accessible GDPR Multilingual