OpenAgentID documentation
Integration map

Deployment adapters

Source examples for Docker, Lambda, Workers, and Vercel with explicit prerequisites.

The SDK repository includes four private source examples under openagent-sdk/deploy. They illustrate deployment integration; they are not published managed authentication services.

ExampleSource entry and build
Dockerdeploy/docker/server.ts; tsup targets Node20
AWS Lambdadeploy/aws-lambda/handler.ts; SAM deployment configuration
Cloudflare Workerdeploy/cloudflare-worker; Wrangler configuration and Worker entry
Vercel Edgedeploy/vercel-edge; separate Next.js application and middleware/route integration

Prepare the deployment

  1. Resolve the actual SDK artifacts and required cryptographic bindings.
  2. Configure identity/verification/credential providers for the application.
  3. Select durable session, nonce, revocation and audit storage where those features are used.
  4. Keep server-only filesystem and secret operations outside browser/edge bundles.
  5. 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.

On this page