# Host ai workflow runner with Echo: streamed responses

Deploy an AI workflow runner built with Echo 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 Echo: 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). Not separately tested: your event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured; treat the AI workflow runner-specific behavior as your application code.

## Representative Queries
- Host ai workflow runner with Echo: streamed responses
- Where can I host AI workflow runner built with Echo?
- I need a tested end-to-end streaming transport, timeout behavior and client disconnect handling.

## Resource Requirements
- Compute
- Postgres

## Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## Prerequisites
1. A Echo project that builds and starts with the documented commands (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with servers:write, databases:read

## Workflow Steps
1. **Build and start**: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build). The server must bind 0.0.0.0 on PORT.
2. **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...
3. **Deploy**: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
   Command: `ample deploy . --name --public`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/streaming-response-service) from the example; then run your own checks...
   Command: `ample logs --kind build`

## Success Checks
- App responds on its public URL
- Streaming-response-service self-test

## Limitations
- Verified on the ubuntu-24.04 template at s-1vcpu-1gb with the example fixture...

## Cost Estimate
Monthly Amount: $10.00
- **App Server**: $5.00
- **Managed PostgreSQL Database**: $5.00

## Evidence Summary
- Echo pattern fixture deployed on Ample...
- The same Echo app deployed with a --release-command migration...

## Next Actions
- Browse the catalog index
- Search published recipes by intent, stack and constraints
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse AI workflow runner
- Browse Echo
- Browse Streaming response service
- Browse Deploy AI app