.NET · Docker · Kubernetes
.NET, Docker & Kubernetes, built and run by one team
We write your software in .NET, pack each part of it into a Docker container, and run it on Kubernetes, where a crashed piece restarts on its own and a new version replaces the old one a copy at a time. It's the setup behind the ERP two of our engineers, working with AI agents, rebuilt for a Michigan manufacturer in about five months, and behind the client systems we host and run today.
Watch it heal itself
Kubernetes keeps your .NET app running when things go wrong
Your software runs as several identical copies spread across servers. Kubernetes checks each copy's health, starts more when traffic climbs, and when a server fails it starts that server's copies again on the others while the rest keep serving.
readynot responding
readynot responding
readynot responding
- 01
Steady
Three copies of the app, one per server. None gets traffic until its health check passes.
- 02
Busy
Traffic climbs. Kubernetes starts more copies and spreads the load across them.
- 03
A server fails
One server stops answering. Its copies start again on the healthy servers, and traffic keeps flowing to the rest.
- 04
Back to normal
The server returns, traffic settles, and the extra copies are removed so you don't pay for idle capacity.
copies of Quest Industries' ERP API in production, each health-checked before it gets traffic
containerized services in LeadStack, our own CRM, on Docker and Kubernetes
client systems we host and fully manage, with automated releases, Sentry and uptime monitoring
An illustrative run. Scaling out and restarting failed copies are standard Kubernetes behavior; how many copies each system runs is set per client.
What Each Piece Does, in PlainEnglish
The tools behind every system we build and run, and why we use them.
.NET
Microsoft's framework for the part of your software you don't see: business rules, database work and APIs. Modern .NET runs on Linux, which is what lets it live in a container. Our newest systems run on .NET 10.
Docker
Each part of the system is packed, with everything it needs to run, into one container image. The same image runs on a laptop, in testing and in production, so "it worked on my machine" stops being an excuse.
Kubernetes
Runs the containers across a group of servers. It keeps the right number of copies running, checks their health, restarts anything that fails and swaps in new versions one copy at a time.
Rancher
One console for all our Kubernetes clusters, so our team can see and manage every client system from the same place.
Argo CD
Keeps what's running in step with what's written in Git. A release is a reviewed change to a file, and going back is undoing that change.
Our Cloud or Yours
We run clusters on our own infrastructure, or on AWS, Microsoft Azure or Google Cloud when that suits you better.
Built and Run for RealClients
What the problem was, what we did, and what changed.
Quest Industries
Mold tooling and machining, Michigan
Problem: Quoting and jobs ran on an old ERP, a workflow platform and Excel workbooks, on servers in the building that needed replacing every four to five years.
What we did: Two engineers working with AI agents built one .NET 10 system. The back end and its helpers (a CAD reader, a document converter, an AI intake agent) run as containers on Kubernetes, released by GitHub Actions and Argo CD.
Result: 1,875 code changes in five and a half months, no more server refresh, and quotes go to customers from the new system every day.
Petra Medical College
Healthcare career college, Arkansas
Problem: A previous firm had spent two years on their online school with little to show for it.
What we did: Built staff, partner and student portals on .NET and PostgreSQL, with a Kubernetes pipeline on Rancher and Argo CD that let us ship changes quickly through the final months.
Result: Delivered in five months, on time and under budget. We host and run it today.
American Allied Health
Online healthcare training
Problem: Two years with an outside firm had produced minimal progress on a new online school.
What we did: Rebuilt it in .NET and handled all the DevOps: every part containerized and released through Azure DevOps and Argo CD onto Kubernetes, managed with Rancher.
Result: Delivered in seven months, and average monthly revenue rose more than 20% after launch. We still host it.
LeadStack
Our own CRM for lending and marketing teams
Problem: Prime, the CRM we built for lenders like CashCall and New American Funding, was never designed to run in the cloud or serve many companies at once.
What we did: Rebuilt it as LeadStack: more than 50 containerized services on Docker and Kubernetes, released through a CI/CD pipeline, with built-in health checks and alerts.
Result: Each service scales on its own, and every event is recorded for a full audit trail.
MedData
Fortune 500 healthcare data company
Problem: Hospital staff needed to screen patients for coverage on an iPad, even with no internet connection.
What we did: Built a .NET back end on Docker and Linux with a SQL Server database, and an app that loads everything it needs into the browser so it keeps working offline.
Result: Their customers saw revenue rise 10% to 35%.
Carszy
Social and safety app for drivers
Problem: A startup wanted drivers to message each other by license plate and report dangerous driving, without sharing personal details.
What we did: Built a .NET back end with PostgreSQL and Redis and real-time chat and calls, deployed with Rancher and Argo CD to Kubernetes on Google Cloud.
Result: A live feed, messaging, audio and video calls, and an admin portal for reviewing reports, all in one app.
Moving your software
How we bring your .NET software onto Docker and Kubernetes
Whether it's an application that has lived on one server for years or a new system, the path is the same.
- 01audit
Look at what you run today
Which parts make up the system, how they're released, where they run, and what breaks when something goes wrong.
- 02docker
Pack each part
Each service gets its own container image, built the same way every time, with nothing installed by hand on a server.
- 03pipeline
Automate the release
Every change is built, tested and approved in a pipeline. Argo CD then rolls it out to Kubernetes.
- 04kubernetes
Run it on Kubernetes
Several copies of each service, a health check before any copy gets traffic, and new versions swapped in one copy at a time. On our servers or in your cloud account.
- 05monitor
Watch it
Sentry error tracking and uptime monitoring report problems straight to the engineers who built it.
- 06run
Hand it over, or let us run it
Your team can take it from there, or we keep running it, as we do for most of our clients.
automated tests that pass before any new version of Quest's ERP ships
code changes to Quest's ERP in five and a half months
months to deliver Petra Medical College's platform, after another firm spent two years
Figures from our Quest Industries and Petra Medical College case studies.
From a Fortune 500 client
MedData's screening app runs on .NET in Docker with a SQL Server database, and keeps working on an iPad with no internet in the middle of a busy hospital.
They are a flexible, open-minded team. If we ask them questions about an issue, they are not defensive. They remain calm, listen, and then propose solutions. This approach makes the process less stressful.
Ready to run your software on Kubernetes?
Tell us what you run today and how you release it. We'll show you what moving it to Docker and Kubernetes would take, and what it would change.
Talk to an engineerCompany Facts
& Figures
Our Office
Get in Touch
Software is what you depend on to get things done. Baytech is who you depend on for software.
