A senior .NET team for two jobs. We build new web APIs, services and apps on current .NET. And we move old .NET Framework systems to .NET 8–10 one step at a time, while your people keep using them.
Most .NET requests fall into one of these. Many clients start with one and move to another as the system grows.
Architecture, code, tests, CI/CD and hosting on Azure or AWS. We design for the load and the team that will maintain it after launch.
An assessment, a migration plan, automated tests around critical logic and a cutover that keeps daily work running.
Engineers who join your repository, your rituals and your code review. The team can grow or shrink as the work changes.
Each card links to a client project where we did this work, with the version of .NET it runs on.
ASP.NET Core APIs that hold the rules for orders, inventory, invoices and users, with the precision finance and operations teams expect.
Services split by domain that talk through REST and message queues, so one busy part of the system can scale without dragging the rest.
.NET MAUI and Blazor apps that run all day in the background and send clean data to the server behind them.
Imports, syncs, notifications and nightly runs that happen on time, retry on failure and show up in your logs when something goes wrong.
Large sites and portals on Umbraco, the .NET content management system, with custom catalogs, search and import pipelines underneath.
Assistants and generators that live in your existing .NET application, use its data and check their own output before a user sees it.
.NET Framework 4.8 still runs, but new libraries, hosting options and developers have moved to .NET 8 and later. A full rewrite puts the business on hold for months. We take the other route: assess, move in steps, protect the logic with tests and cut over when the new version has proved itself.
Jongeneel’s platform for inspections, toolboxes and transport planning moved from .NET Framework to .NET 10 and from Umbraco 8 to 17. NuPicker was replaced with Contentment, xUnit and Moq tests guarded the business logic, and Docker with CI/CD made builds repeatable. Read the case
We read the solution: projects, NuGet packages, internal libraries, background jobs and the modules people use every day. You get a list of risks and a target version.
Libraries and modules move one at a time. Packages with no future get a replacement with the same behavior. Nothing the business depends on is switched off to make room.
Unit tests around the logic that matters most run on every change, so a broken calculation shows up in the pipeline, not on an invoice.
Docker images and CI/CD make every build the same. Traffic or users move to the new version in stages, with the old one ready until the numbers look right.
Monitoring, logging and regular updates, so the next .NET release is a routine upgrade and not another rescue project.
HS High Stake GmbH in Karlsruhe runs a large portal for the German division of a well-known company, its dealers and its employees. It covers product materials, staff training and more. OSKI joined in January 2021, and over the project 7 different full-stack developers worked on it.
“Their communication skills, speed of development, and cost were incredible.”
Ben-Gurion University’s C# and Umbraco site serves applicants, students and staff. We containerized it and moved it from Azure to AWS ECS Fargate with RDS, S3 and ECR. Traffic shifted to the new setup gradually, and the public site stayed up the whole time.
A drone-based agricultural spraying company in Manson, Washington, had a software project in trouble. A previous developer had delayed and mishandled its project for more than six months. In May 2025 the owner brought in one OSKI engineer.
Relentless focus on customer success
This list comes from client projects, not from a wish list. It covers .NET Framework 4.8 on the oldest systems we maintain through .NET 10 on the newest ones.
Need a .NET site or portal with a content editor? See Umbraco development. Need engineers for months, not a project? See dedicated teams.
Migrations, microservices, cloud moves, desktop apps and AI features, on .NET 9 and .NET 10 among others.
An internal platform for inspections, toolboxes and transport planning, upgraded from Umbraco 8 to Umbraco 17 on .NET 10 with daily workflows intact.
The university's main Umbraco site: ~80,000 pages, ~1,000 editors, daily staff data imports and a zero-downtime move from Azure to AWS.
A cloud-native platform for multi-day, multi-venue events: 8 .NET microservices on Azure handle registration, scheduling, attendee matching and Zoom.
The third generation of a leading Israeli car site: ~100K records moved from a legacy CRM into Umbraco, fast catalog search and an editor-friendly back office.
An assistant inside Lokad's platform that answers questions, generates Envision code and tests it against the real Envision runtime.
An internal ERP that replaced separate tools for inventory, purchasing, shipping and reporting, with a two-way QuickBooks sync the finance team can rely on.
Quotes from verified Clutch reviews of long-running, rescue and custom software projects.
Guys proved to be experts in their field.
What stood out most was their commitment to delivering a functional and reliable solution, no matter the challenges.
Given that the client (us) invest in giving them adequate feedback, they deliver high quality, maintainable code.
The best enterprise CRM is the one that fits your identity stack, your ERP and your integration platform, not the longest feature list. We compare six platforms by data model, governance and API limits, with list prices.
Umbraco 8 reached end of life in February 2025. Moving to Umbraco 17 means migrating the database through supported steps and rebuilding the code layer on ASP.NET Core and .NET 10. Here is how to plan it.
A practical guide to shipping LLM-generated code users can trust: execute it against the real runtime, feed errors back for a retry, separate explain and generate modes, keep memory and track first-try and second-try success.
Anything missing? Send us your question and an engineer will answer, usually within one business day.
Contact usYes. We start by reviewing the solution, its packages and its internal libraries, then plan the move module by module. For Jongeneel, a transport company, we moved an internal platform from .NET Framework to .NET 10, replaced a plugin that had no upgrade path and kept background jobs running.
No. Critical modules keep working through the migration, and the cutover happens in stages. When we moved Ben-Gurion University’s site of about 80,000 pages from Azure to AWS, traffic shifted gradually and the public site had no interruption.
We add automated tests around the business logic that matters most before and during the move, so every change is checked in the pipeline. On Jongeneel we used xUnit and Moq for this, plus Docker and CI/CD so every build is the same.
Yes. We review the code first, fix what hurts daily work and then agree on a plan. For one AgTech client we took over a software project that a previous developer had delayed for more than six months and rebuilt the codebase with current practices. It was delivered on time and on budget.
Yes. Engineers work in your repository, follow your guidelines and go through your code review. For HS High Stake in Germany, 7 different OSKI developers worked on one .NET portal, starting in 2021. We say we can have a dedicated team ready in 2–4 weeks.
Our rate listed on Clutch is $25–49 per hour, and the minimum project is $1,000. Well-defined work can run as a fixed-scope, fixed-price project. Ongoing work runs as a monthly dedicated team or as individual engineers added to yours.
Anywhere that runs .NET. We have built and run .NET systems on Azure, including Azure Functions, Service Bus and Key Vault, and on AWS with ECS Fargate, RDS and S3. We also set up Docker, CI/CD pipelines and infrastructure as code with Terraform.
A spec, a Figma file or three paragraphs is enough to start.
Cookies on oski.solutions
We'd like to use analytics cookies to understand how the site is used, and marketing cookies to measure our ads. They are off unless you allow them. You can change your choice any time via “Cookie settings” in the footer. Cookie policy