--- title: "How to host an admin dashboard built with ASP.NET Core on Ample: tenant-scoped workspaces" description: "Deploy an admin dashboard built with ASP.NET Core on Ample using the multi-tenant relational data pattern." canonical_url: "https://ample.computer/recipes/admin-dashboard/asp-net-core/tenant-workspaces" last_updated: "2026-11-06" --- # How to host an admin dashboard built with ASP.NET Core on Ample: 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. ## Infrastructure requirements - [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.) - [Postgres](/discover/primitive/postgres): verified (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.) ## Prerequisites - An 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 ## Exact tested configuration - template: `dotnet-10` - runtime: `dotnet` - size: `s-1vcpu-1gb` - build: `dotnet publish -c Release -o out` - start: `ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll` ## 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 needs an answer first). Re-running with no change is a no-op. ``` 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`. ``` ample logs --kind build ``` ## Tested examples - **ASP.NET Core pattern fixture** (tests/deploy-canaries/asp-net-core-patterns): 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 (`/` on the live URL, expect ample canary asp net core patterns) - multi-tenant-relational-data self-test (`/p/multi-tenant-relational-data` on the live URL, expect tenant_isolation=ok) ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision 4558e9477d094f5b47da324b98672824b61ba91b). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-11-06T00:41:08Z at revision `7360fc06ef21`: 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). (expires 2027-05-05T00:41:08Z) - canary_run on 2026-11-05T22:38:23Z at revision `da3e37255e5a`: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation. (expires 2027-05-04T22:38:23Z) Last verified: 2026-11-06T00:41:08Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `0802c329be823fa0` observed 2026-11-06T06:16:17.558478534+00:00 at revision `4558e9477d09`, binding state `current`, required scopes: servers:write, databases:read. ## Input schema ```json { "additionalProperties": false, "properties": { "env": { "description": "Encrypted environment variables (bucket credentials, secrets)", "items": { "pattern": "^[A-Z][A-Z0-9_]*=.*$", "type": "string" }, "maxItems": 50, "type": "array" }, "name": { "description": "App name", "maxLength": 63, "minLength": 1, "pattern": "^[a-z0-9-]+$", "type": "string" }, "path": { "description": "Project directory or ample.toml service", "maxLength": 512, "minLength": 1, "type": "string" }, "release_command": { "description": "Migration command run before activation", "maxLength": 512, "type": "string" } }, "required": [ "name", "path" ], "type": "object" } ``` ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse Admin dashboard (GET /v1/catalog/nodes/workload%3Aadmin-dashboard on the api origin; auth: false, approval: false) - Browse ASP.NET Core (GET /v1/catalog/nodes/stack%3Aframework-asp-net-core on the api origin; auth: false, approval: false) - Browse Multi-tenant relational data (GET /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data on the api origin; auth: false, approval: false) - Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission. ## About this recipe Canonical URL: https://ample.computer/recipes/admin-dashboard/asp-net-core/tenant-workspaces Formats: [HTML](https://ample.computer/recipes/admin-dashboard/asp-net-core/tenant-workspaces) | [Markdown](https://ample.computer/recipes/admin-dashboard/asp-net-core/tenant-workspaces.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aadmin-dashboard%3Aasp-net-core%3Atenant-workspaces) Recipe ID: `page:recipes:admin-dashboard:asp-net-core:tenant-workspaces` | Revision: `r1` | Catalog revision: `cat_eac8c53f36410baa` Status: verified; runs with one `ample deploy` call (support `verified`, execution `ready`) Path: [Agent hosting discovery](/discover/discovery) / [Applications and workloads](/discover/workload) / [Portals and communities](/discover/workload/portals-and-communities) / [Admin dashboard](/discover/workload/admin-dashboard) / [Host admin dashboard with ASP.NET Core: tenant-scoped workspaces](/recipes/admin-dashboard/asp-net-core/tenant-workspaces)