Pruthvik
AI / Cloud Engineering Lead
Pruthvik leads AI and cloud engineering, including the cloud infrastructure the teams build and deploy on.
Cloud and DevOps on AWS, Google Cloud and Azure
The part of software people notice only when it fails: where it runs, how it gets released, and what happens when something breaks. Our in-house team in Rajkot, India sets this up for new products and sorts it out for existing ones, led by Pruthvik, our AI / Cloud Engineering Lead.
- Clouds
- AWS · Google Cloud · Azure
- Tools
- Docker · Kubernetes · CI/CD
- Lead
- Pruthvik, AI / Cloud Engineering Lead
Who this suits
- Products moving from one server or shared hosting to something that can grow.
- Teams whose releases are manual, slow or frightening.
- Companies with a cloud bill that keeps rising and nobody can explain.
What we take on
What we set up and look after.
Cloud set-up
Servers, databases, storage and networks set up for your product, with access held in your company's name.
Migrations
Moving from shared hosting, on-premise servers or another cloud, in steps you can roll back.
Release automation
CI/CD pipelines, so each release is built, tested and deployed the same way every time.
Containers
Docker and Kubernetes where they earn their complexity, and simpler hosting where they do not.
Serverless
Functions and managed services for work that comes in bursts.
Monitoring and backups
Alerts, logs, error tracking and backups that have been tested by restoring them.
Security basics
Least-privilege access, secrets kept out of code, updates and HTTPS.
Cost control
Finding what you pay for and do not use, and sizing the rest to real traffic.
Technologies: AWS · Google Cloud · Azure · Firebase · DigitalOcean · Docker · Kubernetes · Terraform · GitHub Actions · Nginx · Linux
Related
Useful next reads
How an engagement runs
- You tell us what you need and what exists today.
- We agree a written scope, or a dedicated team, with you.
- We build in short cycles you review, then release and support.
Questions
Before you get in touch
Which cloud should we use?
It depends on what you run, what your team knows and any rules you must follow. If you have no strong reason, we compare the options for your product and its expected traffic before you commit.
Can you move us to the cloud without downtime?
Often with very little. We copy the system across, test it, keep the old one ready to return to, and switch at a quiet time. We tell you beforehand if your system needs a planned stop.
Who holds the accounts?
We recommend your company holds the cloud accounts and billing, and gives our team the access the work needs.
Can you reduce our cloud bill?
We review what you run and show what can be removed or resized, and what each change would save, before anything is touched.
Start a project
Tell us what you run today.
Where your product is hosted, what is going wrong, and what you want to change.
What happens next
Your message goes to Ghanshyam Gadhiya, partner and CEO, who replies by email. If it is easier, you can also reach us on WhatsApp.