### Host admin dashboard with Next.js: tenant-scoped workspaces

Deploy a admin dashboard 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). Not separately tested: your tenant model, membership and per-tenant authorization; treat the admin dashboard-specific behavior as your application code.

#### Representative Queries
- Host admin dashboard with Next.js: tenant-scoped workspaces
- Where can I host Admin dashboard built with Next.js?
- I need an explicit tenant model and application-enforced tenant isolation tests.

#### Resource Requirements
- **Compute**
- **Postgres**

#### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

#### 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)
- An Ample account token with servers:write, databases: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 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 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/multi-tenant-relational-data) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`. `ample logs --kind build`

#### Success Checks
- App responds on its public URL. (Path: `/`, Expect: `ample canary next js patterns`)
- Multi-tenant-relational-data self-test. (Path: `/p/multi-tenant-relational-data`, Expect: `tenant_isolation=ok`)

#### 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 admin dashboard itself (your tenant model, membership and per-tenant authorization) 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) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:  
  - **App server**: size `s-1vcpu-1gb`, quantity 1.0, monthly amount 5.0  
  - **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**: Next.js pattern fixture deployed on Ample; checks passed for multi-tenant-relational-data and configuration-secrets.
   - Observed at: 2026-09-21T02:34:39Z
   - Implementation revision: 1d28ae0-dirty (CLI 0.1.21)
   - Expires at: 2027-03-20T02:34:39Z
2. **Canary Run**: 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
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**
- **[Search published recipes by intent, stack and constraints](https://api.ample.computer/v1/catalog/search)**
- **[Prepare a side-effect-free deployment plan for an authorized project](https://api.ample.computer/v1/catalog/plan)**
- **[Read the existing agent authentication setup](https://api.ample.com/computer/mcp/setup)**
- **[Browse Admin dashboard](https://api.ample.com/computer/catalog/nodes/workload%3Aadmin-dashboard)**
- **[Browse Next.js](https://api.ample.com/computer/catalog/nodes/stack%3Aframework-next-js)**
- **[Browse Multi-tenant relational data](https://api.ample.com/computer/catalog/nodes/pattern%3Amulti-tenant-relational-data)**
- **[Browse Deploy web app](https://api.ample.com/computer/catalog/nodes/intent%3Adeploy-web-app)**