Cloud and DevOps
Tankar designs and runs the cloud infrastructure its products and client platforms depend on, with infrastructure as code, automated deployments, monitoring and backups. The goal is a platform where releases are routine, failures are visible before customers notice, and the monthly bill is understood.
Releases as routine
A platform is working when a release is a normal afternoon rather than an event. Tankar builds pipelines that test and deploy every change, preview environments for review, and rollbacks that take one click.
Visible before it hurts
Monitoring covers errors, latency, saturation and cost, with alerts routed to the people who can act. Runbooks describe what to do, and incidents are reviewed so the same one does not happen twice.
In your account, in code
Everything lives in your cloud account and is defined in Terraform, so the environment can be reviewed in a pull request and rebuilt from the repository.
Typical engagements
What this service usually produces, as deliverables rather than adjectives.
- Cloud architecture and landing zone for a new product on AWS, Azure or Google Cloud
- CI/CD pipelines with tests, preview environments and one-click rollbacks
- Infrastructure as code with Terraform for environments that can be rebuilt from the repository
- Containerisation and Kubernetes or managed container hosting for an existing application
- Monitoring, alerting, error tracking and on-call runbooks
- Cloud cost review with a plan for reserved capacity, right-sizing and cleanup
How it runs
The stages this service goes through, and what you see at each one.
Discovery
Current infrastructure, deployment process, incidents, compliance needs and the cloud bill. Written estimate within 48 hours.
The written estimate follows within 48 hours of the scoped call.
Design
Target architecture, environment separation, access model and the migration or build plan, reviewed with your security owner.
Build
Infrastructure as code, pipelines, monitoring and backups, built in your cloud account with a weekly demo.
Test
Restore from backup, failover, load and a review of access and secrets before anything goes live.
Launch
Cutover with a rollback plan, runbooks and a handover to your team or to Tankar's support plan.
Run
Patching, cost reviews, capacity planning and incident response on an SLA-backed plan.
- Team shape
- A DevOps engineer paired with a project manager, with a security reviewer for access and secrets.
Stack for this service
The technologies this work is usually built on, and why each one is used here.
| Technology | Why we use it here |
|---|---|
| AWS, Azure and Google Cloud | Chosen by where your data must live, what your team already knows and which managed services fit the workload. |
| Vercel | For Next.js sites and applications, global delivery and preview deployments without running servers. |
| Terraform | Environments defined in code, reviewed in pull requests and rebuildable from the repository. |
| Docker | The same image runs in development, CI and production. |
| Kubernetes | Where the workload needs it; managed container services are recommended when it does not. |
| GitHub Actions | Tests, builds and deployments on every pull request with preview environments. |
| Monitoring and error tracking (Sentry, cloud-native monitoring) | Errors, latency and cost are visible on dashboards with alerts before customers report them. |
Selected work
Case studies where this service carried the engagement. Only outcomes with a source are shown.
Own productGovernment and public sectorTenderBazaar: tender discovery and alerts for Indian SMEs
A tender discovery platform that collects listings from central, state and municipal portals into one searchable feed with daily alerts.Services: SaaS product development, Mobile app development and 1 moreRead the case study
Own productTravel and hospitalityTripBNG: a B2B travel booking platform for agents
A booking platform that gives travel agents supplier inventory, quotes, credit limits and settlement reports in one account.Services: SaaS product development, API development and integrations and 1 moreRead the case study
Engagement models that fit
Architecture and migration work is usually fixed price; operations run on a retainer with an SLA.
- Fixed priceA defined scope with a clear end state: an MVP, a website, a well-specified module or an integration.
- Time and materialsEvolving products, research-heavy work such as AI features, and engagements where the backlog is set sprint by sprint.
- Retainer and supportLive products that need maintenance, monitoring, small improvements and a response commitment after launch.
Questions buyers ask
What buyers ask most about this service, answered before the first call.
Tell us what you are building.
NDA on request. Written estimate within 48 hours of a scoped call. Reply within one business day.