## Host partner portal with Next.js: application activity history

### Summary
Deploy a partner portal built with Next.js on Ample using the transactional workflows 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 Next.js: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the partner portal-specific behavior as your application code.

### Representative Queries
- Host partner portal with Next.js: application activity history  
- Where can I host Partner portal built with Next.js?  
- I need an application-owned event schema and tested history queries; not native platform audit logs.

### Resource Requirements
- **Compute**  
- **Postgres**

### Limitation
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 partner portal itself (your domain records, validation rules and concurrency policy) 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.

### 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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
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/transactional-workflows) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   Command: `ample logs  --kind build`

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Components**:
  - App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  - Managed PostgreSQL database: size 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.

### Evidence Summary
- **Canary Run**: Next.js pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.  
  Summary: An optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).
  Observed At: 2026-09-21T02:34:39Z
- **Canary Run**: The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation.  
  Observed At: 2026-09-20T01:54:51Z

### Next Actions
- **Action**: Browse the catalog index  
  - **Method**: GET  
  - **Relative Path**: /v1/catalog
- **Action**: Search published recipes by intent, stack and constraints  
  - **Method**: POST  
  - **Relative Path**: /v1/catalog/search  
- **Action**: Prepare a side-effect-free deployment plan for an authorized project  
  - **Method**: POST  
  - **Relative Path**: /v1/catalog/plan  
- **Action**: Read the existing agent authentication setup  
  - **Method**: GET  
  - **Relative Path**: /mcp/setup  
- **Action**: Browse Partner portal  
  - **Method**: GET  
  - **Relative Path**: /v1/catalog/nodes/workload%3Apartner-portal  
- **Action**: Browse Next.js  
  - **Method**: GET  
  - **Relative Path**: /v1/catalog/nodes/stack%3Aframework-next-js  
- **Action**: Browse Transactional workflows  
  - **Method**: GET  
  - **Relative Path**: /v1/catalog/nodes/pattern%3Atransactional-workflows  
- **Action**: Browse Deploy web app  
  - **Method**: GET  
  - **Relative Path**: /v1/catalog/nodes/intent%3Adeploy-web-app