st8 — Versioned State Store

Config management done right

Everything you need to change application behavior at runtime — safely, with history.

Every write creates an immutable, numbered revision. Nothing is ever overwritten — full history, always.

Roll back any namespace or branch to a previous revision or named checkpoint with a single command.

Run canary deployments or A/B tests by writing different config to different branches. Switch at request time.

Flat, free-form partitioning. Use any convention that fits — payments/prod, platform-staging, tenant-42.

st8d speaks the OpenFeature Remote Evaluation Protocol. Point your OFREP provider at it and use your flags through the standard OpenFeature SDK.

st8d is a single binary. Run it on any Linux machine — bare-metal, VM, or container. MIT licensed.

# Push config — no restart, no redeploy

$ echo '{"new_checkout":true}' > feature_flags.json

$ st8ctl --local apply -f feature_flags.json --message "enable new checkout"

✓ Revision 42 created

# Tag a known-good state

$ st8ctl --local checkpoint stable

✓ Checkpoint "stable" → rev 42

# Something went wrong — roll back instantly

$ st8ctl --local rollback --checkpoint stable --message "revert: latency spike"

✓ Rolled back to rev 42 (rev 43 created)