Coordinate flag reviews and updates
Connect
SPIRITT
LaunchDarklyLaunchDarkly
Put releases in motion
SPIRITT builds and runs the operation around your feature flags, from environment promotion and approvals to experiment setup and dependency-aware cleanup.
What you can do with LaunchDarkly.
Releases with a process
Turn release plans into flag workflows, scheduled changes, and approval requests tied to the right project and environment.
Less flag debt
Combine flag status, evaluation counts, dependencies, and code reference evidence to turn cleanup candidates into actionable engineering work.
Connected release context
Give product and engineering a shared view of flag changes, experiment definitions, and release decisions across LaunchDarkly and team tools.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for feature releases, experimentation operations, or flag lifecycle management.
02
Connect LaunchDarkly
Connect LaunchDarkly with access to the projects, environments, and flag operations your mission requires.
03
Delegate an outcome
Give SPIRITT a release mission. It builds the workflow, coordinates connected tools, and executes within your permissions and approval rules.
Hand over a mission.
Choose a mission. Make it yours.
Put LaunchDarkly to work.
Give every flag a release plan
Questions
LaunchDarkly, with SPIRITT.
01What can SPIRITT execute in LaunchDarkly?+
SPIRITT can create flags, segments, environments, experiments, release pipelines, scheduled changes, and workflows. It can also create approval requests, apply approved changes, and copy flag configurations between environments within a project.
02What access does the connection need?+
LaunchDarkly supports API key and OAuth connections. The connected identity needs permissions for the target projects, environments, and actions. Reading flag status requires different access from creating environments or applying changes, so the mission should use appropriately scoped access.
03Can it run releases without bypassing approvals?+
Yes. SPIRITT can inspect project approval settings, submit flag or configuration-copy approval requests, track reviews, and apply requests once approved. It can operate a recurring approval queue while keeping review requirements separate from execution.
04How can LaunchDarkly work with our engineering tools?+
SPIRITT can link flags to external resources, coordinate reviewers in Slack, create cleanup work in Linear, and combine audit entries with Sentry incident evidence. Webhooks can feed a custom release journal so change context stays available outside LaunchDarkly.
05What custom apps can SPIRITT build around feature flags?+
Useful builds include a release control room showing environment status and approvals, a context membership diagnostic app, and a searchable flag change journal. These use LaunchDarkly configuration and operational evidence rather than replacing application-side flag evaluation.
06How is this different from a LaunchDarkly workflow?+
LaunchDarkly workflows automate flag changes through configured conditions or schedules. SPIRITT can create those workflows and operate the wider process: gather release context, coordinate owners, build custom interfaces, investigate incidents, and turn flag lifecycle evidence into engineering tasks.