Host rest api with Hono: streamed responses

Deploy a rest api built with Hono 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 Hono: 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 rest api-specific behavior as your application code.

Representative Queries

• Host rest api with Hono: streamed responses
• Where can I host REST API built with Hono?
• I need a tested end-to-end streaming transport, timeout behavior and client disconnect handling.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. 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

• A Hono project that builds and starts with the documented commands (npm install and npm run start with @hono/node-server on the node-22 template)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• An Ample account token with servers:write, databases:read

Tested Configuration

• Template: node-22
• Runtime: node
• Size: s-1vcpu-1gb
• Install: npm install
• Build: npm run build --if-present
• Start: npm run start

Workflow Steps

1. Build and start: npm install and npm run start with @hono/node-server on the node-22 template. 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.
4. Verify: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

Examples

• Hono pattern fixture: Multi-pattern Hono app whose streaming response service module was checked live.

Success Checks

• App responds on its public URL.
• Streaming-response-service self-test: an SSE stream.

Limitations

• Verified on the node-22 template at s-1vcpu-1gb.
• The rest api itself is application code and was not separately tested.

Cost Estimate

• Monthly Amount: $10.00
• Components:
  • App server: s-1vcpu-1gb - $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb - $5.00

Evidence Summary

• Hono pattern fixture deployed on Ample; checks passed for streaming-response-service and configuration-secrets.

Next Actions

• Browse the catalog index.
• Search published recipes by intent, stack and constraints.
• Prepare a deployment plan for an authorized project.