SifrBolt / docs

SifrBolt Documentation

Documentation to understand the SifrBolt platform and use it effectively.

Why DB Packs Matter

DB Packs bundle the data-layer capabilities that keep personalized storefronts responsive. Enabling them allows SifrBolt to combine adaptive Redis caching, stale-while-revalidate, and a microcache tier.

Plan check

Available on Surge plans and above. Confirm your manifest includes db_packs and redis_advanced before proceeding.

Preflight

  1. Download the latest signed manifest from Plans & Entitlements or the Trust Center and confirm db_packs is enabled.
  2. Identify the tenant(s) you will activate first—start with a sandbox or low-risk storefront if this is your first rollout.
  3. Invite stakeholders who will review the metrics (engineering, merchandising, compliance) so everyone shares the same view of impact.

Activate in the Console

  • Turn on DB Packs and Adaptive Redis toggles for your chosen tenant.
  • Trigger the warm-up action from the console to preload object cache and avoid cold-start latency.
  • Monitor the Redis Engine widget to confirm APCu and adaptive policies report as Enabled.

Validate Performance

Verification

  1. Capture before/after charts for page speed and conversion using the dashboard bundled with the activation pack.
  2. Use the verification CLI to confirm the activation trail is signed (for example bunx @sifrbolt/verify rollout --bundle db-packs-2025-01).
  3. Attach the verification output to your change record or launch recap.

Keep an Eye On

  • APCu hit rate ≥ 80% indicates the microcache is carrying its weight.
  • Redis p95 latency under 6 ms keeps campaigns safe during spikes.
  • Adaptive skip reasons: if a key lands on the deny list unexpectedly, adjust via the provided filters or templates.

Rollout Next Steps

  • Expand coverage to the rest of your fleet using rollout rings (10% → 50% → 100%).
  • Pair with Image IQ or other performance packs once latency stabilizes.
  • Update your runbooks so the activation steps and verification outputs are easy to reference later.

Add vertical-specific DB Pack guidance under docs/src/pages/implementation/ to help new teams cruise through activation.