Comptech Container Platform
An enterprise Kubernetes platform with GitOps, a private registry, security scanning and tested DC/DR failover, supported locally by Comptech.
Overview
One platform for containers and VMs, across two sites
Comptech Container Platform gives banks and enterprises a single, governed platform to modernise applications, host vendor software and run DevSecOps, on hardware they control.
Clusters in the primary data centre and the DR site are managed together, applications and their storage are replicated between sites, and every change flows through Git. Comptech engineers in Bangladesh design, build and support it.
Use cases
Built for regulated application estates
Core banking modernisation
Move surrounding channels and services off monoliths step by step, without a big-bang rewrite.
Microservices
Independently deployable services with service mesh, tracing and automated delivery.
Vendor application hosting
Run vendor-supplied containers safely, with images checked before they reach production.
DevSecOps
Pipelines, signed images and policy checks so security is part of every release.
Features
Run and recover across sites
Multi-cluster management
DC and DR clusters managed from one place, with consistent policies and placement.
Tested DR
Ceph with Ramen storage replication, with tested failover and failback of applications between sites. NetApp ONTAP with Trident is also supported.
VMs alongside containers
KubeVirt runs virtual machines on the same platform, so legacy workloads move without a rewrite.
Delivery and security
Ship safely, every time
GitOps and CI
Argo CD keeps clusters in sync with Git; Tekton runs build and test pipelines inside the platform.
Private registry
A private Quay registry with vulnerability scanning, replicated from DC to DR.
Supply-chain security
Runtime and compliance scanning, a signed image supply chain, and quarantine-then-promote intake of vendor images.
Observability
Grafana dashboards, service mesh visibility with Kiali, tracing with Tempo/Jaeger, and central log aggregation.
Single sign-on and secrets
Keycloak SSO with AD/LDAP and MFA, group-based roles, and secrets in an OpenBao vault.
Local support
Comptech engineers in Bangladesh, with Bronze, Silver and Gold SLAs.
Architecture
Two sites, one platform
Production runs in the primary data centre. Container images, application definitions in Git and persistent volumes are replicated to the DR site, so applications can fail over and fail back in a controlled, tested way.
- Primary site (DC)Kubernetes clusters running production workloads.
- DR siteStandby clusters kept in sync by GitOps and storage replication.
- ReplicationCeph/Ramen or NetApp volumes and Quay images copied between sites.
- Failover and failbackApplications moved between sites as a tested, repeatable procedure.
Components
What's in the platform
Orchestration
- Components
- Kubernetes, multi-cluster management
- What it does
- Runs containers and manages DC and DR clusters together
Delivery
- Components
- Argo CD, Tekton
- What it does
- GitOps deployment and CI pipelines
Registry
- Components
- Quay
- What it does
- Private image registry with vulnerability scanning, replicated to DR
Storage and DR
- Components
- Ceph, Ramen, NetApp Trident
- What it does
- Persistent storage with replication, failover and failback
Virtualisation
- Components
- KubeVirt
- What it does
- Virtual machines alongside containers
Observability
- Components
- Grafana, Kiali, Tempo, Jaeger
- What it does
- Dashboards, service mesh, tracing and logs
Identity and secrets
- Components
- Keycloak, OpenBao
- What it does
- Single sign-on, MFA, roles and secrets vault
Included
With every Comptech product
On premises or private cloud
Runs in your own data centre, so data stays in the country. Open formats and standard APIs avoid lock-in.
Single sign-on
Keycloak with AD/LDAP, MFA and group-based roles across every tool.
Secrets vault
Credentials and keys held centrally in an OpenBao vault, not in configuration files.
DC/DR design
Designed for a primary data centre and a disaster recovery site.
Local support and SLAs
Comptech engineers in Bangladesh, with Bronze, Silver or Gold SLAs.
Pilot and training
A pilot in 4 to 6 weeks, plus training for your team.
From pilot to production
01
Discover
Agree the first use case, the systems involved and the success criteria.
02
Pilot
Deploy on your infrastructure and prove the use case in 4 to 6 weeks.
03
Production
Add the DR site, single sign-on and the remaining teams and workloads.
04
Support
Local support under a Bronze, Silver or Gold SLA, with training for your team.
Questions
Can it run our existing virtual machines?
Yes. KubeVirt runs VMs next to containers, so you can move workloads first and modernise them later.
VMs on KubernetesHow long does a pilot take?
A typical pilot runs 4 to 6 weeks on your hardware or private cloud, with one agreed use case and success criteria set at the start.
What support do you offer?
Local support from Comptech engineers in Bangladesh, with Bronze, Silver and Gold SLA levels. We also train your team to run the platform day to day.
Are we locked in?
No. The platforms use open formats and standard APIs, so your workloads and data stay portable.
Request a pilot
Tell us about the applications you want to modernise and your DC/DR setup. We'll plan a 4 to 6 week pilot.
Related services