You commit one phase at a time, with GO/NO-GO between phases. Your team gets its own Git repository extending ours. The runtime is MIT-licensed, if we disappear, you keep going. Hosting in our Swedish data centre or yours. Built on twenty years of European authority cloud experience, including SÄPO-validated national protected objects.
Most platform engagements ask you to commit to a multi-year, multi-million pilot upfront. We don’t. Each phase is a fixed-price commitment. You decide whether to continue at the end of each. If we miss the mark in Phase 1, you walk away after roughly a third of the total budget, not all of it.
The mid-cap European industrial customer cannot easily commit to a multi-year, multi-million pilot upfront, even when the long-term ROI is strong. Phasing solves this. Phase 1 is a structured evaluation at a budget level a sponsor can approve without board involvement. Phase 2 only happens if Phase 1 proved out. The architecture investment compounds: every use case after Phase 2 reuses the same ontology, agents and audit infrastructure.
Vendor lock-in is a real fear. We’ve made it architecturally impossible. Your team gets its own GitHub repository extending our component repos. AEL retains copyright on the runtime; you receive a permanent MIT license. If we disappear, you keep your codebase, your customizations, your data.
Each customer gets their own GitHub repository extending AEL's open and private component repos. Your customizations, ontology schemas, system prompts, integration configs, custom dashboards, live there. They are your property.
Easy upstream merge by designEvery PR in AEL's repos triggers automated build + mandatory peer review by the CTO's team before merge. No “silent push” that breaks customer installations. Same discipline applied to large-scale cloud services for European authorities.
No surprise updatesYour repo builds Docker / Kubernetes artifacts. You pull updates via Docker Hub or directly, in your own time. We don't push updates without your control. You decide when a new version lands in production, when to test in staging, when to defer.
Customer-pulled, not vendor-pushedAEL retains copyright on the runtime (the ontology service, MCP builders, audit pipeline). You receive a permanent MIT license, usage, modification, distribution, sublicensing all permitted. If we disappear tomorrow, you have legal and technical right to keep going.
Continuity built inWe’re not a startup learning operations. Our CTO has spent 20 years operating large-scale cloud services for European authorities, several of which were SÄPO-validated national protected objects. The peer-review, customer-pulled updates, audit pipeline and secure data centre approach all come from that experience.
The discipline that runs SÄPO-validated cloud services for European authorities is the same discipline applied to AEL Studio’s CI/CD, peer review, customer update model, and secure data centre architecture in Sweden. Different scale, same principles.
The SÄPO validation refers to systems our CTO operated before AEL Studio. AEL Studio itself is not certified by SÄPO. What transfers is the operational discipline, peer review, customer-pulled updates, secure data centre design, audit-by-default, applied here from day one rather than retrofitted later.
Two production-tested options. No middle-cloud, no shared multi-tenant SaaS, no third-party hosting in jurisdictions you can’t audit.
Dedicated environment per customer. Own Kubernetes namespaces or dedicated cluster. Own data layer, own access control, your IdP integrated. All traffic and data within Sweden.
Right for you when: you don’t want to manage infrastructure yourself, you want a Swedish jurisdiction guarantee, you need a clear single point of operational responsibility.
On-premise (your data centre), your cloud (Azure / AWS / GCP, your tenant in your region), or hybrid. AEL Studio has no external service dependencies beyond its container images. Air-gapped operation possible.
Right for you when: you have a mature IT organisation, your security policy requires self-managed infrastructure, you have specific air-gap or sovereign cloud requirements.
Phase 1 is a 4-week, fixed-price evaluation. You walk away after with a documented domain ontology, a simulated demonstration on a parametrised version of your process, and a structured GO/NO-GO decision, no further commitment.