Your stack. The L1 seats in it.

Rails are yours. Lightfoot does not collect the traffic on them.

You license named L1 graphs. They run in your account.

A Lightfoot L1 is a versioned l1spec file — YAML you can diff in a merge request. You plug it into the tools you already operate: PagerDuty, Jira, ServiceNow, GitLab, GitHub, Datadog, New Relic, and the internal systems behind your IAM. It triages that data and leaves a cohesive note, comment, or draft pull request. You customize the graph. You merge.

This is not a chatbot you paste tickets into. It is not a Lightfoot-hosted desk. The runner, the model, and the credentials stay with you. Lightfoot invoices an annual platform license: runtime, catalog, and connectors on one line. Not per-connector packs. Not someone else on your on-call.

Annual license. You run it.

Disk is the reviewable graph: ec2-disk-pressure. It reads volumes and CloudWatch in a role you mint, then writes a PagerDuty note, a New Relic annotation, and a GitLab draft MR. You still ack, escalate, and merge.

Open the catalog specimen

Note

Lands on the PagerDuty incident you already own. The graph does not ack, reassign, or resolve.

Annotation

Lands on the New Relic alert you already own. Same story: comment, not close.

Draft MR

Opens in your GitLab. Volume-expansion Terraform, human-required merge. mergeAllowed: true is invalid.