Host vendor portal with Next.js: tenant-scoped workspaces · Ample Computer

Host vendor portal with Next.js: tenant-scoped workspaces

Deploy a vendor portal built with Next.js on Ample using the multi-tenant relational data 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: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). The vendor portal-specific behavior (your tenant model, membership and per-tenant authorization) is your application code on that verified basis.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). 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 needs an answer first). Re-running with no change is a no-op.

    $ ample deploy . --name <app-name> --public  
    
  4. Verify.
    Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.

    $ ample logs <deployment_id> --kind build  
    

How it was checked

✓ app responds on its public URL· http get/ → “ample canary next js patterns”
✓ multi-tenant-relational-data self-test· http get/p/multi-tenant-relational-data → “tenant_isolation=ok”

Evidence

  1. November 5, 2026 · canary run
    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 multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok).

  2. November 6, 2026 · canary run
    The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover