Brief
You describe the users, the job to be done, current tools and any hard date or constraint. A page is enough.
Technologies
.NET development for APIs, desktop software and Windows-fluent operations
.NET is a first-class backend and desktop stack at Hirvex Technologies. We use it for APIs, internal systems and Windows applications that have to live with domain-joined PCs, local devices and IT policies that a Node process on a laptop will not survive.
Who this is for. Organisations standardised on Microsoft tooling, or products that must be desktop-native on Windows.
Problems we typically meet
These are the patterns that show up before a useful first release—not abstract “digital transformation” language.
- A web app was forced onto a counter that needed a desktop runtime.
- Legacy .NET Framework code has no owner.
- IT will not run unsigned mystery installers.
- The rest of the enterprise speaks C# and SQL Server.
How we approach the work
We target current .NET for new work. Migrations from Framework are estimated after a read of the solution. Desktop packaging and update behaviour are part of the product when we ship a client.
What a serious first release can include
Scope is confirmed in discovery. This is the shape of work we are equipped to deliver—not a menu you must buy in full.
- ASP.NET APIs and web apps
- Windows desktop applications
- SQL Server and PostgreSQL-backed systems
- Integrations into Microsoft-centric estates
- Gradual modernisation of legacy .NET
What we need from you
A useful brief is better than a long one. If you can answer most of the following, we can propose a first slice instead of a theatre estimate.
- Who will use this, and what must they finish in a session?
- Which systems must stay (accounting, payments, identity, a shop)?
- What is already live that we should not break?
- Any hosting region, language or compliance rule that is non-negotiable?
- The date that actually matters—and why.
How an engagement runs
Four steps. No mystery bench.
Scope
We reply with clarifying questions and a first-release outline: modules, roles, integrations and what “done” means.
Build
Named engineers work in visible increments, with staging you can click and a weekly written status.
Run
Launch, handover and a support path. The system is yours to operate—not a black box we disappear from.
Questions we are asked
C# only, or also VB.NET?
New work is C#. We can maintain VB.NET in a takeover if that is what the repository contains; we will not start new VB products.
Azure required?
No. .NET runs well on Linux and on other clouds. Azure is used when you already have it or it is the right operational fit.
Start a conversation
If this is the work in front of you
Send the users, the job to be done and any hard constraint. We will answer as engineers—not with a canned brochure.