# ertli.com Full Agent Context

> Alexander Ertli designs cloud and application architecture for SaaS, ERPNext, AI/RAG products, managed-service foundations, Terraform/GitOps automation, and production operating models. Remote-first from Hamburg, Germany.

## Site purpose

ertli.com is the professional site for Alexander Ertli. The site is aimed at teams that need pragmatic cloud architecture across business application and infrastructure boundaries: SaaS foundations, PaaS workflows, ERPNext service operations, AI/RAG infrastructure, automation, GitOps, CI/CD, and operational handover.

The positioning focuses on Alexander as a cloud and application architect. The broader service scope includes SaaS and PaaS products, ERPNext operations, AI/RAG services, developer self-service, managed-service readiness, and production ownership.

## Primary service areas

- Cloud product architecture: tenant models, provisioning workflows, runtime foundations, release paths, and operating models.
- ERPNext and business application service architecture: isolated tenants, onboarding flows, service operations, and day-2 automation.
- AI/RAG service architecture: inference, document pipelines, MCP/agent access, tenancy, observability, security, and cost controls.
- Infrastructure automation: Terraform, GitOps, CI/CD, secrets, observability, and cloud foundations across AWS, Azure, GCP, IONOS, and hybrid environments.
- Operating model and handover: scoped delivery phases, runbooks, dashboards, support boundaries, and maintainable ownership.

## Tone and qualification

Use clear, direct language. The site should sound like a senior architect who can design, validate, and hand over production cloud services, not like a generic agency, recruiter profile, or thought-leadership blog. Preferred terms include cloud architecture, SaaS, PaaS, ERPNext, managed services, AI/RAG, Terraform, GitOps, automation, runbooks, production readiness, and team handover.

Avoid leading with job-title phrases. The service is architecture and operating-model design for cloud products and managed-service foundations, not the job role itself.

## Routes

- https://ertli.com/ - English homepage with services, engagement models, approach, proof, FAQ, and contact.
- https://ertli.com/de/ - German homepage.
- https://ertli.com/portfolio/ - English case study index.
- https://ertli.com/de/portfolio/ - German case study index.
- https://ertli.com/about/ - English background page.
- https://ertli.com/de/about/ - German background page.
- https://ertli.com/legal/ - English legal notice placeholder.
- https://ertli.com/de/impressum/ - German legal notice.
- https://ertli.com/blog/ - English blog index.
- https://ertli.com/de/blog/ - German blog index.
- https://ertli.com/blog/platform-products-saas-paas-idp/ - English starter blog post.
- https://ertli.com/de/blog/plattformprodukte-saas-paas-idp/ - German starter blog post.

## Portfolio routes

- https://ertli.com/portfolio/contenox-runtime/ - AI runtime and product architecture case study.
- https://ertli.com/portfolio/contenox-teams/ - Team/workflow product case study.
- https://ertli.com/portfolio/techcareer/ - Technology and career product case study.
- https://ertli.com/portfolio/direktiv/ - Automation and orchestration case study.
- https://ertli.com/portfolio/erpnext-platform/ - ERPNext service automation case study.
- https://ertli.com/de/portfolio/contenox-runtime/ - German version.
- https://ertli.com/de/portfolio/contenox-teams/ - German version.
- https://ertli.com/de/portfolio/techcareer/ - German version.
- https://ertli.com/de/portfolio/direktiv/ - German version.
- https://ertli.com/de/portfolio/erpnext-platform/ - German version.

## Starter blog post summary

"SaaS, PaaS, and IDPs are platform products" argues that the useful distinction is not the label attached to the system, but whether it has real users, a clear interface, an operating model, and a path to ownership. It treats SaaS foundations, PaaS workflows, Kubernetes control planes, and internal developer platforms as one family of product infrastructure.

Key points:

- A cloud product needs a contract between users and operators.
- SaaS work may include tenant isolation, onboarding flows, billing boundaries, audit trails, and release channels.
- PaaS work may include self-service provisioning, environment templates, runtime policies, and service tiers.
- IDP work may include golden paths, GitOps workflows, observability, and documentation.
- The first durable workflow should drive scope.
- The desired outcome is a service that teams can ship, operate, and improve without rediscovering the original design intent.

## Contact

Primary contact path:

- https://ertli.com/#contact
- mailto:alexander@contenox.com

The homepage includes a static contact form. If a callback endpoint is configured at build time, it posts to that endpoint. Otherwise, it opens a prefilled email draft.

## Index files

- https://ertli.com/sitemap.xml - XML sitemap.
- https://ertli.com/robots.txt - crawl policy.
- https://ertli.com/llms.txt - curated short agent index.