OPERATIONS MEMO / APRIL 2026
Stripe Issue + Free Deployment Strategy Diversification
We already have 12 products consuming shared free capacity across 11 Netlify sites and 5 Render resources. The response is to fix the Stripe blockage without letting payment remediation control deployment velocity.
Immediate rule: classify each launch as static, preview, or stateful before it claims another shared free-tier slot.
CURRENT LOAD
- 11 Netlify sites are already sharing one free hosting pool.
- 4 Render web services plus 1 Redis instance are already sharing another.
- The next deployment should reduce concentration risk instead of extending it.
STRIPE RESPONSE
- Keep revenue recovery on a separate track from hosting migration work.
- Route public support traffic through Bandcamp and direct contact until Stripe is verified.
- Only restore Stripe after the full checkout path is tested end to end.
PLATFORM SPLIT
- GitHub Pages or Vercel handle static sites, docs, archives, and preview-first fronts.
- Netlify is reserved for sites that still need its existing workflow or edge behavior.
- Render is reserved for stateful APIs, workers, and Redis-backed workloads.
ROLLOUT ORDER
- Audit every pending product by workload type before launch.
- Move the lowest-risk static deployments off the shared Netlify and Render path first.
- Track platform, owner, DNS, env vars, and quota exposure in one ledger.
- Review vendor mix before each new deployment, not after limits are hit.