01What managed DevOps services usually include
- CI/CD pipelines: automated builds, tests and deployments, kept working and improved
- Cloud infrastructure: servers, networks and databases, managed as code
- Monitoring and alerts: uptime, errors and performance, watched by a person
- Backups: regular backups, with restores tested
- Security updates: patches and access reviews on a regular schedule
- Incident response: someone to act when something breaks, within agreed times
- Cost review: regular checks to keep the cloud bill under control
- Reporting: a short monthly summary of what was done and what is next
02Managed service, in-house team or one-off project?
Managed DevOps service
- Works well when
- You want reliable operations without building a team
- Watch out for
- Keep accounts, code and documentation in your own name
In-house DevOps team
- Works well when
- Infrastructure is central to your business and you can hire and keep the people
- Watch out for
- Hiring time, cover for leave and the cost of a team
One-off project
- Works well when
- You need a platform built once and can run it yourself
- Watch out for
- Nobody looks after it afterwards unless you plan for it
03What to ask a provider before you sign
- Will everything run in our own cloud accounts and repositories?
- What is included each month, and what costs extra?
- What are the response times, and what counts as urgent?
- Who is on call, and when?
- How do you document the setup, so another team could take over?
- How do you report, and how often?
- How do we end the arrangement, and what do we keep?
04Red flags
- The provider holds the cloud accounts, so you cannot leave easily
- No written response times
- No documentation, so only they understand your setup
- Vague monthly scope that grows into extra charges
- No regular reports or reviews
05Working with a provider in India
A provider in India can offer a lower cost than many Western teams for the same scope, and can cover hours that overlap with your day. Agree the overlap hours, the on-call arrangement and how urgent incidents are handled outside those hours before you start.
06How MOUNTSMY runs managed DevOps
We take on the daily work of your delivery pipelines, cloud, monitoring, backups and updates, while the accounts and code stay yours. We agree response times and scope in writing, document the setup and send a short monthly report. You can also hire a DevOps engineer by the hour or as a dedicated engineer.
?Frequently asked questions
What is the difference between managed DevOps and managed cloud?
They overlap. Managed cloud focuses on running your cloud infrastructure, while managed DevOps also covers your delivery pipelines and release process.
Do we keep control of our cloud accounts?
You should. We recommend your accounts and code stay in your name, with the provider added as a manager, so you can leave at any time.
How is a managed service priced?
Usually a monthly fee set by the size of the environment and the response times you need. We give a written quote after a short review.
Can you take over a system that someone else built?
Yes. We start with a written review of the setup, then a plan for looking after it.
Do you offer 24/7 cover?
Cover hours depend on the plan. We agree what counts as urgent and who responds, and when, in writing at the start.