.NET & Microsoft Azure

Build, modernise and extend serious Microsoft software platforms.

Yeti provides experienced product engineering for organisations running complex .NET, C#, Azure and SQL estates - from new platform development and integrations to legacy modernisation and additional engineering capacity.

Talk to Yeti See our work

What we do

Four kinds of work inside a Microsoft estate.

Most engagements are a combination rather than one of these alone: a new service that has to speak to an older system, or a modernisation that only makes sense once the integrations around it are understood.

Build
New applications, services and APIs built in modern .NET, designed to be maintained and extended by the people who will own them.
- C# and modern .NET
- Web applications and APIs
- Business and operational software
- Backend and transactional services
Modernise
Ageing applications moved forward in controlled stages. We start from what the business depends on rather than defaulting to a full rewrite, and we do not treat splitting a system into services as an automatic improvement.
- Legacy .NET modernisation
- Architecture and maintainability
- Cloud migration in stages
- Performance and technical debt
- Repeatable deployment
Azure
Cloud engineering considered alongside the product: how it is hosted, secured, released and observed once it is live.
- Azure App Service hosting
- Azure SQL and managed data services
- Key Vault and secure configuration
- Storage and private networking
- Front Door and traffic routing
- Application Insights and monitoring
- Automated delivery pipelines
- Terraform and Terragrunt
Integrate
Most serious platforms sit inside an existing estate. We work with what is already there instead of asking the business to rearrange itself around us.
- Third-party and provider APIs
- Payment and transactional flows
- Identity and access
- CRM and internal platforms
- Data flows and reporting
- Event and message-based integration

Working with an internal team

Already running .NET and Azure?

Yeti can work alongside an established internal engineering organisation and take ownership of a product, service or delivery workstream without requiring the surrounding estate to be rebuilt around our preferences.

How added engineering capacity works

This tends to be useful where:

The roadmap is bigger than the engineering capacity available to deliver it.
Permanent recruitment is taking longer than the business can wait.
A contained workstream needs someone to own it end to end.
Specialist engineering help is required for a defined period.
Legacy work is consuming the capacity of the core team.

Beyond the backend

The product around the platform, not only the platform.

Backend engineering on its own rarely finishes a product. Yeti covers the interface, the design decisions, the mobile experience and the infrastructure it runs on, so a workstream does not stall waiting for another supplier.

Frontend engineering
React, Vue, TypeScript and modern component architecture.
Product design and UX
Interface, journey and product design alongside engineering.
Mobile
Connected mobile products built next to the platforms behind them.
QA and release
Testing, review and release practice as part of delivery.
Cloud and infrastructure
Environments, deployment, monitoring and recovery.

Cloud architecture, environments and operational controls are covered in more detail on infrastructure and reliability.

Evidence

Platforms, integrations and technically demanding product work.

A selection of Yeti work chosen for its scale and technical demands rather than its styling. Each case study describes the product, the business problem it solves and how it is used.