Managed DevOps team
A four-person DevOps team runs your cloud platform and makes sure your applications deploy and run reliably. We do not write applications. We work only on infrastructure, cloud and DevOps.
Who is on the team and what they own
-
Lead
accountableResponsible for
Platform architecture, quality and security, risk decisions, escalations, planning and a regular overview of the platform. The one person accountable to you for the result.
What you get
Main contact, recommendations and decisions, a regular overview
-
Middle
Responsible for
Runs and changes the platform: CI/CD pipelines, Kubernetes, infrastructure as code, monitoring, updates, incidents and documentation. Works independently, including on harder tasks. Delivers what the lead designed.
What you get
Finished changes, closed requests and platform improvements, harder tasks and incidents
-
2× Junior
Responsible for
The same work as the middle: running and changing the platform, CI/CD, Kubernetes, infrastructure as code, monitoring, incidents and documentation. The difference is experience: less autonomy, simpler tasks, supervised by the middle and the lead.
What you get
Finished changes and closed requests, more team capacity
We assign requests by complexity: routine and smaller tasks go to the juniors, harder ones to the middle, and the lead handles decisions and risks. You never have to decide who gets a task. When a team member is ill or on holiday, another member with the same role covers for them, with no impact on you.
How we work together
Your main contact is the team lead, who owns the result, priorities, risks and the regular platform overview. Day to day, though, you talk to the whole team directly. You can hand tasks to the middle and the juniors and ask them for details without routing every question through the lead. Changes of scope, priorities and bigger decisions are confirmed by the lead.
- Requests
- A shared Slack or Teams channel and the ticketing system of your choice. Every request has a requester, a priority and a status.
- Rhythm
- A short weekly sync of 15 to 30 minutes and a monthly review with the lead: what happened, what the risks are and the plan for the next period.
- Escalation
- Junior, middle, lead. For critical incidents the lead contacts you directly.
- Hours
- Working days, 8:00 to 17:00 Central European Time. Out-of-hours on-call is not included and can be agreed separately.
What is included and what is not
Included in the monthly price
- Running and maintaining CI/CD, Kubernetes and the related infrastructure
- Infrastructure as code and everyday changes on request
- Updates, patches and basic security hygiene
- Monitoring, alerts and first response to incidents
- Documentation and runbooks
- A monthly review with the lead, and a short written summary if you want one
Not included, quoted separately
- Larger projects and architecture changes, such as a new landing zone or a cloud migration. We run them as separate fixed-price projects.
- 24/7 on-call. It can be agreed separately.
- Cloud costs, licences and third-party tools.
- Application development. We do not write applications; we work only on infrastructure, cloud and DevOps.
Fixed-price projects are listed under other services.
Service levels
Once a month we meet with the lead and go through what was done, what incidents there were, what risks we see and what we recommend next. If you want, we also write a short summary. We do not send reports nobody reads. Service levels apply during working hours.
- 4 hFirst response to a normal request, within 4 working hours
- 1 hFirst response to a critical incident, within 1 working hour, with a status update every 2 hours until it is resolved
- 3 daysSmall change completed, within 3 working days
- 1×Monthly review with the lead, once a month, at a time that suits you
Price and terms
CZK 263,000 per month excl. VAT for the work of a four-person team (lead, middle, two juniors) within the scope above.
- Invoiced monthly, a fixed amount regardless of how many in-scope requests you send
- Minimum term of 12 months
- Indexed once a year to IT wage growth (Czech Statistical Office)
- Work outside the scope is quoted separately
The first 30 days
- Week 1Access, getting to know your platform and your teams, setting up communication channels.
- Weeks 2 and 3An audit of the current state, the first runbooks, quick wins you can see.
- Week 4The first monthly review and the plan for the next period.
How to start
- 1A short call: we go through the scope and your platform.
- 2We confirm the scope and the service levels.
- 3We prepare the contract and agree a start date.
Frequently asked questions
How much does the managed DevOps team cost?
CZK 263,000 per month excluding VAT for a four-person team (lead, middle, two juniors). The amount is fixed regardless of how many in-scope requests you send. The minimum term is 12 months.
Do you also develop applications?
No. The team works only on infrastructure, cloud, CI/CD and Kubernetes. Application development stays with your developers or vendor.
Is 24/7 on-call included?
No. The team works on working days from 8:00 to 17:00 CET. Out-of-hours on-call can be agreed separately.
What if we need a new landing zone or a cloud migration?
Larger projects and architecture changes are not part of the monthly price. We run them as a separate fixed-price project, after a joint analysis and with the scope approved in advance.
How fast do you respond?
Within 4 working hours for a normal request and within 1 working hour for a critical incident. Small changes are completed within 3 working days.
Tell us what you are working on.
Thirty minutes, free. We reply within one working day.