Host member portal with SvelteKit: application activity history

Summary

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

Representative Queries

• Host member portal with SvelteKit: application activity history
• Where can I host Member portal built with SvelteKit?
• I need an application-owned event schema and tested history queries; not native platform audit logs.

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.

Prerequisites

1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. 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: 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) from the example; then run your own checks.
   • Command: ample logs --kind build

Examples

• SvelteKit pattern fixture: Multi-pattern SvelteKit app whose transactional workflows module was checked live.
  • 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 member portal itself is application code was not separately tested.

Cost Estimate

• Monthly Amount: 10.0 USD
• Components:
  • App server: 5.0 USD
  • Managed PostgreSQL database: 5.0 USD

Evidence Summary

• Canary Run: 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

For more details, refer to the documentation.