Kubernetes platform services
Plan, build and run production Kubernetes and Red Hat OpenShift platforms, in your data centre or in the cloud, with the security, resilience and day-two operations your applications depend on.
Kubernetes that is ready for production, and stays that way
Kubernetes has become the standard way to run modern applications. Banks, mobile financial services, telecom operators and government agencies in Bangladesh now run customer-facing systems on it.
Installing a cluster takes a day. Making it secure, observable, recoverable and easy for development teams to use takes design and discipline. Keeping it that way through three Kubernetes releases a year takes a team.
Our CNCF and cloud-certified engineers design, build and run platforms on Red Hat OpenShift, on upstream Kubernetes and on the managed services of AWS, Azure and Google Cloud. We work in your data centre or in the cloud, alongside your team, and we stay for day two: upgrades, monitoring, backups and support.
- Years in business
- 35+
- Certified engineers
- 50+
- Projects delivered
- 200+
- Client organisations in six sectors
- 33
Signs you need a platform, not just clusters
Most organisations start with a cluster or two for a pilot. These are the signs it is time to run Kubernetes as a platform.
Every cluster is different
Each team or vendor built its own, so versions, tools and security settings vary, and nobody can support them all.
Upgrades keep slipping
Clusters run versions that are out of support, because every upgrade is manual and feels risky.
Security findings pile up
Scans flag vulnerable images and broad permissions faster than anyone can fix them, and auditors are asking questions.
Developers wait for environments
A new namespace, pipeline or database takes a ticket and a week, so teams build their own workarounds.
Recovery is untested
Backups exist, but nobody has restored a whole application or failed over to the disaster recovery site.
Licence costs keep rising
Virtualisation renewals have jumped, and you want one platform that runs virtual machines and containers together.
Our Kubernetes services
From the first design to running the platform every day. Use one service, or all of them.
Platform strategy and architecture
Choose the right platform, size it and plan how it will be run, before you buy hardware or subscriptions.
Learn more
Platform implementation
Production clusters on bare metal, VMware, OpenStack or the cloud, built as code and tested before handover.
Learn more
Red Hat OpenShift
Install, upgrade and support OpenShift, including its virtualisation, GitOps, security and AI features.
Learn more
Operations and support
Monitoring, upgrades, patching and incident response by our engineers, with 24/7 cover when you need it.
Learn more
Platform engineering and GitOps
Self-service templates, a developer portal and GitOps, so teams ship without waiting on tickets.
Learn more
Backup and disaster recovery
Application-aware backups, replication to a second site, and failover you have actually tested.
Learn more
Virtualisation and VMware migration
Run virtual machines beside containers on one platform, and move off VMware in planned waves.
Learn more
AI and GPU platforms
Share GPUs between teams and serve models in production, on premises or in the cloud.
Learn more
Kubernetes security
Harden clusters, control images and policies, and protect workloads while they run.
Learn moreDay 0, day 1, day 2
Most of a platform's life is day two
Design and build take weeks. Running the platform takes years. Kubernetes releases a new minor version about three times a year and supports each for about a year, so upgrades, patching and capacity planning never stop. We plan for day two from the first workshop.
- Day 0: design
- Requirements, platform choice, architecture, sizing and the operating model.
- Day 1: build
- Clusters and platform services installed as code, then tested before go-live.
- Day 2: operate
- Monitoring, patching, scaling, backups and support, for as long as the platform runs.
- Upgrades
- A new Kubernetes minor version about three times a year, each one tested before it reaches production.
Platform options
Which Kubernetes is right for you
There is no single right answer. We help you choose on cost, skills, support and where your data has to live, and we build and run all four. Upkeep shows how much running each one asks of your own team.
01
Red Hat OpenShift
Kubernetes with the rest of the platform included.
Console, registry, monitoring, logging, GitOps, pipelines, virtualisation and security are tested together, upgrades are automated, and Red Hat supports it as one product.
Best for: Regulated institutions that want one supported platform on premises.
UpkeepMedium02
Upstream Kubernetes
Open-source Kubernetes, assembled from CNCF projects.
No subscription fees and full control of every component. Your team, or ours, chooses, integrates and upgrades each piece.
Best for: Teams with strong engineering skills and tight budgets, such as universities and research groups.
UpkeepHigh03
Managed Kubernetes in the cloud
Amazon EKS, Azure AKS or Google GKE.
The cloud provider runs and patches the control plane. You choose when to upgrade, run the worker nodes and add-ons, and pay for what you use.
Best for: Workloads your policies allow to run in a public cloud region.
UpkeepLow04
Hybrid
One platform across your data centre and the cloud.
The same platform and tools in every location, managed from one place, for disaster recovery, extra capacity or a gradual move to the cloud.
Best for: Organisations with data that must stay in the country and workloads that can move.
UpkeepHigh
How a platform programme runs
The four phases we use across all our work, applied to Kubernetes.
01
Assess and plan
Review your applications, infrastructure, skills and rules, choose the platform, and agree a roadmap and budget.
02
Design
Design the clusters, networking, storage, security, delivery and operating model, and how the platform will grow.
03
Build and migrate
Build the platform as code and test it, prove it with a pilot application, then move workloads in waves.
04
Operate and improve
Run, patch and upgrade the platform with your team, report on service levels and keep improving it.
How we build platforms that last
A platform carries many applications for many years. These practices keep it dependable and affordable to run.
01
Everything as code
Clusters, platform services and policies are defined in Git and applied by automation, so any environment can be rebuilt and audited.
02
Upgrades are routine
We plan the upgrade path from day one and rehearse it, so clusters stay on supported versions without drama.
03
Secure by default
Least-privilege access, trusted images, network policies and audit logs are part of the build, with Bangladesh Bank's ICT security guideline in mind for financial institutions.
04
Built for your team to run
We document, pair and train as we build, so your engineers can operate the platform with us or without us.
05
Open standards, no lock-in
We build on CNCF projects and open interfaces, so applications and skills move between platforms and clouds.
06
Measured by service levels
We agree what matters, such as availability, recovery time and time to a new environment, then measure and report it.
Technology we work with
We are not tied to one vendor. We choose each component for support, skills and fit, and keep the list short.
Platforms
- Red Hat OpenShift
- Kubernetes
- Amazon EKS
- Azure Kubernetes Service
- Google Kubernetes Engine
- OpenShift on AWS and Azure
Networking and traffic
- OVN-Kubernetes
- Cilium
- Calico
- Gateway API
- Istio
- NGINX
- F5 BIG-IP
- MetalLB
Storage and data
- OpenShift Data Foundation
- Ceph with Rook
- NetApp Trident
- Portworx
- Hitachi storage plug-ins
- Dell Container Storage Modules
Delivery
- Argo CD
- Flux
- Tekton
- GitLab CI
- Helm
- Kustomize
- Terraform
- Ansible
Observability
- Prometheus
- Grafana
- Loki
- OpenTelemetry
- Tempo
- Alertmanager
Security
- Red Hat Advanced Cluster Security
- Kyverno
- OPA Gatekeeper
- Falco
- Trivy
- Sigstore
- HashiCorp Vault
- cert-manager
- Keycloak
Partners we build on
Platforms for the sectors we know
Each sector has its own rules on data, uptime and audit. Our sector pages show where a Kubernetes platform fits.
Banking and finance
Always-on platforms for digital banking, payments and the services around the core, with disaster recovery built in.
Government
Sovereign platforms for citizen portals, APIs and national systems, hosted in the country.
Healthcare
Highly available platforms for clinical and patient-facing applications, with controlled releases.
Education and research
Shared platforms for research software, teaching systems and GPU computing, on open foundations.
Development partners
Reliable platforms for programme systems that small teams can run, in the country or in the cloud.
Ways to work with us
Platform assessment
A review of what you run today and what you need, ending with a platform choice, a design, a budget and a roadmap.
Build project
We design and build the platform against an agreed scope, timeline and acceptance tests, then hand it over.
Managed operations
We run the platform day to day under agreed service levels, with 24/7 cover where you need it.
Engineers in your team
Platform and DevOps engineers who join your team, pair on real work and train your people.
Common questions
Should we use OpenShift or upstream Kubernetes?
It depends on what you want to own. OpenShift costs more in subscriptions, but it includes and supports the console, registry, monitoring, GitOps, virtualisation and security tools, and it automates upgrades. Upstream Kubernetes has no licence fees, but your team chooses, integrates and maintains every component. We build and run both, and compare them on your workloads and budget.
Platform strategy and architectureCan Kubernetes run in our own data centre?
Yes. Most of the platforms we build run on premises, on bare-metal servers, VMware or OpenStack, because the data has to stay in the country or close to core systems. They can also be linked to cloud clusters for disaster recovery or extra capacity.
Platform implementationHow long does it take to build a production platform?
Installing the software takes days. Most of the time goes into the work around it: getting servers and networks ready, connecting identity, storage and security tools, and testing. The strategy assessment gives you a dated plan for your environment.
Do you support the platform after it goes live?
Yes. Our support plans range from expert help for your own platform team to fully managed operations with 24/7 cover, delivered by engineers who know your platform.
Operations and supportCan our VMware virtual machines move to Kubernetes?
Many of them can. OpenShift Virtualization and KubeVirt run virtual machines on the same platform as containers, and migration tools move them in planned waves. We assess which machines should move, which should be containerised and which should stay where they are.
Virtualisation and VMware migrationDo our applications need to change to run on Kubernetes?
Usually a little. Most applications need their configuration, logging and health checks adjusted to run well in containers. Our application modernisation team does that work, from containerisation to full re-architecture.
Containerisation and replatformingPlan your Kubernetes platform
Tell us what you run today and where you want to be. We'll suggest a first step, whether that is an assessment, a new platform or support for the one you have.