This month's highlights include a top-to-bottom Deployment Monitoring redesign, first-class Kubernetes job executions, and GCP app scaffolds for custom Terraform modules — plus AI-friendly module discovery in the CLI and a new Billing Admin role. Read on for details.
# Product
- Deployment Monitoring Redesign
- Kubernetes Job Executions in UI
- App Scaffolds for GCP
- AI-Friendly Module Discovery
- Billing Admin Role
## Deployment Monitoring Redesign
We've rebuilt the Deployment section of the Monitoring tab across all three workload types — Kubernetes, AWS ECS/Fargate services, and AWS ECS/Fargate jobs. The previous layout was bulky, hard to read at scale, and didn't surface the information engineers actually need when something breaks.
What's new:
- Compact, scannable layout for deployments and revisions
- Failure information surfaced directly on the deployment instead of buried behind a click-through
- Direct links to the debugging resources you reach for first (logs, tasks/pods, cloud console)
- Better Kubernetes deployment failure reporting — we enumerated the common k8s failure modes and improved the deployment logs to explain why a rollout failed instead of leaving you to dig through kubectl
- Kubernetes log filtering by pod, replica set, or job, so you can isolate the workload you care about
### Kubernetes Job Executions in UI
Jobs are now a first-class surface in Nullstone. You can list job executions in both the UI and CLI, see exit codes and lifecycle state (pulling image, creating container, starting, running), and tell apart cron-triggered, user-triggered (nullstone run), and workflow-triggered runs.
We also fixed a long-standing papercut: `nullstone run` now waits for all k8s job logs to flush before exiting, so you no longer lose the tail of the output on short jobs.
### AI-Friendly Module Discovery
Two new CLI commands make it easy for humans and AI agents to find and understand modules in the Nullstone registry:
- nullstone modules find — search the registry by metadata and contributor type, returning module metadata so an AI can pick the right one
- nullstone modules describe — introspect a module version's schema (vars, connections, outputs)
### Billing Admin Role
A new organization role for the person who manages the Nullstone subscription but doesn't write code. Billing Admins can create organizations, manage subscriptions, invite or remove members, and configure providers and cost providers — but cannot create or manage stacks, blocks, or workspaces. Useful for separating finance and admin duties from engineering access.
---
# Catalog
### App Scaffolds
Building a custom Terraform module for an app on GCP Cloud Run, GCP GKE, and AWS EKS used to mean re-implementing all the boilerplate Nullstone needs — service accounts, log streaming, metrics, artifact pushes, deployments, and remote access. We've shipped standalone scaffold modules that wire all of that up for you, so custom apps drop into Nullstone with the same operational surface as our first-party modules. These are available in the public Terraform registry:
- https://registry.terraform.io/modules/nullstone-modules/eks-appscaffold/aws/latest
- https://registry.terraform.io/modules/nullstone-modules/gke-appscaffold/google/latest
- https://registry.terraform.io/modules/nullstone-modules/cloudrun-appscaffold/google/latest
### GCP Cloud Run Service
Deploy a long-running API or web app to GCP Cloud Run via Nullstone.
- Cloud Run Service
