Performance and reliability
Cloud, DevOps and cost
I set up or take over your infrastructure on Google Cloud or AWS: infrastructure as code, CI/CD, containers, monitoring, database high availability and backups. Along the way I look for the money you're wasting. I ran the production servers for a media group's products across both clouds.
- Timeline
- Agreed per project, then optional monthly care
- Price
- Fixed-scope quote; optional monthly retainer
- Engagement
- Fixed-scope project
Is it a fit?
For
- Teams still deploying by hand or over SSH
- Startups moving off shared hosting or a single server
- Companies whose cloud bill has grown faster than their traffic
Not for
- Companies with an established SRE team: I'm happy to review their work, but they don't need this
What you get
- Infrastructure as code (Terraform) for every environment
- CI/CD with tests, preview environments and one-step rollback
- Containerized services and a documented deploy process
- Monitoring, logging and alerting that someone will actually read
- Backups with a tested restore, and a written recovery plan
- A cost report: savings made, and the ones still available
How it runs
- 01
Review
Inventory what runs where, what it costs, how it's deployed and how it would be restored.
- 02
Codify
Describe the infrastructure as code so every environment can be rebuilt from the repository.
- 03
Automate
CI/CD with tests and previews; deploys become routine instead of events.
- 04
Observe and optimize
Dashboards and alerts first, then right-sizing and caching where the numbers say it pays.
Typical stack: Google Cloud · AWS · Terraform · Docker · GitHub Actions · NGINX · PostgreSQL · MySQL · Redis · Grafana · Prometheus
Questions
Which clouds do you work with?
Mainly Google Cloud and AWS. I also deploy to Vercel, Railway and DigitalOcean, and to GPU clouds such as RunPod for model serving.
Do you offer ongoing server care?
Yes, as a monthly retainer: updates and patches, monitoring, backup checks, cost reviews and small changes.
How do you approach cutting costs?
By measuring first: right-sizing instances, removing idle resources, caching in front of expensive services, and using committed or spot capacity where the workload allows.
Can our data stay in the Gulf?
Yes. I build the infrastructure in cloud regions inside the UAE or Saudi Arabia, and keep backups, logs and monitoring data there too, so data residency holds end to end, not only for the main database.
More in performance and reliability
- Performance and Core Web Vitals audit: Find out in five working days exactly why your application is slow, and what to fix first.
- Launch-day readiness: Your biggest day shouldn't be your first real load test.
Tell me about your project.
A short brief is enough to start. I’ll reply with questions, a suggested first step and when I could begin.