Cloud & DevOps
Infrastructure defined in code
We set up cloud infrastructure that is defined in code, deployed automatically and monitored properly: AWS and Google Cloud environments in Terraform, CI/CD pipelines, containers and Kubernetes where scale justifies it, and the logging and alerting that tell you something is wrong before your users do.
What we can build
- AWS and Google Cloud environments defined in Terraform
- Containerised deployments, with Kubernetes where scale justifies it
- CI/CD pipelines with automated checks
- Monitoring, logging, alerting and backups
- Cost review and right-sizing
Typical projects
- 1.Moving a manually configured server to a reproducible cloud setup with staging and production
- 2.A deployment pipeline that runs tests, applies migrations and releases with a rollback path
- 3.Alerting and dashboards for a system that previously failed silently
Relevant technologies
- AWS
- Google Cloud
- Terraform
- Docker
- Kubernetes
- CI/CD
Offshore software development
Why work with a software team in Sri Lanka
Working hours that overlap yours
We work on Sri Lanka time, UTC+5:30, with no daylight saving. That covers the working day across Asia and the Middle East, mornings in Europe and afternoons in Australia and New Zealand, and we schedule early or late calls for the Americas.
Written down, in English
Scope, decisions and progress are written down in English and kept in your project tools, so you can see where things stand from any time zone without chasing anyone.
Engineers, not account managers
You talk directly to the engineers building your software. Technical questions get technical answers, not a relay through a sales layer.
Scoped before work starts, owned by you after
Fixed-scope projects or ongoing monthly work, agreed in writing before anything starts. You own the source code, infrastructure and deployment pipelines.
Questions
Cloud & DevOps: common questions
Do you work with AWS or Google Cloud?
Both. We define environments in Terraform, so they can be reviewed, versioned and rebuilt rather than configured by hand.
Do we need Kubernetes?
Often not. We use managed services and simple container deployments by default, and Kubernetes when the scale or the team justifies it.
Can you reduce our cloud bill?
We review what is running against what is used and right-size it. How much that saves depends on the setup, so we report what we find before changing anything.