Nais

Learn the platform contract—and the cloud beneath it.

A practical path from the Google Cloud-versus-Nais decision through teams, workloads, identity, data, observability and production responsibility.

7 modules Foundation → production Reviewed 22 August 2026

Nais is an application platform built around autonomous teams that develop, deploy and operate their own products. It supplies a secure runtime and self-service building blocks so each team does not have to assemble a Kubernetes and cloud platform from scratch. The name originally meant NAVs Application Infrastructure Services; the Nais community is working towards letting the N mean Norwegian.

Nais is not a separate cloud provider. Each cloud environment is a Kubernetes cluster on Google Kubernetes Engine, while selected capabilities come from Google Cloud, Aiven and platform-operated components. The developer-facing contract is intentionally higher-level: teams primarily use Nais manifests, Nais Console, GitHub Actions and platform APIs.

That abstraction changes who handles complexity, not whether production responsibility exists. This learning path focuses on both sides of the contract: what the platform automates and what the product team must still understand, decide and operate.

If you are deciding between the two operating models, begin with Google Cloud directly or through Nais?. It compares benefits, limits, support responsibilities and PostgreSQL outages before the technical modules begin.

From foundations to production

Start with the direct comparison, then follow the life of a service: understand the platform, deploy a workload, connect it safely, add data and telemetry, and prepare it for production.

Guide35 min

Decision guide

Google Cloud directly or through Nais?

Compare the developer experience, responsibility, support, flexibility and failure behavior when a product team uses Google Cloud directly or through Nais.

  • Benefits and trade-offs
  • Responsibility and support
  • PostgreSQL failure scenarios
Start module →
0125 min

Foundations

Platform model and architecture

Understand Nais as a product for autonomous teams, the team/environment/workload model, and how its contract maps to Kubernetes and Google Cloud.

  • Teams and environments
  • Paved roads
  • Naiserator and GKE
Start module →
0235 min

Developer path

Workloads, manifests and delivery

Move from container image to Nais Application or Naisjob, understand the manifest contract, and design a traceable GitHub-to-production delivery flow.

  • Application and Naisjob
  • nais.yaml
  • GitHub Actions
Start module →
0335 min

Security

Identity, authentication and zero-trust traffic

Separate user, delegation, machine and workload identities; design explicit access policies; and expose services only to their intended audience.

  • ID-porten and TokenX
  • Maskinporten and Entra ID
  • accessPolicy
Start module →
0435 min

Platform capabilities

Data services and observability

Choose Nais data capabilities by behavior and ownership, then combine logs, metrics and traces into useful service-level operations.

  • Cloud SQL and buckets
  • Kafka and BigQuery
  • OpenTelemetry and Grafana
Start module →
0530 min

Operations

Production readiness and operating ownership

Turn a deployed workload into an operated product through SLOs, dependency and recovery design, secure supply chains, cost ownership and incident practice.

  • Production checklist
  • Supply chain security
  • Incidents and recovery
Start module →
0620 min

Assessment

Nais production knowledge check

Fifteen scenarios on the Nais platform model, workloads, delivery, identity, access, data, observability and production ownership.

  • 15 scenarios
  • Explanations
  • Official Nais sources
Take the knowledge check →

Revisit the Google Cloud foundation

Nais deliberately hides much of Google Cloud and Kubernetes, but projects, IAM, workload identity, VPC, GKE and managed data services still shape security, location, resilience and cost.

Open Google Cloud →