Host Inventory Manager with ASP.NET Core: Relational Workspace Data

Deploy an inventory manager built with ASP.NET Core on Ample using the relational records 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 workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states, and access rules; treat the inventory manager-specific behavior as your application code.

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

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

1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. 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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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/relational-records) 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 relational records 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
• Relational-records self-test:
  • Kind: http_get
  • Path: /p/relational-records
  • Expect: records=ok transitions=true isolation=true

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 inventory manager itself (your record schema, states and access rules) 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
• 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. Buckets are allocation-priced per quota and not included.

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 relational-records and configuration-secrets. Pattern proof: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
  • Observed At: 2026-09-21T01:15:54Z
  • Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty (CLI 0.1.21)
  • Expires At: 2027-03-20T01:15:54Z
  • Scope: checks=[/p/relational-records], pattern=pattern:relational-records, template=dotnet-10
• Canary Run: The same ASP.NET Core app deployed with a --release-command migration; the marker it created was readable after activation.
  • Observed At: 2026-09-20T23:34:47Z
  • Implementation Revision: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
  • Expires At: 2027-03-19T23:34:47Z
  • Scope: pattern=pattern:relational-records.

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search with body { limit: 5, query: "Host inventory manager with ASP.NET Core: relational workspace data" }
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan with body { inputs: {}, projectId: "", recipeId: "page:recipes:inventory-manager:asp-net-core:relational-workspace", recipeRevision: "r1" }
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Inventory Manager: GET /v1/catalog/nodes/workload%3Ainventory-manager
• Browse ASP.NET Core: GET /v1/catalog/nodes/stack%3Aframework-asp-net-core
• Browse Relational Records: GET /v1/catalog/nodes/pattern%3Arelational-records
• Browse Deploy Web App: GET /v1/catalog/nodes/intent%3Adeploy-web-app