Host approval workflow with ASP.NET Core: relational workspace data · Ample Computer
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). The approval workflow-specific behavior (your record schema, states and access rules) is your application code on that verified basis.
supportverifiedreleasepublishedagent runready
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis supplied.
You need
- An ASP.NET Core project that builds and starts with the documented commands (
dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT) - A PostgreSQL driver reading
DATABASE_URLat 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
Build and start.
dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT. The server must bind0.0.0.0onPORT.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.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 <app-name> --public
- 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, readample logs <deployment_id> --kind buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL · http get/ → "ample canary asp net core patterns"
✓ relational-records self-test · http get/p/relational-records → "records=ok transitions=true isolation=true"
Evidence
November 6, 2026 · canary run
ASP.NET Core pattern fixture deployed on Ample (dotnet publish -c Release -o outin the builder, thendotnet <entry>.dllon the dotnet-10 template withASPNETCORE_URLSbound toPORT); 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).November 5, 2026 · canary run
The same ASP.NET Core app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested 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.
What it doesn’t cover
- Verified on the dotnet-10 template at
s-1vcpu-1gbwith the example fixture. - The pattern checks verified the platform side; the approval workflow itself (your record schema, states and access rules) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.