Host form collection with SvelteKit: relational workflow state

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

Representative Queries

• Host form collection with SvelteKit: relational workflow state
• Where can I host Form collection built with SvelteKit?
• I need a domain record schema, validation rules and concurrency behavior.

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: 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: tests/deploy-canaries/sveltekit-patterns

Success Checks

• App responds on its public URL
  • Kind: http_get
  • Path: /
  • Expect: ample canary sveltekit patterns
• 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 form collection 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: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Kind: canary_run
  • Summary: 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
  • Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
  • Expires At: 2027-03-19T03:31:44Z
• 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 (CLI e3181f5)
  • Expires At: 2027-03-19T02:16:51Z

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Form collection: GET /v1/catalog/nodes/workload%3Aform-collection
• Browse SvelteKit: GET /v1/catalog/nodes/stack%3Aframework-sveltekit
• Browse Transactional workflows: GET /v1/catalog/nodes/pattern%3Atransactional-workflows
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app