Host client portal with Nuxt: tenant-scoped workspaces

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

Representative Queries

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

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

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

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
   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
   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) (/api/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

Examples

Nuxt pattern fixture

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

Success Checks

• App responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary nuxt patterns
• Multi-tenant-relational-data self-test
  • Kind: http_get
  • Path: /api/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 Nuxt major versions are not verified.
• The client 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.
• 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.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• 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.