Host Marketplace with Next.js: Inventory Imports

Deploy a marketplace 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 marketplace-specific behavior as your application code.

Representative Queries

• Host marketplace with Next.js: inventory imports
• Where can I host Marketplace built with Next.js?
• I need an inventory import contract, staging objects, and row-level error handling.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request.
• 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.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials.

Framework

Next.js

Workload

Marketplace

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. A bucket created with ample bucket create with its credentials passed as encrypted S3_* environment variables
4. An Ample account token with servers:write, databases:read, buckets: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: next build then next start -H 0.0.0.0 -p $PORT on the node-22 template.
2. Implement the Pattern on PostgreSQL: The fixture's module implements bulk import staging.
3. Wire Object Storage: Create the bucket(s), then pass endpoint, region, bucket, and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and the pattern self-test route(s).

Examples

• Next.js Pattern Fixture: Multi-pattern Next.js app whose bulk import staging module was checked live.

Limitations

• Verified on the node-22 template at s-1vcpu-1gb; other sizes, templates, and Next.js major versions are not verified.
• Managed PostgreSQL 16 only; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• 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

Evidence Summary

• Kind: canary_run
• Summary: Next.js pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.