Docs / Getting started
Your first EU-compliant app
Alleex Cloud composes vetted modules into a production app — EU-hosted by default, GDPR-wired by construction. Here's what you need to know before you build.
Quick start
Deploy in three steps
Open the gallery
Browse the template registry. Every available template has GDPR + EU AI Act compliance wired in by construction — not as an add-on.
Browse templates →Deploy hosted or describe what you need
One-click deploy to EU infrastructure (Neon Frankfurt, Cloudflare EU Workers), or open the /create flow and describe your app. The composition engine selects the right template and modules — you do not write scaffolding.
Open /create →Eject when you're ready
At any point, eject your app as plain Next.js code and host it yourself. The eject boundary is the @alleex-cloud/canonical-schema contract — what leaves is yours. What stays is the hosted builder.
Concepts
How Alleex Cloud works
Composition, not codegen
Alleex Cloud does not write freeform code from a prompt. It composes verified, tested modules into a working app according to your intent. The output is predictable because the building blocks are vetted.
Module
A module is a discrete capability — auth, compliance, payments, AI chat — with a typed interface (module.json), a tested implementation, and known dependencies. Modules compose; they do not conflict.
Template
A template is a curated set of modules for a vertical (SaaS, booking, content paywall). Templates are in the gallery registry. Adding a template requires a passing test suite — no phantom entries.
Compliance by construction
The composition engine rejects a plan that adds analytics without compliance-eu. GDPR compliance is architectural — a constraint enforced at compose time, not a setting you remember to turn on.
EU residency by default
Your app's data lives in the EU (Neon Frankfurt, Cloudflare EU) with no region toggle. The Alleex Cloud builder dashboard uses US vendors (Vercel, Clerk) under SCCs — separate from your app data, and stated plainly.
Important
What Alleex Cloud is not
Not a freeform code generator
Alleex Cloud does not take a prompt and write arbitrary code. It composes from a vetted registry. The upside: the output is tested, compliant, and predictable. The constraint: capabilities exist in the module catalog — if a module does not exist, we add it to the registry, not to a one-off generated file.
Not a compliance checkbox
GDPR compliance is architectural: EU residency, hash-chained audit log, DSAR portal, and cookie consent are wired in at compose time. This page is information, not legal advice — consult your DPO for your specific obligations.