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

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

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

### Workload
- Partner portal

### Execution Status
- Ready

### 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**: 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.
   - Command: `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`.
   - Command: `ample logs  --kind build`

### 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 partner 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
- **Monthly Amount**: $10.00
   - **App server**: 1.0 x $5.00 (size: s-1vcpu-1gb)
   - **Managed PostgreSQL database**: 1.0 x $5.00 (size: s-1vcpu-1gb)

### Evidence 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).

### Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes by intent**: POST /v1/catalog/search 
- **Prepare a side-effect-free deployment plan**: POST /v1/catalog/plan
- **Read existing agent authentication setup**: GET /mcp/setup