# Host client portal with SvelteKit: application activity history

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

## Representative Queries
- Host client portal with SvelteKit: application activity history
- Where can I host Client portal built with SvelteKit?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

## 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.
   - [More Info](/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.  
   - [More Info](/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

## Tested Configuration
- **Template**: node-22
- **Runtime**: node
- **Size**: s-1vcpu-1gb
- **Install**: npm install
- **Build**: npm run build --if-present
- **Start**: npm run start

## 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.  
   Command: `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`.  
   Command: `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.  
  Source Ref: `tests/deploy-canaries/sveltekit-patterns`

## 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 client portal 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
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml  
  (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:
  - **App server**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  - **Managed PostgreSQL database**: 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
1. **Canary Run**  
   - **Summary**: SvelteKit pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
   - **Observed At**: 2026-09-20T03:31:44Z
   - **Expires At**: 2027-03-19T03:31:44Z

## Next Actions
- **Browse the catalog index**  
  - Operation: GET  
  - Relative Path: /v1/catalog
- **Search published recipes by intent, stack and constraints**  
  - Operation: POST  
  - Relative Path: /v1/catalog/search  
  - Parameters: {"body":{"limit":5,"query":"Host client portal with SvelteKit: application activity history"}}
- **Prepare a side-effect-free deployment plan for an authorized project**  
  - Operation: POST  
  - Relative Path: /v1/catalog/plan  
  - Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:client-portal:sveltekit:activity-history","recipeRevision":"r1"}}
- **Read the existing agent authentication setup**  
  - Operation: GET  
  - Relative Path: /mcp/setup
- **Browse Client portal**  
  - Operation: GET  
  - Relative Path: /v1/catalog/nodes/workload%3Aclient-portal
- **Browse SvelteKit**  
  - Operation: GET  
  - Relative Path: /v1/catalog/nodes/stack%3Aframework-sveltekit
- **Browse Transactional workflows**  
  - Operation: GET  
  - Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows
- **Browse Deploy web app**  
  - Operation: GET  
  - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app