Host client portal with SvelteKit: public profile assets

Deploy a client portal built with SvelteKit on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the client portal-specific behavior as your application code.

Representative Queries

• Host client portal with SvelteKit: public profile assets
• Where can I host Client portal built with SvelteKit?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage
• primitive:cdn

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• 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.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
• CDN: 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: 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 image delivery: public objects in a published bucket served from the CDN URL.
3. Wire object storage: Create the bucket(s) and pass endpoint, region, bucket, and keys as --env values. Use path-style addressing.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and the pattern self-test route(s).

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 client portal itself is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • app server: s-1vcpu-1gb - $5.00
  • managed PostgreSQL database: s-1vcpu-1gb - $5.00