# Host Client Portal with SvelteKit: Tenant-Scoped Workspaces

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

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

## Resource Requirements
- **Primitive:** Compute
- **Primitive:** Postgres

## Infrastructure Requirements
1. **Primitive: Compute**  
   _Status:_ Verified  
   _Summary:_ Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. **Primitive: Postgres**  
   _Status:_ Verified  
   _Summary:_ 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 SvelteKit project that builds and starts with the documented commands (vite build with @sveltejs/adapter-node then node build 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**  
   _Body:_ 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**  
   _Body:_ 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**  
   _Body:_ 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.  
   _Command:_ ample deploy . --name --public

4. **Verify**  
   _Body:_ 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`.  
   _Command:_ ample logs --kind build

## Examples
- **Title:** SvelteKit pattern fixture  
  _Description:_ Multi-pattern SvelteKit app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  _Source Ref:_ tests/deploy-canaries/sveltekit-patterns

## Success Checks
1. _Description:_ app responds on its public URL  
   _Kind:_ http_get  
   _Path:_ /  
   _Expect:_ ample canary sveltekit patterns

2. _Description:_ 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 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  
- **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
- **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  
  _Expires At:_ 2027-03-19T03:31:44Z

## Next Actions
1. **Action ID:** browse-catalog  
   _Label:_ Browse the catalog index  
   _Method:_ GET  
   _Relative Path:_ /v1/catalog

2. **Action ID:** search-recipes  
   _Label:_ Search published recipes by intent, stack and constraints  
   _Method:_ POST  
   _Relative Path:_ /v1/catalog/search  
   _Parameters:_ {"body":{"limit":5,"query":"Host client portal with SvelteKit: tenant-scoped workspaces"}}

3. **Action ID:** plan:page:recipes:client-portal:sveltekit:tenant-workspaces  
   _Label:_ Prepare a side-effect-free deployment plan for an authorized project  
   _Method:_ POST  
   _Relative Path:_ /v1/catalog/plan  
   _Parameters:_ {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:client-portal:sveltekit:tenant-workspaces","recipeRevision":"r1"}}