Experienced C# .NET Data Management App

@talhaamin

I have a vast experience in developing your requirements. I have served various clients using your required architecture. Looking forward to discuss more details.

@ConnectUsSoft

Hello, I went through your project. We can help build a secure client-server solution with .NET APIs, remote policy management, web dashboard, and clean architecture. We have strong expertise in C#, .NET, REST API, SQL, JavaScript, web applications, cloud deployment, and server management. Let's discuss your project. Thank you.

@amusto

With my extensive experience of over 20 years in the software engineering field, focusing heavily on C#/.NET, I have successfully delivered numerous clean and well-commented production-quality solutions. Throughout my career, I have always practiced modern .NET techniques like dependency injection, async/await, and EF Core — exactly what your project demands. Moreover, I religiously follow a clean, layered architecture approach coupled with thorough unit and integration testing to ensure robustness. In addition to all these attributes, my fluency in REST API development combined with my adeptness at SQL Server storage management will ensure a seamless workflow between your client and server components. My rich understanding of automated testing methodologies also guarantees that critical paths in the application will be thoroughly tested to meet the required quality standards. Which type of client do you want? Web based or desktop? I can do both with Angular or WPF as you prefer. Please contact me to discuss the details so I can provide a detailed plan with times and costs. Regards, Armando

@AhteshamAK

The core challenge in an endpoint security platform is not only building the client and server components — it is designing a reliable architecture where workstation policies, remote management, reporting, and future scalability work together securely. I would approach this with a clean layered .NET architecture using dependency injection, async workflows, EF Core data access, REST-based communication, and a maintainable management dashboard for centralized configuration. The solution would be structured around: • Windows workstation client agent • .NET server/API layer • Secure policy distribution and status reporting • Database architecture • Web-based administration panel • Automated testing and deployment documentation My experience with enterprise applications, business management systems, APIs, databases, and scalable web platforms allows me to focus not only on development but also on long-term maintainability and production readiness. I can provide architecture documentation, clean source code, deployment guidance, and a complete handover process. Could you share the expected number of managed endpoints and whether the server environment will be cloud-hosted or deployed on-premise? Best, Ahtesham

@seefattechnologi

OKAY------ I will deliver exactly what you need with high-quality, clean, and scalable solutions. I have successfully completed similar projects for my clients before. As an experienced .NETFull Stack Developer, I am sure you'll be impressed with both my work quality and commitment.  Please ping me to get started and achieve outstanding results. Thanks!!

@kamran2012

Interesting project, Hi, I will deliver the full client/server solution: the workstation agent enforcing security policies locally, the REST API handling policy distribution and status reporting, and a web front end for centralized management. Architecture will follow clean layered design with dependency injection, async/await, and EF Core for the data layer. On a similar policy management system, structuring the agent with a local policy cache and a heartbeat sync loop eliminated downtime gaps when the server was briefly unreachable. I will apply the same pattern here. Questions: 1) For the workstation client, which OS versions must it support (Windows 10+, Server 2019+, or others)? 2) Do you have specific security policies already defined, or will the policy schema be designed as part of this project? Looking forward to your response. Best regards, Kamran

@vladang

The part that usually bites in an endpoint solution like this isn't the REST layer. It's what the client does when it can't reach the server. If enforcement fails open on a dropped connection, the policy model stops meaning anything, so I'd build the client as a Windows service that caches the last signed policy locally and keeps enforcing until it receives a verified update, then reconciles state on reconnect. On the server, I'd use layered .NET with DI and EF Core, keeping policy distribution, client status reporting, and central management as distinct REST endpoints. Client identity gets signed so a spoofed agent can't pull configuration, and every policy carries a version and signature the client validates before applying. Integration tests would exercise the full round trip (policy push, client apply, status report back) rather than only isolated units, which is where these systems usually break. C++ handles the low-level workstation enforcement, process and registry hooks, sitting behind a clean C# interface so the managed side stays fully testable. The web front end stays focused on policy editing and live client status, with schema and architecture docs plus dev and production deployment scripts delivered alongside the source. One thing worth settling early: are the workstations domain-joined, or do agents authenticate to the server on their own? That decision shapes how I handle client identity and policy signing across the board.

@akshaybhagwat76

Hi, I'm a C#/.NET Core developer with 7+ years building production-grade backend systems using EF Core, dependency injection, async/await, and layered architecture — the exact pattern this project calls for. I've delivered REST APIs for policy distribution, config management, and status reporting in multi-tenant enterprise systems (healthcare, ERP, LMS platforms), along with RBAC and secure authentication flows. Proposed approach: a lightweight Windows client reporting status/enforcing policy via REST, a server layer handling policy distribution with EF Core-backed persistence, and a clean web front-end (Angular) for centralized management — built with clear separation of concerns for testability. I write thorough unit/integration tests (xUnit) for critical paths and document architecture and schema clearly for handover. Comfortable scripting deployment for dev/prod environments. Happy to discuss polling vs push for client-server communication before starting.

@shrec

Hi, I reviewed your project and would be happy to help. I have relevant experience, communicate clearly, and focus on delivering high-quality work on time. I can start immediately and will keep you updated throughout the project. Please share any additional requirements, and we can discuss the best approach. Looking forward to working with you. Best regards, Ivane C

@tnt42010

Hello, I have extensive experience building **enterprise-grade C#/.NET applications, client-server systems, REST APIs, security-focused software, and modern web applications**. I can deliver a scalable, production-ready endpoint management platform with clean architecture and comprehensive documentation. **My approach includes:** * Designing a layered architecture using **ASP.NET Core, EF Core, Dependency Injection, async/await, and REST APIs** * Developing the workstation client for secure policy enforcement and status reporting * Building a responsive web-based management portal for centralized administration * Implementing secure authentication, role-based access control, auditing, and encrypted communication * Creating automated unit and integration tests for critical workflows * Providing deployment scripts, database schema, architecture documentation, and a complete handover The solution will be modular, maintainable, and designed for future expansion while following .NET best practices and production-quality coding standards. I look forward to discussing your security requirements and system architecture in more detail.

@devitmd98

Hi, The main challenge in building an endpoint security platform is not only developing the client and server components, but creating a reliable architecture where workstation agents, centralized policies, reporting, and remote management work together securely and efficiently. I have experience developing production-grade applications using C#/.NET, REST APIs, database-driven systems, and modern software architecture patterns. My approach would be to design a clean layered architecture with dependency injection, async workflows, EF Core-based data access, secure communication between client and server, and a scalable web management interface for administrators. I can help build the complete solution including the workstation client, backend services, REST endpoints for policy distribution and status monitoring, database design, and responsive web frontend. I will also focus on maintainability through proper documentation, automated testing, deployment scripts, and a structured handover process. The final delivery would include the complete source code, architecture documentation, database schema, test coverage for critical workflows, and guidance for deployment and future expansion. Thank you for reviewing my proposal. I look forward to hearing from you.

@devbaloni1983

Hi, ** .Net expert** I have more than 15 years of experience in the development As I am an expert, I can build it according to your requirements. Because I have a lot of experience in these fields, I can build your project as soon as possible. I offer excellent software quality work and provide the best support for your project. If you give me this job, I will do my best to finish your job by your timeline. If you want to see my past works, I can show you my past works right now. Ready to discuss this with you about the task now. Thank you for the reading.

@gowthamsarathy

Hello, I reviewed your requirements carefully and understand that you need a production-grade C#/.NET endpoint security platform consisting of a workstation agent, centralized REST API, database layer, and web-based administration console. My approach would use modern .NET with a clean layered architecture, dependency injection, async processing, EF Core, and secure API communication. The workstation client will enforce policies locally while maintaining resilient synchronization with the server, including offline policy caching and status reporting. The web console will provide centralized policy configuration, endpoint visibility, and management. I’ll also implement unit/integration testing for critical workflows, deployment scripts, architecture/database documentation, and a complete handover. Quick questions: * Should endpoint policies remain enforceable from a locally signed/cached policy when the workstation loses server connectivity, and how should policy expiry be handled? * What tamper-resistance level is required for the workstation agent—for example, protection against local users stopping the service or modifying cached policies? I can start ASAP and would be happy to discuss the security model and architecture in detail. Best Regards

@vishal1145

Your REST API will become a single point of failure if the server goes down and workstations cannot retrieve updated policies. Without a fallback mechanism, endpoints will either freeze or revert to insecure defaults during outages. Quick questions - are you planning active-active redundancy or will clients cache policies locally with TTL expiration? And what's your target fleet size - 100 endpoints or 10,000? Here is the architectural approach: - C# .NET CORE: Build the server with layered DI architecture using EF Core for policy versioning and async REST endpoints that handle concurrent client requests without blocking. - WINDOWS DESKTOP CLIENT: Implement a background service that polls the server, enforces policies via Windows APIs, and queues status reports when offline to prevent data loss. - DATABASE DESIGN: Design a schema with policy inheritance tables, audit logs, and indexed client status records to support fast queries as your fleet scales beyond 5K endpoints. I've built similar endpoint management systems for 2 enterprise clients where uptime was non-negotiable. Let's schedule a 20-minute architecture review before you commit to the build.

@corpmember29

Hello, I have reviewed your client-server endpoint security platform requirement and understand that the scope includes a C#/.NET workstation agent, REST-based management server, web administration front end, EF Core data layer, automated testing, and production deployment. I have 8+ years of experience in C#, .NET, ASP.NET Core, EF Core, Windows services, endpoint management systems, REST APIs, SQL Server/PostgreSQL, React/Angular front ends, CI/CD pipelines, and enterprise security-focused applications. I can deliver a layered architecture using dependency injection, async/await, clean domain separation, unit and integration tests, deployment automation, and comprehensive documentation. My recommended stack is .NET 8 for the server and workstation client, ASP.NET Core Web API, EF Core with SQL Server or PostgreSQL, React for the web front end, xUnit for testing, and Docker/PowerShell deployment scripts for development and production environments. I WILL PROVIDE 2 YEARS OF FREE ONGOING SUPPORT AND COMPLETE SOURCE CODE. WE WILL WORK WITH AGILE METHODOLOGY AND I WILL ASSIST FROM ARCHITECTURE, DATABASE DESIGN, CLIENT AGENT DEVELOPMENT, WEB FRONT-END IMPLEMENTATION, TESTING, DEPLOYMENT AUTOMATION, DOCUMENTATION, AND FINAL HANDOVER. I am available on desk as per your convenient time zone and will work on your project until you are satisfied with my work. Thanks Christina

@mbilal4

Hi, I can build your endpoint security platform in C#/.NET, including the workstation client, REST API, database, and web dashboard. The system will allow you to manage security policies remotely, deploy them to workstations, and monitor client status from one place. I’ll use clean .NET architecture with EF Core, dependency injection, async services, testing, and deployment scripts. I can start with a working policy-management and reporting prototype, then complete the remaining features in clear milestones. Let’s discuss the security policies you need and the Windows versions you want to support.

@SJMDEVELOPER

Hi, Hope you're doing well in Katowice! We’re an ISO-certified software partner specializing in high-leverage C#/.NET enterprise software, Windows desktop apps, REST APIs, and secure client-server systems. Here is what we will build for your platform: ✓ Complete Endpoint Security & Data Management: Performance-focused C#/.NET workstation client. ✓ Scalable Core Architecture: REST server with EF Core, centralized policy management, and a clean web admin portal. ✓ Production-Ready Quality: Automated testing baked in from day one to ensure zero technical debt. ✅ Question: Do you already have the endpoint security policies and workflows defined, or would you like us to help design the overall architecture and policy framework? If you're open to it, let's connect for 10 minutes to walk through your timeline and nail down the best execution strategy. Best, Manoj

@ssquare489

For this endpoint-security platform, I would separate the workstation client, management API, policy engine, and web console into clearly defined layers so each component can be tested, deployed, and extended independently. I recommend modern .NET with C#, ASP.NET Core Web API, EF Core, SQL Server or PostgreSQL, and a React or Angular administration portal. My two priorities would be clean implementation and scalability: signed policy packages, secure device enrollment, reliable background synchronization, and auditable configuration changes will protect endpoints while making centralized administration dependable as the workstation count grows. The client would run as a Windows Service, periodically retrieve policies, enforce approved controls locally, report health and compliance status, and continue operating safely during temporary network loss. The server would provide REST APIs, RBAC, device inventory, policy versioning, deployment groups, status reporting, alerts, audit logs, and secure certificate or token-based client authentication. I handle architecture, database design, client and server development, web dashboards, automated testing, deployment scripts, documentation, and handover. The codebase would follow dependency injection, async patterns, layered architecture, structured logging, and unit/integration coverage for policy delivery, authentication, enforcement, and reporting.

@JustinJcob

How strict should the workstation enforcement be: Windows-only with services/agents running elevated, or cross-platform .NET client support? Also, do you already have specific security policies in mind, such as USB blocking, app control, firewall rules, or compliance/status checks? I can build your full C#/.NET client–server endpoint security solution with a clean layered architecture, REST APIs, EF Core data layer, async/await, DI, web-based management frontend, automated tests, deployment scripts, and hand-over documentation. I’m ready to handle the workstation agent, policy distribution, reporting, admin dashboard, schema design, and production-ready code structure. I’m young, a fast learner, and available 24/7 to keep communication and delivery moving quickly. Let’s chat so I can understand the exact policy scope and deployment environment. Kind regards, Haroon Z.