# Host approval workflow with Next.js: CSV imports

Deploy a approval workflow built with Next.js on Ample using the bulk import staging 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: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the approval workflow-specific behavior as your application code.

### Representative Queries
- Host approval workflow with Next.js: CSV imports
- Where can I host Approval workflow built with Next.js?
- I need a domain CSV format, row validation, deduplication and an import recovery path.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

### Infrastructure Requirements
1. **Compute**  
   *Status*: verified  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   *[More Info](https://discover/primitive/compute)*

2. **Postgres**  
   *Status*: verified  
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.  
   *[More Info](https://discover/primitive/postgres)*

3. **S3-compatible object storage**  
   *Status*: verified  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.  
   *[More Info](https://discover/primitive/s3-compatible-object-storage)*

### Prerequisites
- A Next.js project that builds and starts with the documented commands (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

### Workflow Steps
1. **Build and start**  
   `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**  
   The fixture's module implements bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   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**  
   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.
   `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**  
   Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   `ample logs --kind build`

### Success Checks
- App responds on its public URL.  
  *[HTTP GET /]*  
  Expect: `ample canary next js patterns`.
- Bulk-import-staging self-test.  
  *[HTTP GET /p/bulk-import-staging]*  
  Expect: `imported=2 rejected=1 restart=ok`.

### 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 approval workflow itself (your import format, mapping and conflict rules) 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.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: $10.00  
- **Basis**: size prices from pricing.toml (loaded by the API)

| Component                        | Monthly Amount | Quantity | Size            |  
|----------------------------------|----------------|----------|-----------------|  
| app server                       | $5.00          | 1.0      | s-1vcpu-1gb     |  
| managed PostgreSQL database      | $5.00          | 1.0      | s-1vcpu-1gb     |

#### 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
- **Kind**: canary_run  
  Summary: Next.js pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
  Observed At: 2026-09-21T02:34:39Z

### Formats
- **HTML**: [Read More](/content/recipes/approval-workflow/next-js/csv-imports/index.html)  
- **Markdown**: [Markdown Format](/content/recipes/approval-workflow/next-js/csv-imports.md)
- **JSON**: [API Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aapproval-workflow%3Anext-js%3Acsv-imports)