Zhivko Todorov
ALL CASE STUDIES

CASE 69 · SOLSTICE · 2024

APPCONFIGFEATURE FLAGSLAUNCHDARKLYCOST

Feature flags, on AWS, at a tenth of the price.

An edtech platform had been on LaunchDarkly for three years, paying $9,400/mo for a usage tier that mostly covered seats they didn’t need. The flag features they actually used were a subset. We migrated to AWS AppConfig with a thin SDK and got the bill to $920/mo without losing capability.

INDUSTRY

Edtech

DOMAIN

PLATFORM

DELIVERED

2024

STACK

AWS APPCONFIG·APPCONFIG AGENT·CLOUDWATCH METRICS·EVENTBRIDGE·CUSTOM SDK

RESULTS

What changed, by the numbers.

FF PLATFORM COST

−90%

$9.4K → $0.9K / MONTH

FLAG EVALUATION LATENCY

< 5ms

LOCAL AGENT

GRADUAL ROLLOUT

PRESERVED

BAKE-TIME + ROLLBACK

MIGRATION TIME

5w

INCL. SDK + SHADOW

HOW IT WENT

LaunchDarkly’s feature set is huge; this customer used roughly a quarter of it. They had flags, percentage rollouts, gradual ramps, and audit logs. They didn’t use experimentation, segmentation by 17 dimensions, or the SDK-side analytics. The premium tier paid for everything anyway.

AppConfig with the local agent matched the runtime semantics that mattered. We built a thin SDK wrapper that translated the team’s existing flag-evaluation calls (which were already abstracted behind a custom interface) to AppConfig under the hood. Gradual rollouts mapped to AppConfig’s deployment strategies.

Shadow ran for two weeks with both systems returning evaluations. Once parity was confirmed, we switched the production reads to AppConfig and turned off LaunchDarkly. The savings funded two engineering hires in the next budget cycle.

READY WHEN YOU ARE

Let's get your AWS bill (and architecture) in order.

The discovery call is free. You walk away with at least one concrete idea — even if we never work together.

Or email directly →