Infrastructure and maintenance
Cloud, Kubernetes and SLA-backed maintenance of systems on which business continuity depends.

Overview
We design and maintain infrastructure for systems the whole organisation's work depends on: in AWS and other public clouds, in on-premise environments and on Kubernetes clusters. Scaling, backups, monitoring and deployments are automated.
Before a project we advise on technology decisions: audit of existing systems, architecture design, cloud cost assessment, migration plan. Our recommendations are based on cost, risk and the capabilities of the client's team.
After launch we take over maintenance of the systems we built, as well as those inherited from other vendors. Scope, response time and availability are defined in the service agreement.
Scope of work
- Audit of systems and infrastructure
- Architecture design and migration plan
- Infrastructure as code
- Automatic scaling and CI/CD deployments
- Monitoring, alerts and backups
- Maintenance under a service agreement
Project flow
- 01
Audit
We analyze systems, infrastructure, costs and deployment processes. We talk to the IT team and to users.
- 02
Architecture
We present the target architecture, costs and the order of work. We take security and compliance requirements into account.
- 03
Deployment
We build or migrate environments in stages, with infrastructure described in code and a rollback plan for every step.
- 04
Maintenance
We monitor the systems, respond to incidents within the time set in the agreement and report on their status at an agreed interval.
When it makes sense
- The system is growing and the current infrastructure can no longer handle the traffic or data volume.
- Cloud costs are rising faster than the business and nobody knows why.
- The company is taking over a system from a vendor who is ending the cooperation.
- An independent assessment of an architecture or of vendor proposals is needed before a large project.
Technologies
Technologies are selected to suit the project and the client's environment. The ones we most often work with:
- AWS
- Azure
- Google Cloud
- Kubernetes
- Terraform
- CI/CD
- Prometheus and Grafana
- on-premise
Frequently asked questions
Most often AWS, but also Azure, Google Cloud and the client's own infrastructure. The choice depends on requirements, costs and what already runs at the company.
