Analyze
Compare versions, trace a flag’s blast radius, guard a rollout, and bisect a regression. Every analysis reads stored structure only — no traffic is sampled and nothing is billed.
Compare two versions
Impact of a flag change
Before you touch a flag, see which other flags depend on it. Impact is read from each version’s prerequisite graph — no traffic is sampled and nothing is billed.
Dependency graph
Every flag in a version, what it requires, and what requires it.
Rollout guard
Compare two versions and surface the changes worth a second look — a default flipped, a rule ramped to a single variation, a flag removed, or a prerequisite left pointing at nothing.
Bisect a regression
Name the flag, an opaque context key, the attributes from the report, and the value you consider wrong. Loglune scans the published versions for the change at which that context started seeing the bad value. A rule that reads an attribute you leave out is reported as missing, never guessed.
Flag readiness
Can this flag be removed? Loglune checks that every context receives one variation, that nothing has changed it for 30 days, and that no other flag depends on it. The verdict is deterministic and identical on the CLI and the agent path.