# Host company website with Next.js: public-site delivery

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

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

## Resource Requirements
- Compute
- CDN

## Infrastructure Requirements
1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   [More details](/content/discover/primitive/compute/index.html)

2. **CDN**  
   The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.  
   [More details](/content/discover/primitive/cdn/index.html)

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

## 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.
   ```bash
   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`.
   ```bash
   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 company website 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.

## Cost Estimate
Monthly Amount: 5.0 USD
Components:
- App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0

## Evidence Summary
### Canary Run
1. 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.

### Unknowns
- Region availability is unknown until a verified region fact is recorded
- Compliance attestations are unknown; none are claimed.

## Formats
- [HTML Format](/content/recipes/company-website/next-js/public-site/index.html)
- [Markdown Format](/content/recipes/company-website/next-js/public-site.md)  
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Acompany-website%3Anext-js%3Apublic-site)

## Next Actions
- **Browse the catalog index**  
  [GET /v1/catalog](https://api.ample.computer/v1/catalog)

- **Search published recipes by intent, stack and constraints**  
  [POST /v1/catalog/search](https://api.ample.computer/v1/catalog/search)
- **Prepare a side-effect-free deployment plan for an authorized project**  
  [POST /v1/catalog/plan](https://api.ample.comcomputer/v1/catalog/plan)