What we do
CompTech Lab is a focused systems integrator. We deliver four practice areas end-to-end — cloud platforms, application modernization, end-to-end security, and operations & managed services — into four industries where regulation, audit, and platform discipline define the shape of the engagement: banking and financial services, insurance, telecom, and public sector.
How we deliver
Every engagement runs through the same five-phase discipline — assess, design, deploy, operate, hand over — sized to scope. We do not run open-ended retainers. The endpoint is a platform your operations team owns, with documentation deep enough to outlast staff turnover and a residual-risk register your audit function can sign for.
What you keep after we leave
- A reference architecture specific to your environment, with architecture decisions (ADRs) for every non-obvious choice and the trade-offs considered for each.
- A runbook set indexed by failure mode — not a generic wiki, but procedures verified against the system as it actually runs.
- An operating model your platform team can sign for — on-call structure, escalation paths, alert hygiene, postmortem culture.
- A residual-risk register — what we hardened, what we left in place by design, and what your operations team should watch for in the next 12 months.
What we believe
- Engineering depth beats scale. A small senior team that has done the work before will out-deliver a large team that hasn’t. We engage where this is true.
- GitOps-shaped from day one. Desired state in Git, reconciliation in the cluster, drift treated as a defect — never an out-of-band patch.
- Identity is platform. Identity is not an application your team integrates with — it is the boundary your platform is shaped around.
- Security is engineering work. Shift-left in the pipeline, shift-right at runtime, evidence at the source. Not a quarterly slide.
- Documentation is a primary deliverable. The handover document is the engineering work, not a closeout task.
What we don’t do
- We don’t replace your engineering team. Our default is a structured handover; we run optional bridge managed services where your team is not yet ready to operate, but we do not aim to stay forever.
- We don’t pitch transformation programmes with five-year horizons. We engage against bounded outcomes and let the next engagement be the next decision.
- We don’t engage where the platform-discipline edge is missing. If the workload doesn’t have a regulatory, identity, or platform-engineering dimension, we’re probably not the right firm.
The technologies we operate
Cloud platforms: Red Hat OpenShift, AWS, Microsoft Azure, Google
Cloud Platform, Advanced Cluster Management, OpenShift GitOps, Argo CD, Terraform,
Ansible.
Identity & security: WSO2 Identity Server, Ping Identity,
Keycloak, HashiCorp Vault, External Secrets Operator, RHACS, Acunetix, Invicti,
cosign / sigstore, OPA, cert-manager.
Integration & data: WSO2 API Manager, WSO2 Micro Integrator,
MuleSoft, Camunda, Temporal, Apache Kafka, Apache Spark, S3-compatible object
storage, Iceberg / Delta lakehouse formats.
AI & modernization: OpenShift AI, NVIDIA NIM, vLLM, Triton,
Ollama, MCP, LangChain, JBoss EAP, Spring Boot, Quarkus, Node.js.
Operations & observability: Datadog, Grafana / Prometheus /
Loki / Tempo, OpenTelemetry, Kiali, Istio, OADP, Velero, GitLab Enterprise, Quay,
Nexus.
Get in touch
Engagements start with a short note describing what you’re building. We reply with a concrete first-two-weeks scope and a definition of done. Send us a note →