Configuration management
Every system, on one item.
Create a configuration item — an IT service, a customer, a server — and attach plugins that surface live data on it: GitHub deployments, PagerDuty incidents, Stripe revenue. The whole picture, on the thing it is about.
GitHub
deploy #412 · main
production · 12 minutes ago · green
PagerDuty
no open incidents
last: 3 days ago, resolved in 41m
Stripe
$18,420 this month
+6% vs last · 212 customers
The four ideas
A small model that fits any business.
Types you define, items that instantiate them, plugins that know one system, connections that join the two.
CI types
A template with the fields you care about — an IT Service, a Customer, a Server. Yours to define; nothing is hard-coded.
Configuration items
An instance of a type: "Checkout Service", "Acme Pty Ltd", "db-primary-1". The page everything else attaches to.
Plugins
A code-defined integration with one external system — GitHub, PagerDuty, Stripe — first-party or community-built.
Connections
A CI plus a plugin plus its configuration and credentials. Add one, and the plugin's data appears on the item.
How it goes
Three steps to a live item.
- 01
Define a type
Name it and give it the fields that matter: owner, environment, tier, whatever your business tracks.
- 02
Add an item
Create the Checkout Service, the customer, the server. It is a page from the first save.
- 03
Attach plugins
Connect GitHub, PagerDuty, Stripe. Their live data sits on the item, together, where the people who need it look.
Questions