Customer-owned architecture for the German Mittelstand. Five concrete packages.
One platform idea, three operational layers, five engagement models. Instead of a generic "AI Process Automation Platform", you get technically clear service depths that you can audit, combine and walk away from when you need to — without vendor lock-in, without the migration trap.
We use what we build.
The page you are reading right now runs on the platform layer (AI-Ready CMS as a Service). The build pipeline beneath it is hardened with the DevSecOps discipline. The content operations are automated through the business-outcome layer (process automation). What we recommend to you is exactly the setup you are visiting this page on.
One idea. Three layers. Five packages.
Customer-owned architecture is the idea. It breaks down into three operational layers — platform (what runs), discipline (how it is operated safely), outcome (why it exists in the first place). Five packages make those three layers concrete.
AI-Ready CMS as a Service
TYPO3 with MCP server, RAG over your content, Schema.org and content-provenance — as a full service or self-hosted. Four tiers, from Starter to Custom.
AI-Ready Commerce as a Service
Sylius with MCP server, RAG over product data, Schema.org markup and content-provenance. Sister package to AI-Ready CMS — same architecture, same operations.
AI Agent as a Service
Office Agent Suite and TYPO3 Business Agent with a RAG pipeline. Multi-channel, GDPR-compliant, running on your infrastructure — no data leaks to US hyperscalers.
Process Automation
Routine work out of heads and spreadsheets. Analysis, optimisation, automation — without replacing your existing IT. On average, 23 hours a week.
DevSecOps as a Service
Security-by-design in every sprint, automated CI/CD pipelines, 24/7 monitoring. The layer the other four packages run on.
Plus four cross-cutting areas
Beyond the five service packages, moselwal.com has four cross-cutting areas where topics, operations and products live. If you're not looking for a specific service but for a cross-cutting solution, a conference engagement or a pre-built package — here's where you'll find it.
Operations
Hosting, training, support and three specialised packages. What decides whether a platform survives in production.
Topics
Cross-cutting solutions like external IT department, GDPR-compliant CMS, and a ROI calculator for digitalisation initiatives.
Products
Pre-built packages we've proven in multiple mid-market setups — Office Agent Suite and business-agent-pro.
Sechs Konzepte, die unsere Architektur tragen.
Hinter den fünf Service-Paketen stehen Konzept-Felder, die mehrere Pakete miteinander verbinden — und in denen sich Architektur-Entscheidungen aufhängen. Jedes ist eine eigene Landing Page mit Definition, Kernfähigkeiten und FAQ. Lesen Sie sich quer ein, je nachdem wo Sie heute stehen.
AI-Ready CMS
Wann ein CMS auch KI-Agenten bedient — und welche vier Bausteine das voraussetzt: strukturierte Inhalte, APIs, semantische Metadaten, Governance.
TYPO3 Kubernetes
TYPO3, das nicht am einzelnen Server klebt: Cluster-Betrieb, horizontale Skalierung, Persistent Storage, mTLS-Mesh und Sicherheits-Defaults aus dem Repository.
AI-Ready Commerce
Shops, die in generativer Suche zitiert werden — und KI-Agenten als Such- und Bestell-Partner akzeptieren. Vom JSON-LD-Layer bis zur Agent-API.
Open Source & Digital Sovereignty
Kontrolle behalten, auch wenn der Anbieter wechselt. Open Source als Souveränitäts-Fundament — plus Standort-Kontrolle, Multi-Cloud und Exit-Strategie.
Structured Content Architecture
Inhalt als Modell, nicht als Layout — die Grundlage für Multi-Channel, KI-Retrieval und Provenance. Mit Content-Modellen, JSON-LD und Relationen.
AI-Ready Platform Engineering
Eine Plattform, die KI-Agenten als gleichrangige Konsumenten behandelt — mit Tool-Registry, Agent-Identity, Sandboxing, Audit-Trail und Cost-Governance.
What ties all five packages together: customer-owned architecture.
All five packages follow four concrete decisions: code ownership (repository access for customers), build provenance (signed builds, SBOM, reproducible artefacts), identity without lock-in (no IdP that cannot be replaced), documented exit paths (with tested runbooks). That turns the five packages into a single technical practice — not a grab bag.