.NET
Our backbone for APIs, enterprise integrations, and Windows software.
What we build with it
- REST and gRPC APIs
- Integrations with enterprise systems
- Windows desktop tools
- Background services and schedulers
Why we use it
.NET is fast, strongly typed, and backed by Microsoft's long support cycles, which matters when software has to run for a decade. C# also carries across server, desktop, and mobile through MAUI.
When we don't use it
For a small API attached to a JavaScript frontend, Node keeps the whole stack in one language. We choose per project, not by habit.
What we have written about .NET
- .NET vs Node.js for a business backend: we measured both
We built one API in .NET 10 and Node.js 24. .NET served 1.6x to 4.2x more requests than 4 Node processes on 4 CPUs. Why that rarely decides it.
- Avalonia vs .NET MAUI vs WPF: which to pick for Windows desktop
WPF for Windows-only apps, Avalonia when you need macOS or Linux too, and .NET MAUI only if the same UI must also ship on iOS and Android.
- Hiring a .NET MAUI developer? 7 things to ask for first
Before you hire a .NET MAUI developer, ask for apps live in both stores, a plan for the yearly .NET upgrade, and signing keys held in your accounts.
- Tauri vs Electron vs WPF benchmark: size and memory measured
One app built in Tauri, Electron, WPF, Avalonia, and Wails on Windows 11. Tauri's installer was 1.05 MB, Electron's 106 MB. Idle memory was closer than claimed.
Questions clients ask
Short answers, no sales language. If yours isn't here, ask an engineer directly.
Ask us anythingIs .NET only for Windows?
Not for years now. Modern .NET runs on Linux and macOS, and most of our .NET APIs deploy to Linux containers.
Which .NET do you use?
Current LTS releases, with ASP.NET Core for web APIs and EF Core for data. Legacy .NET Framework work we take case by case.
Got something to build?
Tell us what you need. An engineer replies, not a sales team.