## Host crm with ASP.NET Core: relational workspace data

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

### Representative Queries
- Host crm with ASP.NET Core: relational workspace data
- Where can I host CRM built with ASP.NET Core?
- I need a workspace-specific schema, state transitions and access rules.

### 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 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 <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 crm 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
- **Monthly Amount**: 10.0 USD   
  Components:  
  - App Server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0  
  - Managed PostgreSQL Database: 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 relational-records and configuration-secrets.
  Observed At: 2026-09-21T01:15:54Z

### Next Actions
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**  
- **[Prepare a side-effect-free deployment plan for an authorized project](https://api.ample.computer/v1/catalog/plan)**