What problem does it solve? Lambda-style serverless functions time out on long-running workloads like AI agent streams, WebSocket servers, and SSE endpoints, and they run far from your database. This Skill guides you through deploying long-running Node.js functions directly onto a Neon branch, with DATABASE_URL injected automatically and compute in the same region as your Postgres data. ## Core Features & Use Cases - Long-Running Handlers: Deploy web-standard fetch handlers with a 15-minute time-to-first-byte budget, supporting streaming agents, WebSocket servers, and SSE endpoints that outlast traditional serverless limits. - Branch-Scoped Backends: Each Neon branch runs its own function version at its own URL against its own isolated database, so preview and CI environments get self-contained backends. - Function Triggers: Schedule cron jobs or react to object-storage uploads that POST to your function, declared in neon.ts or managed via the Neon CLI. - Use Case: You have a Next.js app on Vercel whose AI agent stream gets cut off at 60 seconds. Move just the agent onto a Neon Function, have the browser call it directly with a JWT, and the stream runs next to Postgres without host timeouts. ## Quick Start Ask the AI to define a function in neon.ts with a Hono handler that queries Postgres via the injected DATABASE_URL, then run neon dev locally and neon deploy to get its public invocation URL.
