Ledgerly
How a regulated finance company gave every team flags without giving up control.
- Industry
- Fintech
- Size
- About 600 people
Sample stories, written for this template. Replace them with real, approved customer stories before launch.
The challenge
Ledgerly’s auditors needed to know who changed what in production, and when. A homegrown flag table couldn’t tell them.
Only a handful of engineers were trusted to touch it, so every launch queued behind them.
What they did
Production changes now need a second approver, and every change lands in an exportable audit log.
Seats are provisioned from the company’s identity provider, so access follows the org chart.
“Our auditors asked for the change history and we sent a link. That had never happened before.”
What changed
- Any team can request a production change; the right reviewer approves it in Slack.
- Audit evidence for flag changes is an export, not a week of spreadsheets.
- New features reach one country at a time, matching each market’s approval.
What Ledgerly uses
-
Feature flags
Put every change behind a flag and decide who sees it, without a deploy.
Learn more: Feature flags -
Targeting
Rules that read like a sentence: plans, regions, versions and your own attributes.
Learn more: Targeting -
Approvals and audit
Required reviews, an audit log and SSO for teams with a security review.
Learn more: Approvals and audit
Write your own story
Start free and roll out your first change this week.