# Host subscription content with Next.js: relational catalog data

## Summary
Deploy a subscription content 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 subscription content-specific behavior as your application code.

## Representative Queries
- Host subscription content with Next.js: relational catalog data
- Where can I host Subscription content built with Next.js?
- I need catalog tables, transactional update logic and application-level access boundaries.

## Resource Requirements
- **Primitive:** compute
- **Primitive:** postgres

## Framework
Next.js

## Workload
Subscription content

## Release Status
published

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

- **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 subscription content itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

## Next Actions
- **Browse the catalog index**
- **Search published recipes by intent, stack and constraints**
- **Prepare a side-effect-free deployment plan for an authorized project**
- **Read the existing agent authentication setup**
- **Browse Subscription content**
- **Browse Next.js**
- **Browse Transactional workflows**
- **Browse Deploy web app**

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