Author
Record a change, publish it as the next immutable version, and manage the credentials your SDK uses to pull and replay. Every change is one entry in the append-only log.
Current state
Every flag, segment, and config value as the change log stands now, published or not. Set a flag’s default here, or load any entity into the editor below.
| Entity | Key | Default | |
|---|---|---|---|
| Flag | checkout-v2 | ||
| Flag | new-pricing | ||
| Segment | beta-users | — | |
| Config | checkout-timeout-ms | — |
Define & publish
Record a change to a flag, segment, or config value, then publish the current state as the next immutable version. The value is the entity’s full state; its own key names what it changes.
SDK keys
Each key authenticates the SDK’s pull and replay requests as this tenant. The full key is shown once when you mint it — store it now; only its hash is kept, so it can’t be shown again.
Sign in to a tenant to mint and manage SDK keys.
Slack notifications
Push a message to your team when a reproduction is recorded, a version is published, or this period’s reproduction count crosses its billing threshold. Paste a Slack Incoming Webhook URL — it’s stored for this tenant and never shown to anyone else.
Launch from Slack
Mention the app in a thread and the report becomes a bug-resolution request — one credit, the same path as the console. Bind your workspace so an incoming mention resolves to this tenant, and give the bot token used to reply in that thread with the result and the pull-request link.