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

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

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

## Resource Requirements
- primitive:compute
- primitive:postgres

## Infrastructure Requirements
1. **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.

2. **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.

## 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)
- An Ample account token with servers:write, databases: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 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`

## Success Checks
1. App responds on its public URL  
   - Kind: http_get
   - Path: /  
   - Expect: ample canary next js patterns

2. Transactional-workflows self-test  
   - Kind: http_get
   - Path: /p/transactional-workflows  
   - Expect: tx=ok history=2 conflict=rejected

## 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 client 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.

## Cost Estimate
- Currency: USD  
- Monthly Amount: 10.0  
- Authoritative: true  
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- 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. Buckets are allocation-priced per quota and not included.

## Next Actions
1. **Browse the catalog index**  
   - Action ID: browse-catalog  
   - Operation ID: catalog_index
   - Method: GET
   - Relative Path: /v1/catalog

2. **Search published recipes by intent, stack and constraints**  
   - Action ID: search-recipes  
   - Operation ID: search_recipes
   - Method: POST
   - Relative Path: /v1/catalog/search
   - Parameters: 
     - Body: 
       - Limit: 5  
       - Query: Host client portal with Next.js: application activity history

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Action ID: plan:page:recipes:client-portal:next-js:activity-history  
   - Operation ID: plan_deployment
   - Method: POST
   - Relative Path: /v1/catalog/plan
   - Parameters:
     - Body:
       - Inputs: {}
       - Project ID: ""
       - Recipe ID: page:recipes:client-portal:next-js:activity-history
       - Recipe Revision: r1

4. **Read the existing agent authentication setup**  
   - Action ID: auth-setup  
   - Operation ID: existing_auth_setup
   - Method: GET
   - Relative Path: /mcp/setup

5. **Browse Client portal**  
   - Action ID: browse:workload:client-portal  
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/workload%3Aclient-portal