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

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

## Representative Queries
- Host client portal with ASP.NET Core: tenant-scoped workspaces
- Where can I host Client 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.

## 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 --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
- **ASP.NET Core pattern fixture**: Multi-pattern ASP.NET Core app whose multi-tenant relational data module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

## Success Checks
- app responds on its public URL  
  Kind: HTTP GET  
  Path: `/`  
  Expect: `ample canary asp net core patterns`:  
- multi-tenant-relational-data self-test  
  Kind: HTTP GET  
  Path: `/p/multi-tenant-relational-data`  
  Expect: `tenant_isolation=ok`

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

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **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.

## Evidence Summary
- **Canary Run**: 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.

## Next Actions
- **Browse the catalog index**  
- **Search published recipes by intent, stack and constraints**  
- **Prepare a side-effect-free deployment plan for an authorized project**  
- **Read the existing agent authentication setup**  
- **Browse Client portal**  
- **Browse ASP.NET Core**  
- **Browse Multi-tenant relational data**  
- **Browse Deploy web app**