Below is what we actually do day to day. We try to keep the list short and the descriptions honest. If something here matches what you need, get in touch.
Software engineering ¶
We write backend services in Java, Kotlin, Go, and Groovy. Most of the work falls into a few buckets: REST and gRPC APIs, distributed systems handling high request volumes, and the occasional batch job that has to be reliable more than fast.
We also build crawlers and parsers. Real ones, not the kind that break the first time a target site changes its markup. That means proper retry logic, rate limiting, fingerprint rotation when needed, and storage that does not lose data if a worker dies mid-job.
Data pipelines and analytics ¶
ETL and ELT pipelines, batch and streaming. Kafka for transport, Elasticsearch and Postgres for indexing and querying, Parquet on object storage when the data is cold. We default to managed services when the cost works out, and run things ourselves when it does not.
Reporting, dashboards, data lakes: same approach. Pick the smallest thing that solves the problem, instrument it properly, document the schema, and let the team that owns the data own the pipeline.
Cloud adoption ¶
Migrations and greenfield builds on AWS, GCP, and OpenStack. We do the architecture, the IaC (Terraform and Terragrunt), the network design, and the boring parts: IAM, organisation policies, cost allocation, audit logs.
Multi-cloud is a tool, not a goal. We use it when there is a real reason (regulatory, latency, vendor risk) and avoid it when the only reason is “in case we change our mind later”.
Kubernetes ¶
Cluster setup and operations on GKE, EKS, OpenShift, Rancher, and self-hosted k3s. Helm charts written so other people can read them. CI/CD wired in with whatever the team already uses (Jenkins, GitLab CI, GitHub Actions). Service mesh only when the traffic patterns actually justify it.
We pay attention to the things that bite later: pod disruption budgets, resource requests that match reality, secrets handling, image provenance, and a sane upgrade story.
DevOps ¶
CI/CD, infrastructure automation, GitOps workflows, monitoring, alerting, incident response. The aim is short feedback loops and a system the on-call engineer can debug at 3am with a phone and a coffee.
Tools we use often: Ansible, Terraform/Terragrunt, ArgoCD, Prometheus, Grafana, Loki, OpenTelemetry. We do not have a strong opinion about the brand of the tool, only that the team using it actually understands it.
Security and compliance ¶
- Data protection. Privacy controls, GDPR work, data governance setup. Documented properly so an audit does not turn into a fire drill.
- DPO as a service. We act as outsourced Data Protection Officer: regulatory contact, DPIAs, breach response, internal training.
- Vulnerability assessments. Penetration testing, code audits, infrastructure scans. Findings come back ranked by exploitability and blast radius, with concrete fixes, not a 200-page PDF nobody reads.
Digital marketing ¶
Affiliate program operations and online campaign management. Tracking, attribution, and the routing infrastructure behind it. Useful when you already have offers to push and need the plumbing to work.