semek

About

My name is
Andre Semek.

I live in Berlin and work as a Cloud Engineer at Vattenfall. 15 years of infrastructure — from Windows servers through Linux to Azure and Kubernetes.

Portrait of Andre Semek — solution architect from Berlin

Vattenfall

I'm part of the ACAE team — Azure Container App Environment. We operate a central container platform for more than ten internal business units. My responsibility is the template repository: Bicep modules, Azure DevOps pipelines, DTAP model (Dev/Test/Acc/Prod), Blue-Green deployments with traffic splitting, Key Vault integration.

Before going Azure-native: classic Windows and Linux server administration, virtualisation, containers. The line from then to now is straight: maintainable setups, small diffs, clear modules, documented standards.

Personal

Two kids, football, music.

ADHD — means I work better with clear structures, short cycles, and a lot of documentation. That shapes how I run projects: small steps over big leaps, early showing over big reveals at the end.

Stack

Current focus areas.

  • 01

    Azure & Container

    Container Apps, AKS, ACR, App Services, Key Vault

  • 02

    Infrastructure-as-Code

    Bicep, Terraform, Ansible — modules over monoliths

  • 03

    CI/CD & Pipelines

    Azure DevOps, GitHub Actions — DTAP, Blue-Green, Rollback

  • 04

    Linux & Operations

    Proxmox, TrueNAS, OPNsense, CLI workflows, Monitoring

  • 05

    AI Automation

    Claude, OpenCode, n8n, MCP servers — custom agents (Hermes, OpenClaw, Paperclip)

How I work

My own agent setup.

I don't sell AI I don't run myself. My daily work goes through an orchestrated system of several agents — with clear roles, budgets and handovers. These are exactly the patterns I bring into projects.

  • 01

    Paperclip

    Governance

    The control plane: assigns goals and budgets to the agents, keeps an audit trail and approval gates. If an agent is the employee, Paperclip is the company.

  • 02

    Hermes

    Orchestrator

    My central agent with persistent memory — a second brain for homelab, business and personal life. Takes requests via chat, calls tools, controls my own infrastructure.

  • 03

    OpenClaw

    Gateway

    The executing worker at the gate: receives commands from Slack and Telegram and triggers approved actions. The reliable employee that gets its hands dirty.

  • 04

    Claude · OpenCode

    Engines

    The actual reasoning and coding engines underneath it all. Claude for complex, multi-step work; OpenCode for fast, cheap routine — every task on the right model.

The chain

  1. Chat — Slack / Telegram
  2. Paperclip — goals, budgets, approvals
  3. Hermes — orchestration + memory
  4. OpenClaw — execute actions
  5. Claude / OpenCode — reasoning + code
  6. My own infrastructure

The same principles — roles, guardrails, review steps, small diffs — are what I bring into client projects.

Write to me→