01What decides the price
Scope
- Keeps it lower
- One application and one pipeline
- Pushes it higher
- Many services across several environments
Starting point
- Keeps it lower
- An existing setup to improve
- Pushes it higher
- Infrastructure built from scratch
Infrastructure
- Keeps it lower
- Simple servers or managed services
- Pushes it higher
- Kubernetes clusters with GitOps
Security
- Keeps it lower
- Standard checks in the pipeline
- Pushes it higher
- DevSecOps with audits and policy checks
Monitoring
- Keeps it lower
- Basic dashboards and alerts
- Pushes it higher
- Full observability with runbooks
Clouds
- Keeps it lower
- One cloud
- Pushes it higher
- Several clouds or hybrid
Team
- Keeps it lower
- A team that already knows the tools
- Pushes it higher
- Training and handover for a new team
After launch
- Keeps it lower
- Handover and done
- Pushes it higher
- Monthly support or on-call help
02How teams charge
- Assessment: a short audit with a ranked plan and written quote
- Fixed-scope project: a clear scope, timeline and price for work such as a pipeline or a migration
- Hourly: fixes, audits and short tasks
- Dedicated engineer or team: part-time or full-time by the month, working in your tools
03Costs people forget
- The cloud bill, which depends on how the setup is sized
- Tool licences, where paid tools are chosen
- Time for your own team to review and learn
- Ongoing patching, upgrades and monitoring
- Documentation and handover
Ask every vendor to state what is included after the first release, so quotes cover the same thing.
?Frequently asked questions
Where should we start?
With an assessment of how you ship today. It gives a ranked plan and a quote.
Can we start with one pipeline?
Yes. A first pipeline for one service is a common, low-risk start.
Who owns the pipelines?
You do. They live in your repositories with documentation.
How do I get a quote?
Book a free 30-minute call. We follow with a written plan and quote.