How Alleex Cloud works
Not freeform codegen.
Composition.
Alleex Cloud builds your app by assembling vetted, compliance-tagged modules — not by generating arbitrary code. Every change is typed, audit-logged, and yours to keep.
Three steps
From idea to EU-hosted app
Describe it
Describe what you want to build
Type a plain-language description of your app in the editor prompt. Alleex Cloud parses your intent and plans a composition — a typed, ordered list of vetted modules that together produce your app.
- →No boilerplate to scaffold
- →Composition plan is shown before any code runs
- →You can edit the plan before confirming
Watch it compose
Vetted modules compose your app
Alleex Cloud does not write freeform code from scratch. It assembles your app from a catalog of audited, compliance-tagged modules — each one versioned, typed, and compliance-registered. Every module added to your project is recorded in the audit log the moment it is applied.
- →Every module is typed and compliance-tagged
- →No unaudited generated code enters your project
- →Each composition step is hash-chained in your audit log
Own it and ship
You own the code, repo, and data
Your project lives in your own GitHub repository in your own EU-hosted infrastructure. Alleex Cloud provisions a Neon Postgres database (Frankfurt), Cloudflare EU Workers, and Better Auth — all in your account. You can export, self-host, or stop using Alleex Cloud at any time and keep everything.
- →GitHub repo in your org from day one
- →Neon Postgres per project — Frankfurt region
- →One-click export of project + data + audit log
The difference
Why composition, not vibe-code
Freeform AI codegen — where a model writes arbitrary code from a prompt — is fast to demo and hard to audit. Alleex Cloud uses a different model: composition. Your app is assembled from a catalog of vetted, versioned modules, each tagged with its compliance footprint. The composition engine enforces invariants (no analytics without consent, no personal data without GDPR module) that freeform generation cannot.
| Dimension | Freeform codegen | Alleex Cloud composition |
|---|---|---|
| Auditability | LLM output is probabilistic — the same prompt can produce different code. Impossible to audit or attest. | Every module is pinned and versioned. The audit log records exactly which module version produced each change. |
| Compliance | Freeform codegen can silently omit GDPR consent or data-retention logic — you only find out during an audit. | compliance-eu is a first-class module. The composition engine refuses to add analytics without it. |
| Predictability | Large diffs are hard to review and easy to ship-by-accident. | Each step is a known, bounded module change. Diffs are reviewable and reversible. |
| Cost | Every generation burns tokens on boilerplate that could be shared. | Modules are pre-built. You pay for composition logic, not repeated boilerplate generation. |
The catalog
Vetted modules, compliance-tagged
Every Alleex Cloud module is reviewed before it enters the catalog: checked for EU data residency, GDPR footprint, dependency supply chain, and licensing. Each module exposes a typed interface consumed by the composition engine — so the engine can reason about what a module touches (user data, payments, analytics) and enforce compliance constraints before your app is built.
compliance-eu
GDPR by default — consent, DSAR portal, cookie banner, data-retention triggers.
auth-better
Better Auth, self-hosted in your EU Postgres — no Clerk dependency in your app.
db-neon
Neon Postgres, Frankfurt region. One isolated project per app.
payments-stripe-eu
Stripe with EU merchant routing. No US card data written to your DB.
Private beta: the full module catalog is available inside the editor. Module count surfaced here once the live registry is wired — never a fabricated number.
Auditability
Every composition step is audited
When Alleex Cloud applies a module to your project, it writes an immutable row to your app's hash-chained audit log: which module, which version, which operator, which timestamp. Each row hashes to the previous row (server-side Postgres trigger). Chain heads are periodically witnessed in Sigstore Rekor — a public transparency log — so retroactive alteration is detectable by any third party.
You can export the full audit log as JSON/NDJSON with the Rekor index at any time. This is included in every tier — it is not an enterprise feature.
Build software you can actually ship in a regulated market.
Free tier. EU-hosted. No credit card required.