Containers and Kubernetes sized for your team, not for a giant
Containers make applications portable, but a poorly set up cluster brings its own outages and costs. DoneDeploy containerises your applications and runs them on Kubernetes or a simpler service such as Amazon ECS when that fits better, with AI helping draft manifests and review changes. You get a platform your developers can deploy to without needing to become cluster experts.
- Fixed price
- Free first call
- In your own cloud
From design to implementation, and everything after
What goes wrong without it
Works on my machine
Applications behave differently on laptops, test servers and production because each is set up differently.
A cluster nobody dares to upgrade
Kubernetes versions and add-ons fall behind because upgrades were never planned or tested.
Resources wasted or starved
Without sensible requests, limits and autoscaling, some services crash while nodes sit half empty.
What we do
- Write Dockerfiles that build small, reproducible images
- Choose between managed Kubernetes and Amazon ECS based on your needs, and set it up as code
- Package applications with Helm and deploy them with Argo CD
- Use AI to draft manifests and Helm values and to review changes for missing limits, probes and security settings
- Set up autoscaling, ingress with nginx and secrets management
- Plan and test cluster upgrades so they are routine
What you get
- Dockerfiles, Helm charts and cluster configuration in your Git
- A cluster or ECS setup defined as code
- A deployment guide for your developers
- Upgrade and incident runbooks
From first call to continuous improvement
Free first consultation
We learn how your applications are built and deployed today and what you need to run.
Assess
We review your services and recommend Kubernetes, ECS or something simpler, with the reasons.
Fixed-price proposal
We agree the platform, the services to move and the price.
Build and move
Engineers containerise the services and move them in stages, with AI reviewing each change.
Improve after launch
We tune resources, plan upgrades and review cost and reliability over time.
Argo CD
Amazon ECS
NGINX
PrometheusRelated articles
CI/CD for Models and PromptsEvaluation gates, model registries, canary releases and rollback: applying CI/CD discipline to prompts and models in LLM applications.
GPU Nodes on Kubernetes Without Wasting MoneyNode pools, MIG, time-slicing, scale to zero and spot instances: practical ways to keep Kubernetes GPU costs under control for AI workloads.
vLLM vs Ollama vs TGI: Choosing an Inference ServerHow vLLM, Ollama and Hugging Face TGI differ in throughput, hardware support and operations, and which one fits your workload.Often done together
Frequently asked
Do we need Kubernetes?
Not always. For a handful of services, a managed container service such as Amazon ECS can be simpler and cheaper; we recommend Kubernetes when its flexibility pays for its complexity.
Can you take over an existing cluster?
Yes. We review it, bring its configuration under code and fix the risky parts first.
Who runs the cluster afterwards?
Your team, us, or both. We hand over runbooks either way and can operate it under a support package.
Tell us what you run and what you want to change. We reply personally, and the first consultation is free.
Let's talk »