# Host storefront with SvelteKit: relational catalog data

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

## Representative Queries
- Host storefront with SvelteKit: relational catalog data
- Where can I host Storefront built with SvelteKit?
- I need catalog tables, transactional update logic and application-level access boundaries.

## Resource Requirements
- **Compute**
- **Postgres**

## 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 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**  
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) (/p/transactional-workflows) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.  
`ample logs --kind build`

## Examples
- **SvelteKit pattern fixture**: Multi-pattern SvelteKit app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
1. **App responds on its public URL**  
   - kind: `http_get`  
   - path: `/`  
   - expect: `ample canary sveltekit patterns`

2. **Transactional-workflows self-test**  
   - kind: `http_get`  
   - path: `/p/transactional-workflows`  
   - expect: `tx=ok history=2 conflict=rejected`

## 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 storefront 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.00  
- **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.00  
  - Name: managed PostgreSQL database  
    Size: s-1vcpu-1gb  
    Quantity: 1.0  
    Monthly Amount: $5.00  
- **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

## Formats
- **HTML**: [ample.computer](/content/recipes/storefront/sveltekit/relational-catalog/index.html)  
- **Markdown**: [ample.computer](/content/recipes/storefront/sveltekit/relational-catalog.md)  
- **JSON**: [api.ample.computer](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Astorefront%3Asveltekit%3Arelational-catalog)