page:recipes:campaign site:sveltekit:relational content

Host campaign site with SvelteKit: Postgres-backed content

Deploy a campaign site built with SvelteKit on Ample using the relational records 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, and a published bucket serves public assets from the CDN host. Verified on SvelteKit: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the campaign site-specific behavior as your application code.

Representative Queries

• Host campaign site with SvelteKit: Postgres-backed content
• Where can I host Campaign site built with SvelteKit?
• I need a content schema, publishing workflow and cache behavior after content updates.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:cdn

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.
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.
3. CDN
   • Status: verified
   • Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

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)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, databases:read, buckets:read

Workflow Steps

1. Build and start
   • Body: 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
   • Body: The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Wire object storage
   • Body: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.
4. Deploy
   • Body: 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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
5. Verify
   • Body: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

Success Checks

• App responds on its public URL
  • Path: /
  • Expect: ample canary sveltekit patterns
• Relational-records self-test
  • Path: /p/relational-records
  • Expect: records=ok transitions=true isolation=true

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 campaign site itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
• 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.00
• Basis: size prices from pricing.toml (loaded by the API)
• Components:
  • App server
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: $5.00
  • Managed PostgreSQL database
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: $5.00
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

1. 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 relational-records and configuration-secrets.
   • Observed At: 2026-09-20T03:31:44Z
   • Expiration: 2027-03-19T03:31:44Z

2. 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
   • Expiration: 2027-03-19T02:16:51Z

Formats

• HTML Format
• Markdown Format
• JSON Format

Next Actions

1. Browse the catalog index

   • Method: GET
   • Relative Path: /v1/catalog

2. Search published recipes by intent, stack and constraints

   • Method: POST
   • Relative Path: /v1/catalog/search
   • Parameters: {"body":{"limit":5,"query":"Host campaign site with SvelteKit: Postgres-backed content"}}

3. Prepare a side-effect-free deployment plan for an authorized project

   • Method: POST
   • Relative Path: /v1/catalog/plan
   • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:campaign-site:sveltekit:relational-content","recipeRevision":"r1"}}

4. Read the existing agent authentication setup

   • Method: GET
   • Relative Path: /mcp/setup

5. Browse Campaign site

   • Method: GET
   • Relative Path: /v1/catalog/nodes/workload%3Acampaign-site

6. Browse SvelteKit

   • Method: GET
   • Relative Path: /v1/catalog/nodes/stack%3Aframework-sveltekit

7. Browse Relational records

   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Arelational-records

8. Browse Deploy web app

   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app