Host subscription content with SvelteKit: public product media

Summary

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

Representative Queries

• Host subscription content with SvelteKit: public product media
• Where can I host Subscription content built with SvelteKit?
• I need product-to-object mappings and a tested public media delivery path.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage
• 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. S3-compatible object storage
   Status: verified
   Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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

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 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
   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
   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
   Command: ample logs --kind build

Examples

• SvelteKit pattern fixture
  Description: Multi-pattern SvelteKit app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules. Source Reference: tests/deploy-canaries/sveltekit-patterns

Success Checks

1. Description: app responds on its public URL
   Kind: http_get
   Path: /
   Expect: ample canary sveltekit patterns

2. Description: public-media-library self-test
   Kind: http_get
   Path: /p/public-media-library
   Expect: a CDN URL whose content is served publicly

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 subscription content itself (your media processing, object layout and cache 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.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml

Components

1. App server
   Size: s-1vcpu-1gb
   Quantity: 1.0
   Monthly Amount: 5.0

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