Scrim presents
Behind the curtain
Flags, rollouts, guardrails and the paper trail, in the one place your whole team can read.
50%
62,424 users
see the new checkout
Error rate
0.21%
p95 latency
186 ms
Conversion
+3.1%
Seven more tools, each doing one job, all reading the same flags.
Serveto users where
Q6
Show it to people on the Pro plan, in Portugal and Spain, on iOS 18 or later. Rules read like sentences and preview who they match before you save.
Q7
25% at nine on Tuesday, 50% on Wednesday if the guardrails held, everyone on Thursday. Write the run once and go to lunch.
p95 latency
251 ms
Safety curtain down. Rolled back to 0% in 0.8 s.
Q8
Pick the numbers that matter for this release. If one leaves its band, the safety curtain drops and the rollout waits for you.
Cast B converts 16% better · 97% sure
Q9
Run two versions on alternate seats and let conversion decide. Scrim says when the result is real, and when it is still noise.
Ana Ruiz wants to raise checkout-v2 to 50% in Production.
KT Approved by Kenji · just now
Q10
Changes to production need a second signature, the way a good stage manager wants one. Everything else moves as fast as you do.
Q11
Every flip, who called it, from where, and why, written down like a stage manager's report after every performance.
#482 Remove checkout-v2
Open- if (scrim.isOn("checkout-v2", user)) {- return renderCheckoutV2(user);- }- return renderCheckout(user);+ return renderCheckoutV2(user);
Q12
When a flag has sat at 100% for thirty days, Scrim opens the pull request that takes it out of your code.
For developers
The SDK keeps your rules in memory and evaluates them on your own server, so asking costs a thousandth of a round trip.
1import { Scrim } from "@scrim/node";23const scrim = await Scrim.connect(process.env.SCRIM_KEY);45export function checkout(user: User) {6 if (scrim.isOn("checkout-v2", { id: user.id, plan: user.plan })) {7 return renderCheckoutV2(user);8 }9 return renderCheckout(user);10}
Rules live in memory on your own server. No network call is made per check.
A change in the console streams to every connected SDK, worldwide, before you have let go of the mouse.
If Scrim is ever unreachable, the SDK keeps the last rules it saw, and your code's defaults after that.
4.9
Average from 2,400 teams
“We used to freeze deploys on Fridays. Now we ship on Fridays and nobody notices.”
“The safety curtain came down at 2 a.m. and fixed it before I found my glasses.”
“Finally, a flag tool our product managers use without asking an engineer.”
“Strike alone paid for it: 412 dead flags out of our code in one quarter.”
“Rollouts went from a meeting to a cue.”
“0.04 ms. I checked. Twice.”
“Two casts told us the new pricing page lost money before it cost us any.”
“The show report is the first audit log our compliance team has ever praised.”
Every plan has unlimited flags. Move the slider to the number of people who use your product in a month.
Admit your whole team
No. CO-2500
Company
$240/ month
For teams who ship every day.
Free
From $120
Let's talk
Every answer ships the way your features will. Switch a flag on to roll it out to yourself.
Rolled out to you
1 of 6
Flags · help center
Production
No. You keep deploying the way you do now. Scrim decides who sees what once the code is out there.
Served to you · just now
Your SDKs keep the last rules they received and carry on evaluating them locally. An SDK that has never connected uses the defaults written in your code.
Served to you · just now
No network call happens per check. Rules are evaluated in memory, in about 0.04 ms.
Served to you · just now
Rules and show reports live in the EU or the US, your choice. The user attributes you target on stay on your servers.
Served to you · just now
Yes. Scrim imports the JSON exports most flag tools produce, and the SDK can wrap your old one while you switch, flag by flag.
Served to you · just now
Either. An engineer writes the flag once; after that anyone you allow can raise or lower it from the console, with approvals on production if you want them.
Served to you · just now
Something else? boxoffice@scrim.example
Curtain call
2,400
teams ship with Scrim
1.2B
flag checks a day
0.8 s
to roll back, worst case
0
Friday deploy freezes