{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "Newsletter | ayedo",
  "home_page_url": "https://ayedo.de/",
  "feed_url": "https://ayedo.de/en/newsletter/",
  "description": "The monthly ayedo newsletter: context on cloud infrastructure, digital sovereignty, and what is moving ayedo.",
  "icon": "https://ayedo.de/ayedo-logo-color.png",
  "favicon": "https://ayedo.de/ayedo-logo-color.png",
  "authors": [
    {
      "name": "Fabian Peter",
      "url": "https://www.linkedin.com/in/derfabianpeter/"
    }
  ],
  "language": "en",
  "items": [{
      "id": "https://ayedo.de/en/newsletter/august-2026/",
      "url": "https://ayedo.de/en/newsletter/august-2026/",
      "title": "August 2026",
      "content_html": "\u003cp\u003e\u003cimg src=\"/newsletter/august-2026/august-2026.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch2 id=\"welcome-to-the-first-edition-of-the-ayedo-newsletter\"\u003eWelcome to the first edition of the ayedo Newsletter\u003c/h2\u003e\n\u003cp\u003eCloud infrastructure is constantly evolving. That\u0026rsquo;s why we want to provide a monthly overview of what\u0026rsquo;s happening at ayedo—technically, entrepreneurially, and with a focus on digital sovereignty.\u003c/p\u003e\n\u003cp\u003eIn this first edition, we discuss our new Edge Cloud, the renewed certification according to \u003ca href=\"/en/compliance/\"\u003eISO 27001\u003c/a\u003e\n and \u003ca href=\"/en/compliance/\"\u003eISO 9001\u003c/a\u003e\n, and why we\u0026rsquo;re still quite alone on a European social media platform.\u003c/p\u003e\n\u003cp\u003eIn short: three topics worth reading about.\u003c/p\u003e\n\u003cp\u003eEnjoy the first edition!\nYour ayedo Team\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/newsletter/august-2026/august-2026-2.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch1 id=\"were-on-wediumbut-still-quite-alone\"\u003eWe\u0026rsquo;re on wedium—but still quite alone\u003c/h1\u003e\n\u003cp\u003eRecently, ayedo joined wedium—a European social media platform aiming to be an alternative to Instagram, TikTok, and others.\u003c/p\u003e\n\u003cp\u003eDeveloped in Europe, hosted in Europe, and backed by European service providers. It fits us well. After all, at ayedo, we talk a lot about digital sovereignty, European infrastructure, and how we can reduce our dependency on major US tech companies.\u003c/p\u003e\n\u003cp\u003eSo we should also be active where new European alternatives are emerging.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;ve created a profile, published initial content, and had a look around.\u003c/p\u003e\n\u003cp\u003eOur current conclusion:\u003c/p\u003e\n\u003cp\u003eWe still feel a bit alone. 👀\u003c/p\u003e\n\u003cp\u003eThat\u0026rsquo;s why we want to know:\u003c/p\u003e\n\u003cp\u003eWho from our network is already on wedium?\u003c/p\u003e\n\u003cp\u003eWhich companies, speakers, and content creators should we definitely get to know there?\u003c/p\u003e\n\u003cp\u003eAnd if you already have an account: Why aren\u0026rsquo;t you following us yet?\u003c/p\u003e\n\u003cp\u003eOf course, a new platform won\u0026rsquo;t become as big as LinkedIn, Instagram, or TikTok overnight. But a vibrant community doesn\u0026rsquo;t form by everyone waiting until enough others are already there.\u003c/p\u003e\n\u003cp\u003eSomeone has to start.\u003c/p\u003e\n\u003cp\u003eThat\u0026rsquo;s why we\u0026rsquo;d be delighted if more companies, social media managers, speakers, and creators try out wedium, bring their own content, and tell others about the platform.\u003c/p\u003e\n\u003cp\u003eWe don\u0026rsquo;t have to shut down all existing channels immediately. But we can start building our reach not solely on platforms of American tech giants.\u003c/p\u003e\n\u003cp\u003eSo: Check it out, follow us, and feel free to send us your profiles and recommendations.\u003c/p\u003e\n\u003cp\u003eLet\u0026rsquo;s work together to ensure that a strong European community also emerges on a European social media platform.\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"https://api.wedium.social/s/foVUndrt_9I2\" target=\"_blank\" rel=\"noopener\"\u003ehttps://api.wedium.social/s/foVUndrt_9I2\u003c/a\u003e\n\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/newsletter/august-2026/august-2026-3.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch1 id=\"the-ayedo-edge-cloud-is-available\"\u003eThe ayedo Edge Cloud is available\u003c/h1\u003e\n\u003cp\u003eModern applications don\u0026rsquo;t begin in the \u003ca href=\"/en/kubernetes/\"\u003eKubernetes\u003c/a\u003e\n cluster. From the user\u0026rsquo;s perspective, they begin where the first request hits the public infrastructure.\u003c/p\u003e\n\u003cp\u003eThis entry layer is often underestimated in architectural decisions. DNS, BGP routing, TLS termination, DDoS protection, Web Application Firewalls, health checks, and Layer-4 and Layer-7 load balancing are often seen as independent services. In reality, they form a critical platform layer: It determines whether, where, and under what conditions an application is accessible.\u003c/p\u003e\n\u003cp\u003eWith the ayedo Edge Cloud, we are transforming this layer into a unified operational and responsibility model.\u003c/p\u003e\n\u003ch2 id=\"why-we-consider-the-edge-as-its-own-platform-layer\"\u003eWhy we consider the Edge as its own platform layer\u003c/h2\u003e\n\u003cp\u003eIn recent years, we\u0026rsquo;ve built the ayedo Compute Cloud as a platform for the productive operation of \u003ca href=\"/en/kubernetes/\"\u003ecloud-native\u003c/a\u003e\n applications. Managed Kubernetes, GitOps, observability, object storage, registry, identity, and backups follow a common architectural and operational model.\u003c/p\u003e\n\u003cp\u003eBefore the Compute platform, responsibility remained fragmented.\u003c/p\u003e\n\u003cp\u003eA DNS provider doesn\u0026rsquo;t know the state of a backend. A classic load balancer has no influence on global routing paths. A Web Application Firewall doesn\u0026rsquo;t understand deployment states within a Kubernetes cluster. Each component fulfills a clearly defined task without necessarily mapping the complete path of a request.\u003c/p\u003e\n\u003cp\u003eThis is technically manageable but creates additional interfaces, dependencies, and fault domains. At the same time, it becomes more challenging to consistently design availability, security, and data paths across the entire architecture.\u003c/p\u003e\n\u003cp\u003eThe ayedo Edge Cloud is therefore not designed as an additional load balancer. It forms an independent platform layer between the public internet and the applications on the Compute Cloud.\u003c/p\u003e\n\u003ch2 id=\"own-routing-domain-instead-of-upstream-single-solutions\"\u003eOwn routing domain instead of upstream single solutions\u003c/h2\u003e\n\u003cp\u003eThe architecture doesn\u0026rsquo;t start with a reverse proxy but with its own Autonomous System.\u003c/p\u003e\n\u003cp\u003eCurrently, we operate Points of Presence in Hamburg, Alsbach, and Frankfurt. These locations announce the same IP prefixes via BGP and work in productive active-active operation. Incoming connections thus reach the preferred available location from the internet\u0026rsquo;s perspective via Anycast.\u003c/p\u003e\n\u003cp\u003eThe choice of entry point is not made by DNS-based redirection nor by a central geo-database. It results from the routing decisions of the participating autonomous systems.\u003c/p\u003e\n\u003cp\u003eThis model also changes how failures are handled.\u003c/p\u003e\n\u003cp\u003eIf a Point of Presence is no longer available, the corresponding route is withdrawn. The public IP address of the application remains unchanged. New connections reach one of the remaining locations after BGP convergence. There is no classic failover where a passive system first has to take on a new role. The remaining Points of Presence continue their already running productive operation; only the distribution of traffic changes.\u003c/p\u003e\n\u003cp\u003eAvailability is thus not established by standby capacity but by an architecture where all locations continuously operate productively.\u003c/p\u003e\n\u003ch2 id=\"decisions-before-the-first-pod\"\u003eDecisions before the first pod\u003c/h2\u003e\n\u003cp\u003eAt each Point of Presence, the Edge Cloud terminates incoming connections and processes them depending on the protocol on Layer 4 or Layer 7.\u003c/p\u003e\n\u003cp\u003eThis includes in particular:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eAnycast routing via the ayedo Autonomous System\u003c/li\u003e\n\u003cli\u003eDNS and certificate management\u003c/li\u003e\n\u003cli\u003eTLS termination\u003c/li\u003e\n\u003cli\u003eLayer-4 and Layer-7 load balancing\u003c/li\u003e\n\u003cli\u003eContinuous health checks of the backend pools\u003c/li\u003e\n\u003cli\u003eWeb Application Firewall\u003c/li\u003e\n\u003cli\u003eDDoS protection\u003c/li\u003e\n\u003cli\u003eTraffic and availability metrics\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eThe Edge thus decides before reaching the Compute platform whether a connection is accepted, which location processes it, and to which reachable backend it can be forwarded.\u003c/p\u003e\n\u003cp\u003eKubernetes remains responsible for orchestrating the workloads. The Edge, on the other hand, takes responsibility for their public accessibility. This separation is deliberately chosen: Both layers receive clearly defined responsibilities and can evolve independently of each other.\u003c/p\u003e\n\u003ch2 id=\"a-consistent-responsibility-model\"\u003eA consistent responsibility model\u003c/h2\u003e\n\u003cp\u003eFor decision-makers, the number of technical functions is less decisive than how responsibility is distributed.\u003c/p\u003e\n\u003cp\u003eThose who operate applications productively need not only compute resources. They need a reliable architecture for the entire data path—from public routing to workload. Fragmented responsibilities complicate root cause analysis, increase integration effort, and create dependencies that often only become visible during disruptions.\u003c/p\u003e\n\u003cp\u003eWith the Edge Cloud, we extend the responsibility of the ayedo platform to the public entry point of an application. Compute and Edge remain architecturally separate layers but are operated, monitored, and developed together.\u003c/p\u003e\n\u003cp\u003eThe ayedo Edge Cloud is now available.\u003c/p\u003e\n\u003cp\u003eIn upcoming posts, we will provide more detailed insights into the underlying decisions: operating our own Autonomous System, the properties of Anycast, the differences between Layer-4 and Layer-7 load balancing, and the interplay of BGP, health checks, and Kubernetes.\u003c/p\u003e\n\u003cp\u003eBecause the availability of an application is not decided in the cluster.\u003c/p\u003e\n\u003cp\u003eIt is decided along the entire path to it.\u003c/p\u003e\n\u003cp\u003e\u003cimg src=\"/newsletter/august-2026/august-2026-4.png\" alt=\"\"\u003e\u003c/p\u003e\n\u003ch1 id=\"ayedo-recertified-for-iso-27001-and-iso-9001\"\u003eayedo recertified for ISO 27001 and ISO 9001\u003c/h1\u003e\n\u003cp\u003eThe management systems of Ayedo Cloud Solutions GmbH have been re-evaluated by the independent certification body GUTcert.\u003c/p\u003e\n\u003cp\u003eThe result: Our certifications according to DIN EN \u003ca href=\"/en/compliance/\"\u003eISO/IEC 27001\u003c/a\u003e\n:2024 and \u003ca href=\"/en/compliance/\"\u003eISO 9001\u003c/a\u003e\n:2015 have been confirmed.\u003c/p\u003e\n\u003cp\u003eThe certified scope includes the development, operation, and hosting of \u003ca href=\"/en/kubernetes/\"\u003eContainer\u003c/a\u003e\n and software solutions, as well as the operation of IT infrastructures. Thus, the certificates directly relate to the services we provide for our customers in productive operation.\u003c/p\u003e\n\u003ch2 id=\"information-security-as-a-management-task\"\u003eInformation security as a management task\u003c/h2\u003e\n\u003cp\u003eISO 27001 defines requirements for an information security management system, or ISMS.\u003c/p\u003e\n\u003cp\u003eThe focus is not on individual security products or isolated technical measures. Instead, it assesses whether information security is anchored as a systematic and ongoing process within the company.\u003c/p\u003e\n\u003cp\u003eThis includes, among other things:\u003c/p\u003e\n\u003cul\u003e\n\u003cli\u003eThe structured assessment of information security risks\u003c/li\u003e\n\u003cli\u003eClearly defined responsibilities and permissions\u003c/li\u003e\n\u003cli\u003eDocumented operational and security processes\u003c/li\u003e\n\u003cli\u003eControlled handling of changes and vulnerabilities\u003c/li\u003e\n\u003cli\u003eIncident response and escalation paths\u003c/li\u003e\n\u003cli\u003eEvaluation of service providers and supply chains\u003c/li\u003e\n\u003cli\u003eRegular review and development of measures\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp\u003eEspecially when operating business-critical applications, it is not enough to view security solely from a technical perspective. Firewalls, encryption, backups, and access controls are necessary components of a robust infrastructure. Their effectiveness, however, depends on responsibilities, processes, and control mechanisms being equally robustly defined.\u003c/p\u003e\n\u003cp\u003eThe certification confirms that ayedo has implemented such a management system and applies it within the certified scope.\u003c/p\u003e\n\u003cp\u003eThe certificate according to DIN EN ISO/IEC 27001:2024 is valid until May 30, 2027.\u003c/p\u003e\n\u003ch2 id=\"quality-must-be-reproducible\"\u003eQuality must be reproducible\u003c/h2\u003e\n\u003cp\u003eIn parallel, our quality management system according to ISO 9001:2015 was confirmed.\u003c/p\u003e\n\u003cp\u003eFor an infrastructure operator, quality does not only mean that a platform functions under normal conditions. What matters is whether services can be delivered repeatedly and traceably under defined conditions.\u003c/p\u003e\n\u003cp\u003eThis requires documented processes, measurable quality objectives, regulated responsibilities, and a structured approach to deviations. Equally important is the ability to derive concrete improvements from disruptions, audit results, and customer feedback.\u003c/p\u003e\n\u003cp\u003eISO 9001 provides the organizational framework for this. It views quality not as a state to be achieved once but as a continuous control and improvement process.\u003c/p\u003e\n\u003cp\u003eThe certificate according to ISO 9001:2015 is valid until June 23, 2028.\u003c/p\u003e\n\u003ch2 id=\"what-a-certification-saysand-what-it-doesnt\"\u003eWhat a certification says—and what it doesn\u0026rsquo;t\u003c/h2\u003e\n\u003cp\u003eAn ISO certification is not proof that errors or security incidents are fundamentally excluded.\u003c/p\u003e\n\u003cp\u003eIt demonstrates something else: that risks are systematically assessed, responsibilities are bindingly regulated, processes are traceably documented, and the effectiveness of the management system is regularly reviewed.\u003c/p\u003e\n\u003cp\u003eFor customers, this reduces the dependency on informal processes and the knowledge of individual persons. At the same time, it provides a reliable basis for their own requirements regarding information security, supplier management, compliance, and auditability.\u003c/p\u003e\n\u003cp\u003eThe renewed certifi\u003c/p\u003e\n",
      "summary": "\nWelcome to the first edition of the ayedo Newsletter Cloud infrastructure is constantly evolving. That\u0026rsquo;s why we want to provide a monthly overview of what\u0026rsquo;s happening at ayedo—technically, entrepreneurially, and with a focus on digital sovereignty.\nIn this first edition, we discuss our new Edge Cloud, the renewed certification according to ISO 27001 and ISO 9001 , and why we\u0026rsquo;re still quite alone on a European social media platform.\nIn short: three topics worth reading about.\n",
      "image": "https://ayedo.de/august-2026.png",
      "date_published": "2026-08-25T11:12:03Z",
      "date_modified": "2026-08-25T11:12:03Z",
      "authors": [{"name":"Katrin Peter","url":"https://www.linkedin.com/in/katrinpeter/"}],
      "tags": ["digital-sovereignty","compliance","cloud","cloud-native","operations"],
      "language": "en"
    }
  ]
}