page:recipes:admin dashboard:sveltekit:tenant workspaces

Host admin dashboard with SvelteKit: tenant-scoped workspaces

Deploy an admin dashboard built with SvelteKit on Ample using the multi-tenant relational data 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: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the admin dashboard-specific behavior as your application code.

Representative Queries

Resource Requirements

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.

Prerequisites

Tested Configuration

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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

  3. Deploy
    Command: ample deploy . --name --public 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.

  4. Verify
    Command: ample logs --kind build
    Body: Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Examples

SvelteKit pattern fixture

Success Checks

  1. app responds on its public URL

    • Kind: http_get
    • Path: /
    • Expect: ample canary sveltekit patterns
  2. multi-tenant-relational-data self-test

    • Kind: http_get
    • Path: /p/multi-tenant-relational-data
    • Expect: tenant_isolation=ok

Limitations

Cost Estimate

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

Evidence Summary

Next Actions