Systems and incident record
The rows below say how each system is built, and the incident line says what was last written down.
Architecture
| Component | Platform | Detail |
|---|---|---|
| Static site | CF Pages | Static export on Cloudflare Pages, served from Cloudflare’s global edge |
| Stripe checkout | Payment Links | Direct-to-Stripe Payment Links per lane tier. PCI-DSS Level 1 handled by Stripe; we never touch a card number |
| Fulfillment | CF Worker | Token issuance, R2 signed URLs, Stripe webhook ingest, ops Discord embeds |
| Lead nurture | CF Worker + KV | Email drip cadence rendered server-side, sent via sovereign Postal SMTP. DKIM-signed |
| Discord ops bus | CF Worker | Slash commands, journal post-commit hook, pinned ops dashboard refreshing twice daily |
| Mail (Postal) | Sovereign | Self-hosted SMTP relay (sovereign mail stack). No Mailchimp, no SendGrid in the path |
Incident record
- 2026-05-14 · resolved — site, checkout, mail relay and lead-nurture pipeline were all green when this line was written. It is the only entry in this log, and the log is written by hand: the absence of a later entry is not evidence that nothing has broken since.
This page is rebuilt and republished with the site. For SLAs and incident SLOs see Trust + security. To report an incident, email info@garnetgrid.com.