Host vendor portal with Phoenix: tenant-scoped workspaces · Ample Computer

Host vendor portal with Phoenix: tenant-scoped workspaces

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). The vendor portal-specific behavior (your tenant model, membership and per-tenant authorization) is your application code on that verified basis.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

build MIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite

install mix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod

runtime elixir

sizes - 1vcpu-1gb

start PHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start

template elixir-1.18

Steps

  1. Build and start. mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs. The server must bind 0.0.0.0 on PORT.

  2. Implement the pattern on PostgreSQL. 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. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

   $ ample deploy . --name <app-name> --public
  1. Verify. 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 <deployment_id> --kind build then --kind runtime.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL· http get/ → “ample canary phoenix patterns”
✓ multi-tenant-relational-data self-test· http get/p/multi-tenant-relational-data → “tenant_isolation=ok”

Evidence

  1. November 6, 2026 · canary run

    Phoenix pattern fixture deployed on Ample (mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs); checks passed for multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok).

  2. November 6, 2026 · canary run

    The same Phoenix app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover