Загрузка…
A release stops being an event people brace for. An update ships at the press of a button, and if something goes wrong it rolls back just as fast.
from18 000₽
The total depends on the current state of the infrastructure, the number of services, and your resilience requirements: not everyone needs Kubernetes and a service mesh, and we will say so if they are overkill for you
A lower bound, not a final price. We work out the exact sum after breaking the problem down and fix it before the work starts.
A list of work, not a description of an approach. The scope is adjusted to the job: anything unnecessary comes off and anything missing goes on at the estimate stage.
An update runs the checks and ships itself. Nobody copies files by hand.
The system starts the same way on a developer's laptop and on the production server.
The environment is restored from the repository, not from the memory of whoever set it up.
Metrics, logs and tracing. The on-call engineer hears about a problem, not your customer's support line.
Copies are made on a schedule and verified by restoring them. An unverified backup is the same thing as no backup.
Passwords and keys live in a secure store, not in the code and not in a chat thread.
Tick the work you need and see the order of magnitude. The estimate goes along with your enquiry.
| Include in estimate | Work | Price |
|---|---|---|
| Shipping updatesA release stops being an event people prepare for in advance. | ||
| Build and deploy at the press of a buttonAn update runs the checks and ships itself. Nobody copies files by hand. | 35 000–600 000₽ | |
| ContainerisationThe same startup on a developer's laptop and on the production server. | 25 000–500 000₽ | |
| A staging environmentA separate environment where a change is reviewed before customers see it. | 22 000–350 000₽ | |
| Updates without downtimeCustomers never see a maintenance page, and a bad release rolls itself back. | 30 000–500 000₽ | |
| Infrastructure as codeThe environment is restored from the repository, not from the memory of whoever set it up. | 45 000–800 000₽ | |
| KubernetesWorth it where there are many services and the load swings. For one application on one server it is overkill, and we will say so plainly. | ||
| Cluster deploymentA working cluster sized to your load: nodes, networking, storage, permissions. | 60 000–800 000₽ | |
| Moving an application into the clusterAn existing system moves to Kubernetes without rewriting the code. | 45 000–700 000₽per service | |
| Incoming traffic and certificatesDomains, HTTPS and certificate renewal with nobody involved. | 18 000–275 000₽ | |
| AutoscalingCapacity is added at peak and removed at night. You pay for load, not for headroom. | 25 000–400 000₽ | |
| Service meshEncryption between services, request retries and a map of calls. Worth it from about ten services; before that it is complexity for its own sake. | 70 000–1 000 000₽ | |
| Cluster security policiesA container does not start with more rights than it needs, and services do not reach each other without permission. | 30 000–450 000₽ | |
| ObservabilityThe on-call engineer hears about a failure, not your customer on the phone. | ||
| Metrics and dashboardsLoad, response time and errors on one screen. You see the state instead of guessing. | 35 000–550 000₽ | |
| Log collectionLogs from every service in one searchable place, instead of SSH across the servers. | 25 000–450 000₽ | |
| Request tracingYou can see which step spent three of the four seconds. | 35 000–550 000₽ | |
| Alerting and on-callTrigger rules and routes: who gets woken at night and what waits until morning. | 18 000–325 000₽ | |
| Availability checks from outsideA check from the customer's side: a site can look healthy on the metrics and still not open. | 10 000–175 000₽ | |
| Resilience and recoveryWhat happens when a server, a database or an entire site disappears. | ||
| BackupsOn a schedule and verified by restoring. An unverified backup is the same thing as no backup. | 18 000–350 000₽ | |
| A disaster recovery planWritten down: how long the system takes to come back and in what order, if a site disappears. Proven by a drill, not by faith. | 35 000–600 000₽ | |
| A resilient databaseA replica and automatic failover: the primary going down does not stop the work. | 45 000–700 000₽ | |
| Secrets managementPasswords and keys in a secure store, not in the code and not in a chat thread. | 22 000–350 000₽ | |
| Load testingWe find the system's ceiling before Black Friday rather than during it. | 25 000–450 000₽ | |
This is an order-of-magnitude estimate, not a costed quote and not an offer. Bundled together, some work gets cheaper and some gets more expensive depending on the specifics: the exact sum is worked out after we break the problem down, and it is fixed before the work starts.
Verifiable facts instead of claims about ourselves. There is not a single invented case in this catalogue.
Docker, Kubernetes, GitLab CI, ArgoCD, Terraform, Helm, Prometheus, Grafana and Vault run in our projects.
The infrastructure can be moved to another cloud or onto your own hardware: we do not nail a project to a single provider.
Tell us what is happening now. We reply within one business day, and the first conversation commits you to nothing.