Catalog

700+ catalog kinds across 8 providers, each a typed schema with its own fact sheet: what it costs, which controls it enforces, and the least permissions its runner needs.

For the platform engineer choosing what their organization may deploy, and the reviewer who wants the fact sheet before the deploy.

What You Get

Shipped behavior, stated as it works today.

A Fact Sheet on Every Kind

Every covered kind states which of a fixed list of 17 technical controls it enforces, with evidence for each claim.

Priced From a Named Release

The cost names the catalog release its prices came from and, when both can be priced exactly, how much more or less this will cost each month than what is deployed today.

Curated to What You Allow

The catalog can be curated to the catalog kinds your organization allows. The console, the CLI, and the agent all see the same list and refuse the same things, because one answer serves both.

A Schema, Not a Wiki Page

Each kind is a Protocol Buffer definition in the Kubernetes Resource Model shape with field-level validation, and SDKs generated in Go, Python, TypeScript, and Java.

Open Source, Every Module

Every infrastructure module is open source under Apache 2.0. If you leave, you take your manifests and keep deploying them with the open-source CLI.

A kind’s fact sheet

kind

AwsRdsCluster · aws.planton.dev/v1alpha1

schema

typed spec · field-level validation · SDKs in 4 languages

cost

priced · 3 presets · catalog release named

controls

6 of 17 enforced · evidence attached · absence stated

permissions

least privilege · validated against the provider’s own inventory

modules

Pulumi · Terraform · Apache 2.0

An illustration of the record the product shows. The kind is real; the figures are examples.

Where This Is Proven

The same claims, written for the person who signs, with the record beside each one.

Verified Before Deploy

Before anything is created, Planton states the monthly cost with its coverage, the least-privilege permissions, and the controls each kind enforces.

What It Proves →

Security Posture

Seventeen technical controls with evidence per kind, crosswalked to four frameworks, stated honestly: a kind enforces controls; it is never called compliant.