Connect Statsig to Crush
Give Crush governed access to Statsig’s 93 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Statsig to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Statsig in Runlayer
Add Statsig from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Statsig’s 93 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Statsig
Sign in the way Statsig requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Statsig from Crush
Statsig’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
93 Statsig tools in Crush
Runlayer policy decides which of these Crush users can call.
Approve autotune review
Approve an in-flight review of an autotune experiment.
Approve dynamic config review
Approve an in-flight review of a dynamic config.
Approve experiment review
Approve an in-flight review of an experiment (A/B test).
Approve gate review
Approve an in-flight review of a gate (feature flag).
Cancel autotune review
Cancel (withdraw) an in-flight review of an autotune experiment.
Cancel dynamic config review
Cancel (withdraw) an in-flight review of a dynamic config.
Cancel experiment review
Cancel (withdraw) an in-flight review of an experiment (A/B test).
Cancel gate review
Cancel (withdraw) an in-flight review of a gate (feature flag).
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Statsig call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more