Host ai chat application with NestJS: streamed responses · Ample Computer
Host ai chat application with NestJS: streamed responses
Deploy an AI chat application built with NestJS on Ample using the streaming response service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on NestJS: a Server-Sent Events endpoint read incrementally through the public HTTPS gateway: five one-second chunks arrived spread over time with the first within seconds (not buffered), a 70-second stream of 36 chunks completed past common 60-second idle timeouts, and a client that disconnected after two chunks was observed and recorded by the server (disconnected=true). The AI chat application-specific behavior (your event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured) is your application code on that verified basis.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis supplied.
You need
A NestJS project that builds and starts with the documented commands (
npm install,nest build(TypeScript) thennode dist/main.json the node-22 template)A PostgreSQL driver reading
DATABASE_URLat runtime (auto-provisioned when omitted, or supplied with--env)An Ample account token with
servers:write,databases:read
Exact tested configuration
buildnpm run build --if-presentinstallnpm installruntimenodesizes1vcpu-1gbstartnpm run starttemplatenode-22
Steps
Build and start.
npm install,nest build(TypeScript) thennode dist/main.json the node-22 template. The server must bind0.0.0.0onPORT.Implement the pattern on PostgreSQL. The fixture's module implements streaming response service: a Server-Sent Events endpoint read incrementally through the public HTTPS gateway: five one-second chunks arrived spread over time with the first within seconds (not buffered), a 70-second stream of 36 chunks completed past common 60-second idle timeouts, and a client that disconnected after two chunks was observed and recorded by the server (disconnected=true). Copy the approach into your schema; keep migrations idempotent and run them with
--release-command.Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --publicVerify. Fetch the live URL and the pattern self-test route(s) (
/p/streaming-response-service) from the example; then run your own checks. On failure readample logs <deployment_id> --kind buildthen--kind runtime.$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary nestjs patterns”
✓ streaming-response-service self-test· http get/p/streaming-response-service → “an SSE stream: data: id=
Evidence
November 6, 2026 · canary run
NestJS pattern fixture deployed on Ample (npm install,nest build(TypeScript) thennode dist/main.json the node-22 template); checks passed for streaming-response-service and configuration-secrets. Pattern proof: a Server-Sent Events endpoint read incrementally through the public HTTPS gateway: five one-second chunks arrived spread over time with the first within seconds (not buffered), a 70-second stream of 36 chunks completed past common 60-second idle timeouts, and a client that disconnected after two chunks was observed and recorded by the server (disconnected=true).November 6, 2026 · canary run
The same NestJS app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested examples
- NestJS pattern fixture. Multi-pattern NestJS app whose streaming response service module was checked live; the module is under
tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
- Verified on the node-22 template at
s-1vcpu-1gbwith the example fixture. - The pattern checks verified the platform side; the AI chat application itself (your event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.