SifrBolt Documentation
Documentation to understand the SifrBolt platform and use it effectively.
Why this matters
Each plan maps to a signed manifest. Validate the manifest whenever you need to confirm which packs and limits are available.
Plan Overview
| Plan | Best for | Highlights | Verify |
|---|---|---|---|
| Spark | Solo storefronts proving out SifrBolt | Launch accelerator, core performance automation | Manifest key spark |
| Surge | Multi-brand teams scaling experimentation | Adds edge cache orchestration, image IQ, partner handoffs | Manifest key surge |
| Storm | Regulated or high-traffic commerce | Compliance packs, DB automation, risk interlocks | Manifest key storm |
| Citadel | Enterprise fleets & agencies | ZK attestations, SSO/SAML, enterprise governance | Manifest key citadel |
How to Validate a Plan
Signature check
- Head to the Trust Center and download the license manifest JSON.
- Verify the manifest with the CLI (e.g.,
bunx @sifrbolt/verify manifest --plan <code>storm</code> --file manifest.json). - Share the signed output with procurement or your security office.
Upgrades & Add-Ons
- Enterprise Controls: Add-on for Surge and Storm when SSO/SAML or advanced WAF routing is required.
- Agency Toolkit: Unlocks blueprint automation and SLA hooks for partner rollouts.
- Proof Concierge: Our team manages bespoke attestation packs for your regulators.
For commercial questions, contact your account team or email success@sifrbolt.com. They will point you to the right manifest and paperwork.
Add regional pricing, promotions, or procurement paperwork under docs/src/pages/plans/ as they become available.