Host member portal with Nuxt: tenant-scoped workspaces

Summary

Deploy a member portal built with Nuxt 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 Nuxt: 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 member portal-specific behavior as your application code.

Representative Queries

• Host member portal with Nuxt: tenant-scoped workspaces
• Where can I host Member portal built with Nuxt?
• I need an explicit tenant model and application-enforced tenant isolation tests.

Resource Requirements

• primitive:compute
• primitive: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.

Framework

Nuxt

Workload

Member portal

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

• A Nuxt project that builds and starts with the documented commands (nuxt build then node .output/server/index.mjs (reads HOST and 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
   Command: nuxt build then node .output/server/index.mjs (reads HOST and 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
   Command: ample deploy . --name --public. 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.
4. Verify
   Command: ample logs --kind build. Fetch the live URL and the pattern self-test route(s) (/api/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read ample logs --kind runtime then --kind build.

Examples

• Nuxt pattern fixture: Multi-pattern Nuxt app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL.
  Expected: ample canary nuxt patterns
• Multi-tenant-relational-data self-test.
  Expected: tenant_isolation=ok

Limitations

• Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Nuxt major versions are not verified.
• The member portal itself (your tenant model, membership and per-tenant authorization) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.0 (authoritative)
• Basis: size prices from pricing.toml (loaded by the API)...

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Member portal
6. Browse Nuxt
7. Browse Multi-tenant relational data
8. Browse Deploy web app