How Generated Apps Work
Understanding the runtime architecture, request processing pipeline, background workers, and database lifecycle of your ProjectHelm application.
Every application built by ProjectHelm is a self-contained, enterprise ASP.NET Core solution. There is no central orchestrator or hidden proxy; the emitted container runs directly on Kestrel behind your reverse proxy.
The ASP.NET Core Request Pipeline
Cookie authentication middleware validates the user session. In SaaS apps, the tenant identifier is extracted from claims and injected into the request-scoped ICurrentTenantProvider.
Role policies and custom permissions are evaluated on controller actions before action execution begins.
Before saving records to EF Core, validation rules check preconditions. If state transitions occur, workflow transitions log history, trigger emails, and fire webhooks.
Soft-deleted items (!e.IsDeleted) and foreign tenant rows (e.TenantId == CurrentTenant) are filtered out automatically at the SQL query level.
Background Workers & Automations
Applications with scheduled or interval automations run background hosted services (IHostedService). A cron worker checks every minute for scheduled tasks (daily morning sweeps, interval jobs every N minutes, and email retry queues) without requiring external Lambda functions or cron daemons.