# Host Reporting Dashboard with Next.js: Data Exports

Deploy a reporting dashboard built with Next.js on Ample using the generated downloads 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Next.js: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the reporting dashboard-specific behavior as your application code.

## Representative Queries
- Host reporting dashboard with Next.js: data exports
- Where can I host Reporting dashboard built with Next.js?
- I need a scoped export format, artifact generation and authorized download procedure.

## Resource Requirements
- **Compute**
- **Postgres**
- **S3-compatible object storage**

## Infrastructure Requirements
### Compute
- **Status**: Verified  
- **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

### Postgres
- **Status**: Verified  
- **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

### S3-compatible Object Storage
- **Status**: Verified  
- **Summary**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## Framework
**Next.js**

## Workflow Steps
1. **Build and start**  
   Body: next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**  
   Body: The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Wire object storage**  
   Body: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.
4. **Deploy**  
   Body: 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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
5. **Verify**  
   Body: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   Command: ample logs  --kind build

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Next.js major versions are not verified.
- The reporting dashboard itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:  
  - **App server**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0  
  - **Managed PostgreSQL database**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Canary Run**: Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).
- **Observed At**: 2026-09-21T02:34:39Z  
- **Implementation Revision**: 1d28ae0-dirty (CLI 0.1.21)  
- **Expires At**: 2027-03-20T02:34:39Z  
  
## Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes by intent, stack and constraints**: POST /v1/catalog/search  
  Body: {"limit":5,"query":"Host reporting dashboard with Next.js: data exports"}
- **Prepare a side-effect-free deployment plan for an authorized project**: POST /v1/catalog/plan  
  Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:reporting-dashboard:next-js:data-exports","recipeRevision":"r1"}
- **Read the existing agent authentication setup**: GET /mcp/setup
- **Browse Reporting dashboard**: GET /v1/catalog/nodes/workload%3Areporting-dashboard
- **Browse Next.js**: GET /v1/catalog/nodes/stack%3Aframework-next-js
- **Browse Generated downloads**: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
- **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app