How Lumenfold cut rollback time from 40 minutes to 4 seconds
Lumenfold deploys 60 times a day to 4 million readers. Their rollback used to be a 40-minute redeploy. Now it is a toggle, and their on-call rota is boring again.
Teams from four-person startups to public companies ship through Driftwire. Here is what changed for two of them.
−92%rollback time
“Our checkout rewrite went to 1% on a Tuesday afternoon and to everyone by Thursday. Nobody stayed late. That had never happened before.”
312dead flags deleted
“Two thousand flags, four services, one weekend. The audit log is how we proved nothing changed for customers.”
Across every customer
“Rollback used to be a 40-minute pipeline. Now it is a toggle, and on-call is boring again.”

“We moved 2,000 homegrown flags in a weekend and deleted 312 of them the next month.”

“Guardrails turned rollouts from a meeting into a schedule.”

“We ship forty times a day with a team of nine. Driftwire is why that number does not scare anyone.”

“The audit log settled an argument in our incident review in about eight seconds.”

“Edge evaluation took 40 ms off every page that checks a flag, which is most of them.”

Lumenfold deploys 60 times a day to 4 million readers. Their rollback used to be a 40-minute redeploy. Now it is a toggle, and their on-call rota is boring again.
Parcelwick had 2,000 flags in a homegrown YAML service and nobody willing to touch it. They moved every one in a weekend, without a single user noticing.
Evaluating flags at the edge is fast. Evaluating them on your server is simple. Which one you want depends on numbers you can measure in an afternoon.
Free for five seats and 10,000 monthly users. Your first flag is about ten minutes away, with nothing to pay and nobody to talk to.