# Host reporting dashboard with SvelteKit: relational workflow state

Deploy a reporting dashboard built with SvelteKit on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the reporting dashboard-specific behavior as your application code.

## Representative Queries
- Host reporting dashboard with SvelteKit: relational workflow state
- Where can I host Reporting dashboard built with SvelteKit?
- I need a domain record schema, validation rules and concurrency behavior.

## Resource Requirements
- primitive:compute
- primitive:postgres

## Infrastructure Requirements
1. **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.  
   - **Canonical Path:** /discover/primitive/compute

2. **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.  
   - **Canonical Path:** /discover/primitive/postgres

## 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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). 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/transactional-workflows) 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 reporting dashboard itself (your domain records, validation rules and concurrency policy) 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.

## Evidence Summary
- **Canary Run:** SvelteKit pattern fixture deployed on Ample (vite build with @sveltejs/adapter-node then node build on the node-22 template); checks passed for transactional-workflows and configuration-secrets. Pattern proof: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Observed at: 2026-09-20T03:31:44Z.

## Next Actions
1. **Browse the catalog index**  
   - Method: GET  
   - Relative Path: /v1/catalog

2. **Search published recipes by intent, stack and constraints**  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
   - Parameters: {"body":{"limit":5,"query":"Host reporting dashboard with SvelteKit: relational workflow state"}}

3. **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:reporting-dashboard:sveltekit:relational-workflow","recipeRevision":"r1"}}

4. **Read the existing agent authentication setup**  
   - Method: GET  
   - Relative Path: /mcp/setup

5. **Browse Reporting dashboard**  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/workload%3Areporting-dashboard

6. **Browse SvelteKit**  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-sveltekit

7. **Browse Transactional workflows**  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows

8. **Browse Deploy web app**  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app