.NET low-code frameworks: a practical selection guide
Choose a .NET low-code framework for model-driven applications, visual workflows, RBAC and reporting. Explore how Exceleron’s Genie fits your project.
Published by Exceleron, the provider of Genie. This is a use-case selection guide; the options below are not ranked. External descriptions link to the respective official documentation.
What makes a low-code framework useful for .NET teams?
A useful evaluation goes beyond how quickly a demo form appears. Check how the framework handles your data model, permissions, changes, integrations and production operation.
Model-driven low-code
Describe entities, tables, forms and navigation in models. Evaluate how model changes reach the data layer, API and UI, and where custom development is needed.
Workflow engines
Represent business states, decisions and approvals. Check versioning, permissions, pending human tasks and the history needed to explain a decision.
Orchestration
Coordinate multiple activities across services. Evaluate persistence, recovery, timeouts, external events and the exact delivery guarantees of the chosen runtime.
Background workers
Run processing outside the request cycle. Check scheduling, monitoring, retries, cancellation and protection against duplicate side effects.
How Genie builds a .NET business application
Genie combines a .NET runtime and source generation with a React and TypeScript interface. XML models describe application structure; the runtime supplies JSON metadata, data and permissions to the UI.
Model the records and views
Describe entities, tables, forms and navigation. Review the generated data model and migration before applying database changes.
Configure the user journey
Use wizard, workflow, navigation and report designers to shape the business process. Developers extend integration and domain behaviour where required.
Apply access control
Test role-based permissions with real job roles, including who may view a record, perform an action or approve a request.
Validate operation
Demonstrate reporting, worker monitoring and on-prem or cloud deployment against your operational requirements.
Framework and engine shortlist
These options cover different layers of the stack. Choose by project requirements rather than a universal “best framework” label.
| Option / category | Where to evaluate it | Questions to resolve |
|---|---|---|
| Exceleron’s Genie Model-driven application platform | Business applications combining forms, data views, visual approvals, reporting and role-based access. | Ask for a walkthrough using your own model and approval process; confirm package access, licensing and deployment requirements. |
| Elsa Workflows .NET workflow engine | Embedding a workflow engine or deploying its Server and Studio to author and operate processes. | Evaluate activities, persistence, designer integration and the application UI you will build around the engine. |
| Workflow Core Lightweight .NET workflow library | Developers composing stateful, multi-step workflows with pluggable persistence and concurrency providers. | Evaluate the code authoring approach, persistence provider and operational tooling for your application. |
| Microsoft Durable Functions Stateful serverless orchestration | Code-defined orchestrators coordinating activities and entities on Azure Functions. | Evaluate the hosting model, storage backend, replay constraints and integration with your cloud environment. |
| Hangfire .NET background jobs and workers | Enqueuing background work, delayed jobs, recurring jobs and continuations backed by persistent storage. | Evaluate job execution and retry behaviour; design human approval screens and business workflow state separately. |
Where Genie fits: business workflows on .NET
Genie’s workflow engine uses versioned state-machine definitions bound to business records. Teams can author definitions in XML or use the visual designer, then publish the version that should run.
Human approvals
Any, sequential and parallel approval modes support processes that need assigned reviewers and explicit decisions.
Actions and integrations
Workflow actions can send notifications, execute SQL or call webhooks. Validate authentication, retries and failure handling for each external integration.
Monitored services
The .NET engine includes a monitored background-service base with runtime metrics and dashboard pause/resume support. Confirm which workers your application needs.
For a demo, bring one record type, one approval path, the roles involved and an external API to integrate. Include rejection, duplicate submission and service-failure cases in the acceptance criteria.
See business applications built on the platform
Questions to ask before choosing
Which is the best .NET low-code framework?
The answer depends on the application. Compare model ownership, UI flexibility, workflow needs, access control, hosting, licensing and the effort required to extend the platform. Ask each provider to implement the same small acceptance scenario.
Does a workflow engine replace a background job processor?
A workflow records the business process; a worker executes work. Some systems combine both. Check the documented persistence and execution guarantees before relying on a tool for recovery or cross-service coordination.
Can Genie be evaluated for on-premises applications?
Yes. Discuss the target infrastructure, database, identity integration and operational requirements with Exceleron. Package access and commercial terms should be confirmed during evaluation.
Read the .NET workflow engine and worker comparison · Request a technical walkthrough