# Host knowledge base with Next.js: public-site delivery

Deploy a knowledge base built with Next.js on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Next.js: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the knowledge base-specific behavior as your application code.

## Representative Queries
- Host knowledge base with Next.js: public-site delivery
- Where can I host Knowledge base built with Next.js?
- I need an explicit origin-to-CDN delivery path and a tested public content build.

## 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 bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, 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. The server must bind 0.0.0.0 on PORT.
2. **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. Publish only the bucket that serves public assets and reference its CDN URL.
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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...`
4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) 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
- **App responds on its public URL**  
  Kind: http_get  
  Path: /  
  Expect: ample canary next js patterns
- **Versioned-static-assets self-test**  
  Kind: http_get  
  Path: /p/versioned-static-assets  
  Expect: a CDN URL whose content is served publicly

## 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 knowledge base itself (your site content and build) 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 5.0
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components:**
  - **Name:** app server
  - **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.

## Evidence Summary
- **Kind:** canary_run
  - **Summary:** Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for versioned-static-assets and configuration-secrets. Pattern proof: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.
  - **Observed At:** 2026-09-21T02:34:39Z
  - **Implementation Revision:** 1d28ae0-dirty (CLI 0.1.21)
  - **Expires At:** 2027-03-20T02:34:39Z
- **Kind:** canary_run
  - **Summary:** 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
  - **Implementation Revision:** 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)
  - **Expires At:** 2027-03-19T01:54:51Z

## Next Actions
- **Action:** Browse the catalog index  
- **Action:** Search published recipes by intent, stack and constraints  
- **Action:** Prepare a side-effect-free deployment plan for an authorized project  
- **Action:** Read the existing agent authentication setup  
- **Action:** Browse Knowledge base  
- **Action:** Browse Next.js  
- **Action:** Browse Public web service  
- **Action:** Browse Deploy web app