## Host member portal with ASP.NET Core: tenant-scoped workspaces

Deploy a member portal built with ASP.NET Core 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 ASP.NET Core: 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 member portal-specific behavior as your application code.

### Representative Queries
- Host member portal with ASP.NET Core: tenant-scoped workspaces
- Where can I host Member portal built with ASP.NET Core?
- I need an explicit tenant model and application-enforced tenant isolation tests.

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

### 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.

### Prerequisites
- A ASP.NET Core project that builds and starts with the documented commands (`dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT)  
- 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**  
   `dotnet publish -c Release -o out` in the builder, then `dotnet .dll` on the dotnet-10 template with ASPNETCORE_URLS bound to PORT. 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 <NAME> --public`
4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks. On failure read `ample logs <your logs>`.  
   Command: `ample logs --kind build`

### Limitations
- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture; other sizes, templates and ASP.NET Core major versions are not verified.
- The member portal itself is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components:**
  - **App server**  
    - **Size:** s-1vcpu-1gb  
    - **Quantity:** 1.0  
    - **Monthly Amount:** 5.0
  - **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.

### Success Checks
- **App responds on its public URL:** Validate by performing an HTTP GET on `/`. Expect response: `ample canary asp net core patterns`.
- **Multi-tenant-relational-data self-test:** Validate by performing an HTTP GET on `/p/multi-tenant-relational-data`. Expect result: `tenant_isolation=ok`.

### Evidence Summary
- **Canary Run Summary:**  
  ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to PORT); 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-21T01:15:54Z  
  - **Implementation Revision:** 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)  
  - **Expires At:** 2027-03-20T01:15:54Z