Host approval workflow with ASP.NET Core: relational workspace data

Deploy an approval workflow 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 approval workflow-specific behavior as your application code.

Representative Queries

• Host approval workflow with ASP.NET Core: relational workspace data
• Where can I host Approval workflow built with ASP.NET Core?
• I need a workspace-specific schema, state transitions and access rules.

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.

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

Tested Configuration

• Template: dotnet-10
• Runtime: dotnet
• Size: s-1vcpu-1gb
• Build Command: dotnet publish -c Release -o out
• Start Command: ASPNETCORE_URLS=http://0.0.0.0:$PORT dotnet out/$(basename $(ls out/*.runtimeconfig.json | head -n 1) .runtimeconfig.json).dll

Workflow Steps

1. Build and start

   • Run dotnet publish -c Release -o out in the builder, then dotnet .dll on the dotnet-10 template with ASPNETCORE_URLS bound to 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.
   • Command: ample logs --kind build

Examples

ASP.NET Core pattern fixture

• Description: Multi-pattern ASP.NET Core app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
• Source Reference: tests/deploy-canaries/asp-net-core-patterns

Success Checks

• App responds on its public URL (check path: /, expect: ample canary asp net core patterns)
• Relational-records self-test (check 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 approval workflow 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.

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

• Summary of checks passed for relational-records 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.