Production
Prepare SSR sessions, caching, security, diagnostics, and launch checks.
A
JA successful local render is not a production launch. Confirm session ownership, cache boundaries, access gates, error behavior, canonical URLs, and live board connectivity before shipping.
Before you begin
Deploy a preview that uses the production runtime, production origin, and the board key you intend to launch. Keep DNS or routing reversible until this section passes. If the board enables authenticated, paid, or employer workflows, prepare test identities and a safe way to exercise each enabled path.
Production sequence
- Implement SSR sessions or deliberately choose browser-owned storage.
- Separate public catalog caching from private responses.
- Review the security boundary for tokens, redirects, proxy routes, and logs.
- Run doctor against the deployed frontend.
- Complete the production checklist with the features enabled on your board.
What “ready” means
A production board resolves the intended pk_… key, renders public and private data under the correct cache policy, produces canonical search artifacts from the public origin, and fails visibly when a dependency or entitlement is unavailable. Skipped doctor checks are not passing checks—record why each one is intentionally out of scope.
SSR sessions
Own token cookies and refresh concurrency safely in server-rendered applications.
Caching
Separate public catalog caching from private and entitlement-sensitive responses.
SDK security
Protect tokens, validate redirects, isolate private caches, and respect API-enforced gates.
Cloudflare Workers
Run the SDK at the edge without leaking sessions or caching private responses.
Run doctor
Use SDK diagnostics to verify configuration, live reads, routes, SEO, and optional write probes.
Production checklist
Verify the complete custom board before directing users or search engines to it.