Deployment adapters
Runtime, custody and persistence requirements for the current SDK.
Use production integration for SDK 0.7.2's current runtime, custody, verification and storage requirements. The Node starter runs on a persistent host; the public renderer and portable verifier have different hosting dependencies.
The canonical repository retains older Docker, Lambda, Cloudflare Worker and Vercel examples. These are development source, not current starter deployment targets, published hosting products or qualified recipes for SDK 0.7.2. The generator does not expose their old deployment flags. The former API snapshot's file/build table has been retired to avoid implying those examples are a maintained production path.
Prepare the deployment
- Resolve the actual SDK artifacts and required cryptographic bindings.
- Configure identity/verification/credential providers for the application.
- Select durable session, nonce, revocation and audit storage where those features are used.
- Keep server-only filesystem and secret operations outside browser/edge bundles.
- Verify the request path, denial behavior, origin policy and replica behavior on the target runtime.
Node filesystem key helpers cannot run in every edge environment. A fetch-standard wrapper does not prove the whole facade and its dependencies work in browsers, Deno, Bun, Workers and Node without adaptation. Use only capabilities supported by your target and test the resolved build.
See middleware, adapter packages, and source references. Deploying these documentation sites to Vercel does not deploy any product authentication or broker service.