## Host Order Tracking with SvelteKit: Relational Catalog Data

Deploy an order tracking built with SvelteKit on Ample using the transactional workflows pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and 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 order tracking-specific behavior as your application code.

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

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

### Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **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
- Order tracking

### Release Status
- published

### Support Status
- verified

### 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

### Example 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.

### Success Checks
- app responds on its public URL
- transactional-workflows self-test

### 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 order tracking itself (your domain records, validation rules, and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- **Monthly Amount**: 10.0 USD
- **Components**:
   - app server: s-1vcpu-1gb - 5.0 USD
   - managed PostgreSQL database: s-1vcpu-1gb - 5.0 USD

### Next Actions
- Browse the catalog index
- Search published recipes by intent, stack, and constraints
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse Order tracking
- Browse SvelteKit
- Browse Transactional workflows
- Browse Deploy web app