Identity first
Identity, least privilege and explicit control planes are the foundation of secure cloud adoption.
Cloud platforms
Structured learning for Azure, Google Cloud and Nais, alongside an architectural guide to Altinn and selected cloud-native reference points.
Cloud platforms deserve a dedicated area because platform decisions affect architecture, security, cost, observability and how solutions can evolve. Azure remains a detailed knowledge base. Google Cloud and Nais now form a connected learning journey: first understand the cloud primitives, then learn which decisions Nais turns into a safer, simpler developer contract.
Altinn remains a separate deep dive because it represents a different kind of Norwegian platform: shared capabilities for building and operating public digital services. CNCF is included as the open ecosystem behind many of the cloud-native ideas used across these platforms.
Dedicated knowledge area
Learn the Google Cloud foundation, compare direct cloud operation with Nais, then see what Nais standardizes on top of GKE and managed services. Thirteen bilingual guides and modules form one connected path.
Start with Google Cloud →Products, architecture decisions, identity, security, certifications and 75 scenario-based knowledge questions.
Open →ALTNorwegian digital infrastructureAltinn Studio, Altinn Apps and shared platform services for authentication, authorization, storage, events and notifications.
Open →NAISSeven-part learning pathBegin with Google Cloud direct versus Nais, then continue through workloads, identity, data, observability and production responsibility.
Open →GCPSix-module learning pathResource hierarchy, IAM, networking, compute, data, operations and architecture—with direct links to the Nais abstractions built on top.
Open →CNCFOpen ecosystemProjects and standards around containers, Kubernetes, observability, service mesh and cloud-native architecture.
Open ↗Identity, least privilege and explicit control planes are the foundation of secure cloud adoption.
Begin with requirements for availability, data, security, performance and operations—then choose the service.
Infrastructure as code, policy, observability and repeatable pipelines reduce configuration drift.