Headless Conversational Engine Development in .NetCore

@Microlent

FSM Hello! I can build a headless, production-ready .NET Core conversational FSM that persists every state in SQL, archives payloads as JSON, and runs entirely through clean APIs with real-time updates. Here’s how I’d approach it: • Core FSM engine using a proven library like Stateless with JSON driven transition rules and guards • Db-first SQL persistence layer storing state history and raw conversational payloads • Clean domain mapping layer separating DTOs from business logic • SignalR real-time state updates and live event streaming • Centralized error logging with reporting hooks • Razor Pages admin portal for workflow editing, live logs, and parameter tuning • OAuth2 protected Super Admin access Deliverables: • /converse and /admin Web API endpoints running in .NET Core • SQL backed FSM with JSON replay and auditing • Razor Pages admin dashboard with visual debugging • Sample onboarding flow executing end to end • Unit and integration test suite • Docker compose for one-command local spin up I design state machines that stay flexible without becoming brittle or hard to maintain. Once I review your current DB schema and auth provider, I can lock architecture and timeline immediately. Best regards, Jasmin

@ambar

FSM Will each conversation instance map to one DB row per state change? Should side effects (email/webhook) run inside the transition or via background worker? Do you want workflow JSON versioned per release? I’ve done similar automation work before. I’d keep this simple. Stateless for the FSM core. Each conversation → Conversation table + ConversationStateHistory table. Raw payload stored as JSON column (NVARCHAR MAX). Db First via EF Core scaffold so it plugs into your existing DB cleanly. JSON rules parsed into a transition registry at startup. Small in-memory cache for workflow definitions (reload only when version changes). Guards mapped to C# handlers via dictionary (string → delegate). Side effects pushed to a background queue (IHostedService + Channel) so state save never blocks. SignalR hub grouped by conversationId. Serilog writing to SQL + rolling file. CorrelationId per request (middleware). Razor admin: single SuperUser OAuth2 login workflow JSON editor with basic schema validation live log stream manual state correction (with audit record) API: /converse, /admin Clean DTO layer separate from domain models. Basic integration tests using TestServer + in-memory SQL. Docker compose: api + sql server + seq (logs). Happy to handle this. Do you want workflow edits to affect running conversations or only new ones? Yes/No?

@OutsourceMan

⭐⭐⭐⭐⭐ FSM, Skills Required .NET SQL C# Programming Software Architecture Microsoft SQL Server JSON Web API .NET Core We propose implementing a modular, headless .NET Core FSM using the Stateless library for clean state transitions and guards. Each state and raw conversational payload will be persisted in SQL Server with JSON archiving for replay and analytics. Real-time updates will leverage SignalR, while error logging integrates Serilog with structured reports. The hybrid authoring GUI will be built on Razor Pages, allowing non-technical staff to tweak JSON-driven rules, with full source control support for developers. CnELIndia will handle architecture design, SQL schema, and API endpoints, ensuring seamless Db-First integration. Raman Ladhani will implement the FSM engine, JSON rule engine, Razor Pages portal, and unit/integration tests. Docker-compose will enable one-step local setup. Estimated timeline: 6–8 weeks for end-to-end delivery including sample workflows, logging, and real-time features.

@mubeenm5026

"FSM" At Web Crest, we understand the value of seamless and intelligent workflow management systems, which is why your project piques our interest. Myself, Mubeen, along with my dedicated and skilled 10-member team bring over a decade of experience in high-performing software development, C# programming, and software architecture to the table. We specialize in building solutions that are scalable, smart, and future-ready, making us the perfect fit for your FSM development needs. We realize the importance of data preservation for easy analysis and further adaptations. Our expertise lies in storing crucial information like state persistence using SQL while cleverly archiving raw conversational payloads as JSON. This ensures a compact storage design without compromising on data integrity or availability for real-time tracking. The convenience of non-technical staff tweaking parameters through a Razor Pages GUI alongside developers dropping JSON definitions propels us to balance power and ease of use. Combining this approach with our domain-mapping expertise enables immaculate separation of DTOs and domain objects. Plus, utilizing libraries such as Stateless would add significant value to your projects.

@usamae

FSM I've built .NET Core FSM pipelines using Stateless before - it's clean, testable, and serializes nicely to/from JSON for your rule engine. For storage I'd go with a two-table approach: one for state records, one for JSON payload blobs, so you get full replay and audit without muddying the relational schema. For the hybrid authoring model, the Razor Pages admin with SignalR live logs makes sense. I'd keep the FSM config completely decoupled from the runtime engine so non-technical staff can tweak guard params without touching source - and devs can still drop raw JSON defintions in directly. Timeline: FSM core + SQL persistence + API endpoints in week 1, admin portal + live log stream + workflow editor in week 2, tests + Docker Compose + sample onboarding workflow in week 3. Comfortably within 14 days. Happy to share a quick architecture sketch before we kick off if that helps. - Usama

@DIBS80

Microsoft Certified Professional, C#, .Net Developer, 15+ years of experience FSM HI, I’m a senior .NET Core architect with strong experience building state-driven workflow engines, real-time systems, and rule-based automation using libraries like Stateless combined with SQL persistence and JSON-driven configurations. I would structure this as a clean, headless FSM core with a domain-mapping layer, DB-first EF integration, and a Razor Pages admin portal for workflow editing, live logs, and OAuth2-protected access. The solution will include SignalR event streaming, structured error logging, and Docker-ready deployment, with a sample onboarding flow fully defined in JSON and covered by unit/integration tests. I can share a clear architecture breakdown and phased timeline to get the first working workflow running quickly. I’m ready to discuss next steps and start work.

@vishal1145

FSM - Your JSON-driven rule engine will fail under concurrent user sessions if you don't implement optimistic concurrency on state transitions. Without row versioning in SQL, two simultaneous requests can overwrite each other's state changes, corrupting the conversation flow and breaking audit trails. Before architecting the solution, I need clarity on two things. First, what's your expected concurrent user load - are we talking 50 simultaneous conversations or 5,000? This determines whether we need distributed caching with Redis or if in-memory state management suffices. Second, does your existing database schema enforce soft deletes and audit columns? I'll need to ensure the FSM persistence layer doesn't conflict with your current data access patterns. Here's the architectural approach: - STATELESS LIBRARY + CUSTOM WRAPPER: Use Stateless 5.x with a persistence adapter that writes state snapshots to SQL and appends JSON payloads to a separate ConversationEvents table with proper indexing on UserId and Timestamp for fast replay queries. - SIGNALR CORE: Implement hub-based real-time updates with connection mapping stored in Redis so admin users see live conversation state changes across multiple app instances without polling the database. - RAZOR PAGES + OAUTH2.0: Build the admin portal using IdentityServer4 for token-based authentication with refresh tokens, plus a visual workflow editor that generates valid JSON schemas and validates them against your FSM configuration before persisting. - DB FIRST EF CORE: Scaffold your existing schema with reverse engineering, then layer the FSM tables on top using migrations so ConversationState and ConversationEvents integrate cleanly without touching legacy tables. - DOCKER COMPOSE: Package the API, Razor admin, SQL Server, and Redis into a single compose file with health checks and volume mounts for local development that mirrors your production topology. I've built three similar state machine systems for fintech clients handling KYC workflows that processed 200K conversations monthly. The last one reduced onboarding time from 8 minutes to 90 seconds by eliminating blocking database calls during state transitions. Let's schedule a 20-minute technical call to walk through your existing schema and nail down the concurrency model before I start development.

@abbascsp

FSM I can design and deliver a headless, production-grade .net core FSM engine that persists every state transition in SQL, archives full conversational payloads as JSON for replay/analytics, and exposes clean Web API endpoints ready to integrate into your existing system. I’ve built workflow-driven systems and business-critical engines (ERP, logistics platforms, real-time dashboards) where state integrity, auditability, and extensibility were mandatory. This project aligns perfectly with that experience. I prefer DDD pattern where there will be a Data Layer for database management operations and entities (Db first approach), and a domain/api layer which will contain the business logic and implement the presentation layer (controllers). Libraries and Dependencies: - FSM Engine: Stateless (Open-source and widely used) - ORM: EF Core & Dapper (Only if required) - Database: Mysql OR Postgres OR MS Sql Server - Realtime Connection: SignalR - Authentication: JWT Authentication - Error logging: Native or Serilog I am looking forward to have a discussion with you and move forward with the project. Lets connect and discuss! Have a good day!

@Azursol

Hello,! I’m excited about the opportunity to help with your project. Based on your requirements, I believe my expertise in SQL aligns perfectly with your needs. How I Will Build It: I will approach your project with a structured, goal-oriented method. Using my experience in .NET, SQL, C# Programming, Software Architecture, Microsoft SQL Server, JSON, Web API, .NET Core, I’ll deliver a solution that not only meets your expectations but is also scalable, efficient, and cleanly coded. I ensure seamless integration, full responsiveness, and a strong focus on performance and user experience. Why Choose Me: - 10 years of experience delivering high-quality web and software projects - Deep understanding of SQL and related technologies - Strong communication and collaboration skills - A proven track record — check out my freelancer portfolio. - I’m available for a call to discuss your project in more detail - Committed to delivering results on time, every time Availability: I can start immediately and complete this task within the expected timeframe. Looking forward to working with you! Best regards, Ali Zahid India

@dataspro

Nice to meet you , My name is Anthony Muñoz, I express my interest in working on your project after carefully reading the requirements and concluding that they match my area of knowledge and skills. I am currently the lead engineer for the IT agency DSPro and I have more than 10 years of experience in the field. I have successfully completed a large number of similar jobs and I consider your project to be a challenge in which I would like to work and be able to make it a reality. Please feel free to contact me, it will be my pleasure to help you. I greatly appreciate the time provided and I remain attentive to any questions or concerns. Greetings

@mkh559a5a1fd66e9

FSM My approach is to build a dynamic, configuration-driven FSM engine where each conversation is defined as a workflow consisting of states, transitions and validation rules stored in SQL or JSON rather than hard-coded logic. Each user session will run as an independent conversation instance that stores current state, full context and payload in JSON for replay, debugging and recovery. The proposed flow will be: when a message or request arrives, the engine loads the active workflow and user conversation, identifies the current state, validates input, updates context, evaluates transition rules and moves to the next state, then returns the next response in real time via API or SignalR. All conversations will be persisted with complete history so they can resume after failure and be replayed for auditing. The system will be built with a clean layered architecture including core FSM engine, API layer with authentication, SQL persistence and structured logging. This ensures scalability, configurability and long-term extensibility so new conversation workflows can be added without major code changes.

@AlexDeveloper911

Hi, We went through your project description and it seems like our team is a great fit for this job. We are an expert team which have many years of experience on .NET, SQL, C# Programming, Software Architecture, Microsoft SQL Server, JSON, Web API, .NET Core Lets connect in chat so that We discuss further. Regards

@Ussama91

FSM I will design a .NET Core-based finite-state-machine with a modular architecture, using the Stateless library for the FSM engine, and SQL Server for storage, persisting each state and storing raw conversational payload as JSON, I will implement user authentication, real-time updates using SignalR, and error logging, with a hybrid authoring model, and deliver the solution based on the Db First Approach, including a Razor Pages admin portal, sample onboarding workflow, and unit/integration tests, with a rough timeline of 6-8 weeks, adapting to the proposed budget. Waiting for your response in chat! Best Regards.

@Zawiya3

"FSM" Thank you for considering me for your Headless Conversational Engine Development project. As a versatile full-stack developer with extensive expertise in .NET, C#, and SQL, I believe I bring a unique combination of skills that make me the ideal fit for this job. Over the years, I have been involved in numerous complex projects, but none quite as exciting as building an entire conversational flow system from scratch. By leveraging my experience in .NET Core and C# programming, I will create a robust finite-state-machine (FSM) engine tailored to your specific needs. Additionally, I will ensure that every state is adequately persisted in SQL while archiving the raw conversational payload as JSON for secure storage and easy analysis purposes. My familiarity with Razor Pages is another advantage I bring to the table - it will help me design an intuitive and user-friendly admin portal where non-technical staff can effortlessly tweak parameters. Having already worked with Db First Approach on existing projects, I can integrate this module seamlessly into your codebase — saving you valuable time and effort.

@seventysixeast

FSM Your project is interetsing and I would love to work on this. Would use the Stateless library and maybe the MArtenDB or stay with postgres. Is using mssql mandatory? About me I am a software developer with 30+ years of experience and my forte is databases and my passion for coding and for working on new technologies. I have done my Masters in Maths and Financial management and understand data and algos well. Stacks I work in: .Net/C#, Python, Node, Java, React, Angular, Php Databases: Postgres, MySql, MsSql, Elastic Search

@TechizeBuilder

Hi, I came across your project "Headless Conversational Engine Development in .NetCore" and I'm confident I can help you with it. About Me: I'm a agency owner with over 8+ years of experience in SQL, JSON, Web API. , and I understand exactly what’s needed to deliver high-quality results on time. Why Choose Me? - ✅ Expertise in required Technologies and 1 year post deployment free support - ✅ On-time delivery and excellent communication - ✅ 100% satisfaction guarantee Let’s discuss your project in more detail. I’m available to start immediately and would love to hear more about your goals. Looking forward to working with you! Best regards, Deepak

@abdf2010

Hello there, I reviewed your project Headless Conversational Engine Development in .NetCore and understood the requirements at a high level. I focus on delivering clear, stable, and maintainable solutions aligned with the actual scope, I can work with .NET, SQL, C# Programming and follow a clean development process with proper structure and error handling. If this aligns with what you’re looking for, please come to chat to discuss further. Best regards

@jagratip3

Hi there, I can build a headless .NET Core finite-state-machine (FSM) platform that drives full conversational workflows with persistence, real-time updates, and JSON-driven rules. Proposed Architecture: FSM Engine: Use Stateless library for robust state transitions, guards, and side effects. Encapsulate each conversation as a Session with current state and metadata. Persistence Layer: SQL Server (Db-First) stores both the current FSM state and the raw JSON payload for replay and analytics. Rule Engine: JSON-driven definitions for states, transitions, guards, and side effects. Hybrid authoring allows non-technical staff to tweak parameters via Razor Pages GUI, while developers can commit full JSON definitions to source control. Timeline (Rough): Week 1: FSM engine scaffolding, Db-First setup, JSON rule engine Week 2: API endpoints, SignalR real-time integration, domain layer Week 3: Razor Pages admin portal, workflow editor, authentication Week 4: Sample workflow, testing, Docker-compose, final polish This approach provides a robust, extensible FSM framework that’s easy for non-technical staff to manage while fully developer-friendly for complex workflows.

@Cmonosoft

FSM Hi there, I am ready for video call interview! I can design and implement a headless, production-ready .NET Core finite-state-machine that runs full conversational onboarding flows with SQL persistence, JSON archiving, real-time updates, and a hybrid rule-authoring model. Process Core Engine - * .NET 8 Web API * FSM powered by Stateless or a custom extensible state engine wrapper * State transitions fully driven by JSON definitions * Guard conditions and side effects resolved through registered strategy handlers Persistence Layer - * SQL Server or PostgreSQL * Tables for: Conversations, States, Transitions, Events, Logs * Raw inbound/outbound payload stored as JSON * Full replay capability via stored event stream Rule Engine - * JSON-defined workflow schema * Transition rules, guards, and side effects declarative * Non-technical editing through Razor Pages GUI * Developers can commit JSON definitions directly to source control Real-Time Layer - * SignalR hub for live state updates * Live log stream in admin portal * Event notifications on transition success/failure API Endpoints - * POST /converse (state-driven message processing) * GET /admin/workflows * POST /admin/workflows * SignalR /hubs/conversation I am ready to begin with schema alignment and FSM modeling! Thanks Saurabh