### Host client portal with Phoenix: tenant-scoped workspaces

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

#### Summary
- **Family:** Workload recipe  
- **Release Status:** published  
- **Support Status:** verified  
- **Execution Status:** ready

#### Representative Queries  
- Host client portal with Phoenix: tenant-scoped workspaces  
- Where can I host Client portal built with Phoenix?  
- I need an explicit tenant model and application-enforced tenant isolation tests.

#### Resource Requirements
- **Compute**  
- **Postgres**

#### 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
- A Phoenix project that builds and starts with the documented commands (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).
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- An Ample account token with servers:write, databases:read.

#### Workflow 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 blocked). Re-running with no change is a no-op.
   - Command: `ample deploy . --name  --public`
4. **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  --kind build` then `--kind runtime`.
   - Command: `ample logs  --kind build`

#### Examples
- **Phoenix pattern fixture**  
   - Multi-pattern Phoenix app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
   
#### Success Checks
1. App responds on its public URL  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary phoenix patterns
2. Multi-tenant-relational-data self-test  
   - Kind: http_get  
   - Path: /p/multi-tenant-relational-data  
   - Expect: tenant_isolation=ok

#### Limitations
- Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Phoenix major versions are not verified.
- The client portal itself (your tenant model, membership and per-tenant authorization) 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.

#### Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Authoritative:** true  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **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.

#### Evidence Summary
1.  **Canary run**  
    - Summary: 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).
    - Observed At: 2026-09-20T23:45:31Z  
    - Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)  
    - Expires At: 2027-03-19T23:45:31Z  
    - Scope:  
      - Checks: [/p/multi-tenant-relational-data]  
      - Pattern: pattern:multi-tenant-relational-data  
      - Template: elixir-1.18 
2. **Canary run**  
    - Summary: The same Phoenix app deployed with a --release-command migration; the marker it created was readable after activation. 
    - Observed At: 2026-09-20T23:45:31Z  
    - Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)  
    - Expires At: 2027-03-19T23:45:31Z  
    - Scope:  
      - Pattern: pattern:multi-tenant-relational-data

#### Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

#### Formats
- [HTML](/content/recipes/client-portal/phoenix/tenant-workspaces/index.html)
- [Markdown](/content/recipes/client-portal/phoenix/tenant-workspaces.md)
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aclient-portal%3Aphoenix%3Atenant-workspaces)

#### Next Actions
1. **Browse the catalog index**  
   - Operation Id: catalog_index  
   - Method: GET  
   - Relative Path: /v1/catalog  
   - Requires Authentication: false  
   - Requires Approval: false
2. **Search published recipes by intent, stack and constraints**  
   - Operation Id: search_recipes  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
   - Parameters:  
     - Body:  
       - Limit: 5  
       - Query: Host client portal with Phoenix: tenant-scoped workspaces
   - Requires Authentication: false  
   - Requires Approval: false
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Operation Id: plan_deployment  
   - Method: POST  
   - Relative Path: /v1/catalog/plan  
   - Requires Authentication: true  
   - Requires Approval: false
4. **Read the existing agent authentication setup**  
   - Operation Id: existing_auth_setup  
   - Method: GET  
   - Relative Path: /mcp/setup  
   - Requires Authentication: false  
   - Requires Approval: false
5. **Browse Client portal**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/workload%3Aclient-portal  
   - Node Id: workload:client-portal  
   - Requires Authentication: false  
   - Requires Approval: false
6. **Browse Phoenix**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-phoenix  
   - Node Id: stack:framework-phoenix  
   - Requires Authentication: false  
   - Requires Approval: false
7. **Browse Multi-tenant relational data**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data  
   - Node Id: pattern:multi-tenant-relational-data  
   - Requires Authentication: false  
   - Requires Approval: false
8. **Browse Deploy web app**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app  
   - Node Id: intent:deploy-web-app  
   - Requires Authentication: false  
   - Requires Approval: false