page:recipes:campaign site:sveltekit:public media

Host campaign site with SvelteKit: object-stored public media

Deploy a campaign site built with SvelteKit on Ample using the public media library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on SvelteKit: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the campaign site-specific behavior as your application code.

Representative Queries

• Host campaign site with SvelteKit: object-stored public media
• Where can I host Campaign site built with SvelteKit?
• I need an object layout, public asset URL policy and CDN delivery configuration.

Resource Requirements

• Compute
• Postgres
• S3-compatible object storage
• CDN

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.
3. S3-Compatible Object Storage
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. CDN
   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 and a second, published bucket for public assets (CDN_*)
• An Ample account token with servers:write, databases:read, buckets: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 public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Wire object storage
   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
   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.
5. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Example

SvelteKit pattern fixture
Multi-pattern SvelteKit app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Cost Estimate

• Estimated Monthly Cost: $10.00 USD
  • App server: $5.00
  • Managed PostgreSQL database: $5.00
• 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.

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 media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.

This cleaned content provides the main elements needed to understand the deployment of a campaign site using SvelteKit.