page:recipes:member portal:next js:public profiles

Host member portal with Next.js: public profile assets

Deploy a member portal built with Next.js on Ample using the public image delivery 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host.

Summary

Verified on Next.js: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the member portal-specific behavior as your application code.

Representative Queries

• Host member portal with Next.js: public profile assets
• Where can I host Member portal built with Next.js?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage
• primitive:cdn

Infrastructure Requirements

1. Compute

   • Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
   • Status: verified

2. Postgres

   • 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.
   • Status: verified

3. S3-compatible object storage

   • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
   • Status: verified

4. CDN

   • Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.
   • Status: verified

Configuration

• Framework: Next.js
• Workload: Member portal
• Release Status: published
• Support Status: verified
• Execution Status: ready

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)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
• An Ample account token with servers:write, databases:read, 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. Implement the pattern on PostgreSQL

   • The fixture's module implements public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. 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.

4. 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=...

5. Verify

   • Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

Examples

• Next.js pattern fixture
  Description: Multi-pattern Next.js app whose public image delivery module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  Source Ref: tests/deploy-canaries/next-js-patterns

Success Checks

1. app responds on its public URL

   • Kind: http_get
   • Path: /
   • Expect: ample canary next js patterns

2. public-media-library self-test

   • Kind: http_get
   • Path: /p/public-media-library
   • Expect: a CDN URL whose content is served publicly

3. private-document-library self-test

   • Kind: http_get
   • Path: /p/private-document-library
   • Expect: private=ok (with ?role=owner; 401 without, 403 for viewer)

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 member portal itself (your image processing and profile-media rules) 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

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API)
• Components:
  1. app server
     • Size: s-1vcpu-1gb
     • Quantity: 1.0
     • Monthly Amount: 5.0
  2. 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.

Evidence Summary

1. Canary Run

   • Summary: Next.js pattern fixture deployed on Ample; checks passed for public-media-library, private-document-library and configuration-secrets.
   • Observed At: 2026-09-21T02:34:39Z
   • Implementation Revision: 1d28ae0-dirty

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

Next Actions

• Browse the catalog index (GET /v1/catalog)
• Search published recipes by intent, stack and constraints (POST /v1/catalog/search)
• Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan)
• Read the existing agent authentication setup (GET /mcp/setup)
• Browse Member portal (GET /v1/catalog/nodes/workload%3Amember-portal)
• Browse Next.js (GET /v1/catalog/nodes/stack%3Aframework-next-js)
• Browse Public image delivery (GET /v1/catalog/nodes/pattern%3Apublic-image-delivery)
• Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app)