# Host admin dashboard with ASP.NET Core: tenant-scoped workspaces

Deploy an admin dashboard 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). The admin dashboard-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

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- An ASP.NET Core project that builds and starts with the documented commands (dotnet publish -c Release -o out in the builder, then dotnet <entry>.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

## Exact tested configuration

- build  
  dotnet publish -c Release -o out

- runtime  
  dotnet

- sizes  
  1vcpu-1gb

- start  
  ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll

- template  
  dotnet-10

## Steps

1.  **Build and start.** dotnet publish -c Release -o out in the builder, then dotnet <entry>.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 needs an answer first). Re-running with no change is a no-op.

```sh
   $ ample deploy . --name <app-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 <deployment_id> --kind build` then `--kind runtime`.

```sh
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

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

## Evidence

1. November 6, 2026 · canary run  
   ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o out in the builder, then dotnet <entry>.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).

2. November 5, 2026 · canary run  
   The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.

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

## What it doesn’t cover

- Verified on the dotnet-10 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the admin dashboard itself (your tenant model, membership and per-tenant authorization) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
