page:recipes:vendor portal:phoenix:tenant workspaces

Host vendor portal with Phoenix: tenant-scoped workspaces

Summary

Deploy a vendor portal built with Phoenix 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 Phoenix: 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 vendor portal-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

Prerequisites

Tested Configuration

Workflow Steps

  1. Build and start: mix deps.get, MIX_ENV=prod mix compile and mix release in the builder...
  2. Implement the pattern on PostgreSQL: The fixture's module implements multi-tenant relational data...
  3. Deploy: Run the synchronous deploy once and read the result...
  4. Verify: Fetch the live URL and the pattern self-test route(s)...

Success Checks

Limitations

Cost Estimate

Evidence Summary

  1. Canary run: Phoenix pattern fixture deployed on Ample...
  2. Canary run: The same Phoenix app deployed with a --release-command migration...

Last Verified At

2026-09-20T23:45:31Z