Framework guides Use a published Boundry SDK where one is available, or integrate through the regional REST API while the package for your ecosystem is still in release preview.
JavaScript / TypeScript Node.js Create one client in a server-only module and reuse it from jobs, controllers, or route handlers. Read guide Next.js Keep this module server-only, then call it from a Route Handler, Server Action, or background job. Read guide Remix Use a .server.ts module and call it from an action or loader that runs on the server. Read guide Nuxt Place the client under server/ and call it from a server route or Nitro task. Read guide TanStack Start Call the server-only helper from a server function; never serialize the API key to the client. Read guide SvelteKit Keep the client under $lib/server and call it from an action, hook, or +server.ts endpoint. Read guide Express Create the client once at process startup and call the helper from your route or queue consumer. Read guide RedwoodJS Keep the client in the API side and call it from services, functions, or background jobs. Read guide Hono Pass a Boundry API key from the runtime environment and call the helper inside a Hono handler. Read guide Bun Bun provides web-standard fetch, so the same package and client work without an adapter. Read guide Astro Call the helper only from an Astro action, endpoint, or server-rendered component. Read guide Encore.ts Create the client in backend code and call it inside an Encore API endpoint or subscription handler. Read guide Better Auth Call this helper from Better Auth email callbacks for verification, password reset, and invitations. Read guide Vercel Functions Create the client outside the request handler so warm invocations reuse it. Read guide AWS Lambda Create the client outside the Lambda handler and await the send before returning. Read guide Cloudflare Workers The SDK uses web-standard fetch and has no Node runtime dependency. Bind BOUNDRY_API_KEY as a Worker secret. Read guide Deno Import the npm package through Deno and read the key from Deno.env on the server. Read guide Supabase Edge Functions Use the npm package in the Deno-based function and store BOUNDRY_API_KEY as a Supabase secret. Read guide