## Host vendor portal with SvelteKit: tenant-scoped workspaces

### Summary
Deploy a vendor portal built with SvelteKit 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 SvelteKit: 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 vendor portal-specific behavior as your application code.

### Representative Queries
- Host vendor portal with SvelteKit: tenant-scoped workspaces
- Where can I host Vendor portal built with SvelteKit?
- 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.

### Framework
SvelteKit

### Workload
Vendor portal

### Release Status
published

### Support Status
verified

### Execution Status
ready

### Prerequisites
1. A SvelteKit project that builds and starts with the documented commands (vite build with @sveltejs/adapter-node then node build on the node-22 template)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with servers:write, databases:read

### Tested Configuration
- **Template:** node-22  
- **Runtime:** node  
- **Size:** s-1vcpu-1gb  
- **Install:** npm install  
- **Build:** npm run build --if-present  
- **Start:** npm run start

### Workflow Steps
1. **Build and start**  
   vite build with @sveltejs/adapter-node then node build 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.
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`.

### Examples
- **SvelteKit pattern fixture**  
  Multi-pattern SvelteKit 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  
  - Kind: http_get  
  - Path: /  
  - Expect: ample canary sveltekit patterns  
- Multi-tenant-relational-data self-test  
  - Kind: http_get  
  - 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 SvelteKit major versions are not verified.
- The vendor 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  
- **Basis:** Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components:**  
  - Name: app server  
    - Size: s-1vcpu-1gb  
    - Quantity: 1.0  
    - Monthly Amount: 5.0  
  - Name: 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
- **Kind:** canary_run  
  - Summary: SvelteKit pattern fixture deployed on Ample (vite build with @sveltejs/adapter-node then node build 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).  
  - Observed At: 2026-09-20T03:31:44Z  
  - Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)  
  - Expires At: 2027-03-19T03:31:44Z
  - Scope:  
    - Checks: /p/multi-tenant-relational-data  
    - Pattern: pattern:multi-tenant-relational-data  
    - Template: node-22

### Last Verified At
2026-09-20T03:31:44Z

### Formats
- **HTML:** https://ample.computer/recipes/vendor-portal/sveltekit/tenant-workspaces  
- **Markdown:** https://ample.computer/recipes/vendor-portal/sveltekit/tenant-workspaces.md  
- **JSON:** https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Avendor-portal%3Asveltekit%3Atenant-workspaces
