Services
Custom software developmentUmbraco developmentWeb developmentCRM developmentERP developmentAI & LLM integration.NET development & modernizationE-commerce developmentIntegrations & automationCloud & DevOpsMaintenance, support & project rescueDedicated teams & white-label
Our Work
Case studiesProducts
About Blog Contact
Azure development

.NET platforms and AI features on Microsoft Azure.

Azure is the natural home for many .NET systems we build. It runs the EM2 event platform’s 8 microservices with Functions, Service Bus and AD B2C, Alliant’s multi-site Umbraco estate, a product hub on Cosmos DB, and Azure OpenAI hints in an EdTech product.

What we build with Azure

Where Azure earns its place.

The kinds of work we use Azure for, based on the projects below rather than a list of everything the technology can do.

Microservices on Azure

ASP.NET Core services with Azure Functions, Service Bus, Key Vault and AD B2C, provisioned with Terraform and Azure DevOps.

CMS and websites on Azure

Umbraco multi-site setups behind Azure load balancers with Blob Storage for media and Azure CI/CD.

Azure OpenAI features

AI features that keep data inside your Azure tenant, with human approval where it matters.

Azure case studies

Results from these projects.

Each one with the client’s problem, our approach and what changed.

Azure FAQ

Azure questions we hear.

Anything missing? Send us your question and an engineer will answer, usually within one business day.

Contact us
Azure or AWS?+

Both work well for .NET. Azure is often simpler if you already use Microsoft 365 and Entra ID; AWS can be cheaper for container-heavy workloads. We have built on both and migrated between them.

Do you use infrastructure as code on Azure?+

Yes. The EM2 platform is provisioned with Terraform and deployed through Azure DevOps Pipelines, with Application Insights for monitoring.

Can you add Azure OpenAI to our product?+

Yes. In TutorPro, Azure OpenAI writes exercise hints that teachers approve before students see them.

Start a project

Tell us what you are building with Azure. We come back with a plan and a price.

A spec, a Figma file or three paragraphs is enough to start.

  1. First reply · from an engineer, not a sales rep
  2. 30-min call · with Roman, our CTO, to clarify scope
  3. After the call · a written proposal with plan, team and price
Roman Oleksuk
Roman Oleksuk, CTOPrefer to talk? Pick a slot in Roman's calendar
We reply from a human mailbox. No newsletters. Your brief stays under NDA on request. We use your details only to reply; see our privacy policy.