# Host vendor portal with SvelteKit: application activity history

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

## Representative Queries
- Host vendor portal with SvelteKit: application activity history
- Where can I host Vendor 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
### 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.

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

## Framework
SvelteKit

## Workload
Vendor portal

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

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

## Input Schema
```json
{
  "additionalProperties": false,
  "properties": {
    "env": {
      "description": "Encrypted environment variables (bucket credentials, secrets)",
      "items": {
        "pattern": "^[A-Z][A-Z0-9_]*=.*$",
        "type": "string"
      },
      "maxItems": 50,
      "type": "array"
    },
    "name": {
      "description": "App name",
      "maxLength": 63,
      "minLength": 1,
      "pattern": "^[a-z0-9-]+$",
      "type": "string"
    },
    "path": {
      "description": "Project directory or ample.toml service",
      "maxLength": 512,
      "minLength": 1,
      "type": "string"
    },
    "release_command": {
      "description": "Migration command run before activation",
      "maxLength": 512,
      "type": "string"
    }
  },
  "required": ["name", "path"],
  "type": "object"
}
```

## 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 <app_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 <app_name> --kind build` then `--kind runtime`.
   ```
   ample logs <app_name> --kind build
   ```

## Examples
### SvelteKit pattern fixture
- **Description:** 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 vendor 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.
- 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 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
1. **Kind:** canary_run  
   - **Summary:** SvelteKit pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
   - **Observed At:** 2026-09-20T03:31:44Z  
   - **Implementation Revision:** 03b6402b1b3e19178985f08ea4033804521d85d4-dirty  
   - **Expires At:** 2027-03-19T03:31:44Z
   - **Scope:** Checks: [/p/transactional-workflows], Pattern: pattern:transactional-workflows, Template: node-22

2. **Kind:** canary_run  
   - **Summary:** The same SvelteKit app deployed with a --release-command migration; the marker it created was readable after activation.
   - **Observed At:** 2026-09-20T02:16:51Z  
   - **Implementation Revision:** 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty  
   - **Expires At:** 2027-03-19T02:16:51Z  
   - **Scope:** Pattern: pattern:transactional-workflows

## Last Verified At
2026-09-20T03:31:44Z

## MCP Binding
- **Registry Ref:** mcp:ample_deploy  
- **Tool Name:** ample_deploy  
- **Schema Hash:** 876465fce906da0c224d62961d3343064108ebe30af80cf1b87094974e948853  
- **Observed At:** 2026-09-21T03:19:59.461917+00:00  
- **Implementation Revision:** 49962bcade4f  
- **Required Scopes:** servers:write, databases:read  
- **Binding State:** current

## Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.
