Tutorials
Here you'll find practical examples to help you make the most of nullplatform.
📖 Build and deploy scopes​
Run a scope locally​
🎯 Goal: Build, run, and test a nullplatform agent-backed scope locally using Docker and Minikube.
Prepare your local machine, spin up Minikube, deploy the nullplatform agent, configure the example Kubernetes scope, create a demo release, and create a new scope.
👉 Run as scope locally
Set up a production‑ready Kubernetes scope​
🎯 Goal: Install the nullplatform agent, connect your scopes repo, register a Kubernetes scope, and create your first scope in the UI.
This tutorial shows how to get a Kubernetes scope ready for production: agent install, repo config, scope registration, and first scope creation.
👉 Set up a production‑ready Kubernetes environment
Deploy a production‑ready scheduled task scope​
🎯 Goal: Install the nullplatform agent, set up a Scheduled Task (CronJob) scope, and create your first scheduled task in the UI.
This tutorial walks you through creating a production‑ready scheduled task: clone the scopes repo, register the scope,confirm the channel, and create your first task.
👉 Deploy a production‑ready scheduled task scope
📖 Crafting services​
Create an SQS queue service​
🎯 Goal: Craft a ready-to-use AWS SQS queue service specification—complete with schema, UI, and Terraform/OpenTofu snippets—so your teams> can consistently provision queues in your platform.
In this tutorial, you’ll model a reusable service specification that provisions an AWS SQS queue. You’ll define the JSON Schema, optionally add a UI Schema, copy the generated IaC snippet, and create a link specification so the service can be triggered from other entities.
👉 Create an SQS queue service
📖 Approval and policy enforcement​
Automatically update application repositories on creation​
🎯 Goal: Automatically update application repositories with custom files when new applications are created.
Learn how to add a CLAUDE.md file at application creation time so new repositories come preloaded with useful context.
👉 Automatically update application repositories on creation
Require stage deployment before production​
🎯 Goal: Allow builds to be deployed to production only if they’ve already gone through
stage.
See how to enforce progressive promotion by requiring stage deployment before production.
👉 Require stage deployment before production
Enforce build quality policies on production deployments​
🎯 Goal: Gate production deployments using build catalog metrics. Allow deployments only when Coverage ≥ 80% and No critical vulnerabilities. Otherwise, require manual approval.
Publish coverage and vulnerability metrics to the build catalog. Use these metadata to create policies to enforce production gates. Non-compliant builds pause for approval before proceeding.
👉 Use build catalog to enforce policies on production deployments
Require manual approval for applications in production​
🎯 Goal: Add metadata to applications and enforce policies so sensitive apps require manual approval before production deployment.
Define application-level catalogs to mark applications as sensitive. Require production approval for those apps.
👉 Use application catalog to require approvals in production