On this page
Build a product with foundation
Start from your goal and understand the ownership boundaries.
foundation provides reusable .NET building blocks for product backends. Choose the capabilities your host needs, retain ownership of your domain and deployment, and upgrade through explicit NuGet versions. It does not install an ERP or own your customer directory, tenant membership, database migrations or frontend.
Choose your path
- First integration: create a working API.
- Package access: configure NuGet and run a cache consumer.
- Identity: choose browser, native or machine authentication.
- Outgoing email: configure SMTP or Graph.
- Product architect: choose package boundaries.
- API author: secure browser and machine requests.
- Operator: configure logs and request measurements.
- App developer: use the authoring contract.
- Documentation frontend author: consume the content bundle.
Release and scope
This bundle describes 0.19.0. It adds native OIDC token exchange and explicit BFF transport, request-zone JSON output and presentation controls to the existing host, authentication, mail, persistence, observability and integration adapters. Consumers retain their explicitly selected release line. The exported version must match compiled assemblies; select an explicit package version from the feed. Page status distinguishes released capabilities from future integrations.
Strong authentication supplies backend integrations, while client bridges and physical-device acceptance remain product-owned. Read its boundaries before exposing any method in a product.
What you get
The dependency-free Kernel contains results, errors and identity primitives. Application defines provider-neutral ports. Optional adapters implement cache, diagnostics, mail, templates, schedules, validation, realtime and MCP. The host selects adapters explicitly; installing a package does not configure middleware, credentials, persistence, access policies or remote services.
Start with a working integration, then follow the corresponding concept and API reference. Generated signatures supplement authored guides; missing API summaries are reported instead of guessed.
Follow a complete integration path
For a browser product, continue from the first API through authentication selection, the BFF, local sessions and presentation. For a worker, start with mail setup, protected secrets and durable execution. For modular applications, review persistence composition before adding shared mappings.
The reference introduction connects these tasks to the exact package contracts. Use troubleshooting at the failing boundary.