Загрузка…
What does the work cost?249 items. Every price is public.
Each item carries a range rather than an exact number: the same work costs differently in a single-department project and in a system with branches. We fix the total before the work starts.
from 20 000 ₽
The total depends on the number of roles and scenarios, how many external systems are involved, and whether data has to be migrated from an old program
How the work runs today, where data goes missing, what the system has to close.
20 000 – 300 000 ₽
A storage structure that survives the company growing, without a rewrite.
50 000 – 850 000 ₽
Screens built around how the employee works. Priced from the number of sections and the complexity of the tables.
120 000 – 2 300 000 ₽
Who sees and edits what. Needed anywhere more than one department uses the system.
60 000 – 600 000 ₽
Figures calculate themselves and export to Excel instead of being assembled by hand for Monday.
40 000 – 600 000 ₽
Reference data, history, balances. From a non-standard program, expect the upper end.
70 000 – 1 900 000 ₽
1C, CRM, warehouse or marketplace.
45 000 – 1 200 000 ₽per system
Invoices, acts, delivery notes and contracts from system data, using your templates.
30 000 – 600 000 ₽
For people who do not work at a desk: warehouse, delivery, field work.
50 000 – 900 000 ₽
External access to part of the system: statuses, documents, requests.
150 000 – 1 900 000 ₽
Deployment, accounts, documentation and a walkthrough with the people who will work in it.
50 000 – 900 000 ₽
from 15 000 ₽
The total depends on the number of processes and how settled they are: a stable process is automated quickly, while one that changes every month should not be automated at all
Where people are doing a program's job and what those hours cost. This is where the conversation starts: if the operation is cheaper than automating it, we will say so.
20 000 – 400 000 ₽
Website, email, phone and messengers into a single stream with nothing lost.
35 000 – 600 000 ₽
Invoices, acts and contracts are generated from data instead of typed by hand.
50 000 – 850 000 ₽
Approvals and checks stop depending on what an employee remembers.
50 000 – 950 000 ₽
The system tells the owner a deadline is due and tells the director when it has slipped.
20 000 – 375 000 ₽
Figures are calculated from the system's own data.
35 000 – 550 000 ₽
For when the job is closed by connecting systems that already exist and writing your own would cost more. Cheaper than development, but dependent on someone else's service.
15 000 – 300 000 ₽
from 20 000 ₽
The total depends on how many systems are being connected, whether they have a usable API, and which way the data flows: a standard one-way exchange is several times cheaper than two-way sync with conflict resolution
What connects to what, which data flows which way, and who owns each field.
30 000 – 275 000 ₽
Where the systems have a native exchange format and it closes the job: catalogue export, website leads into CRM.
30 000 – 375 000 ₽per system
Data travels in one direction under its own rules: leads into CRM, stock from 1C to the website.
55 000 – 550 000 ₽per system
Both systems read and write. More expensive than one-way: conflict resolution rules are required.
110 000 – 1 100 000 ₽per system
Exchange through files or straight into the database, when no native method exists.
85 000 – 1 050 000 ₽per system
Ozon, Wildberries and similar: orders, stock, prices.
30 000 – 4 500 000 ₽per platform
Acquiring on the merchant side: payment, refunds, reconciliation of incoming funds.
20 000 – 950 000 ₽
Queue, retry and a notification to the owner when the other system is down.
50 000 – 425 000 ₽
A screen showing completed and stuck exchanges, with manual retry.
90 000 – 650 000 ₽
from 40 000 ₽
The total depends on the volume of data, how accurate the result has to be, and whether an external model is allowed or everything has to stay inside your own perimeter: a self-hosted model on your servers costs several times more than an external one
Accuracy measured on real documents before rollout. The decision is then made on a number, not on how the demo felt.
60 000 – 850 000 ₽
Invoices, delivery notes and requests into structured data.
70 000 – 1 200 000 ₽per document type
An answer in plain words, with a link to the source document.
90 000 – 1 350 000 ₽
Classification, assignment of an owner, answers to the routine ones.
70 000 – 1 050 000 ₽
The model does not just answer but acts: creates a request, changes a status, prepares a document. Every action is logged.
120 000 – 1 900 000 ₽
The AI lives inside the CRM, the portal or the bot, not in a separate window someone has to remember to open.
50 000 – 750 000 ₽
Transcription of calls and voice messages, with analysis afterwards.
55 000 – 850 000 ₽
The model does not answer what it does not know and does not invent figures. Anything doubtful goes to a person.
40 000 – 600 000 ₽
The model runs on the company's servers when the data cannot leave.
180 000 – 3 100 000 ₽
For when a general model does not reach the accuracy your domain needs.
120 000 – 2 200 000 ₽
from 250 000 ₽
The total depends on the composition of the team and its workload: a developer, a tester and an infrastructure engineer are counted separately
Developers who work on your product only, and to your priorities.
from 250 000 ₽
from 45 000 ₽
The total depends on the size of the system, the state of the code and how much access has to be recovered: a project with a repository and a written description is taken over several times faster than a server whose password only the developer knew
What has been written, how maintainable it is, and what it costs a new team to get into the project.
25 000 – 425 000 ₽
Accounts, password storage, vulnerable dependencies, services exposed to the internet.
22 000 – 350 000 ₽
What it runs on, who owns the accounts, and whether the system comes back if the server disappears today.
17 000 – 275 000 ₽
Integrity, duplicates and broken relations. This is often where "the system calculates it wrong" actually comes from.
18 000 – 300 000 ₽
An audit before we take responsibility for a system we did not write. One-off work.
45 000 – 600 000 ₽
A director can make the decision, not only a technical specialist.
10 000 – 175 000 ₽
What to fix first, what can wait, and what each item costs.
18 000 – 325 000 ₽
Anything not working as designed is fixed with no separate quote per correction.
12 000 – 55 000 ₽per month
Libraries and the environment are updated on a schedule, not after something has broken or leaked.
10 000 – 45 000 ₽per month
Response time is fixed in the contract rather than depending on how busy we are this month. Baseline: business hours.
15 000 – 70 000 ₽per month
We find out about a failure, not your customer. Backups are verified by restoring them.
10 000 – 45 000 ₽per month
Evenings, weekends and nights, where downtime stops the business.
20 000 – 90 000 ₽per month
Each additional system beyond the first.
10 000 – 45 000 ₽per month
from 240 000 ₽
The total depends on the number of roles and screens, whether you need payments and a user account area, and which services the product exchanges data with
How the work runs today, where data goes missing, what the system has to close.
20 000 – 300 000 ₽
A storage structure that survives the company growing, without a rewrite.
50 000 – 850 000 ₽
Screens built around how the employee works. Priced from the number of sections and the complexity of the tables.
120 000 – 2 300 000 ₽
Who sees and edits what. Needed anywhere more than one department uses the system.
60 000 – 600 000 ₽
External access to part of the system: statuses, documents, requests.
150 000 – 1 900 000 ₽
Figures calculate themselves and export to Excel instead of being assembled by hand for Monday.
40 000 – 600 000 ₽
For people who do not work at a desk: warehouse, delivery, field work.
50 000 – 900 000 ₽
Acquiring on the merchant side: payment, refunds, reconciliation of incoming funds.
20 000 – 950 000 ₽
1C, CRM, warehouse or marketplace.
45 000 – 1 200 000 ₽per system
A landing page for one service or one campaign: sections, a form, analytics.
25 000 – 275 000 ₽
Deployment, accounts, documentation and a walkthrough with the people who will work in it.
50 000 – 900 000 ₽
from 30 000 ₽
The total depends on the number of marketplaces, where stock and prices come from, and whether you need automated review replies
Ozon, Wildberries and similar: orders, stock, prices.
30 000 – 4 500 000 ₽per platform
Both systems read and write. More expensive than one-way: conflict resolution rules are required.
110 000 – 1 100 000 ₽per system
Figures are calculated from the system's own data.
35 000 – 550 000 ₽
AI answers routine reviews and buyer questions; angry and disputed ones go to a manager.
70 000 – 1 050 000 ₽
The system tells the owner a deadline is due and tells the director when it has slipped.
20 000 – 375 000 ₽
Queue, retry and a notification to the owner when the other system is down.
50 000 – 425 000 ₽
A screen showing completed and stuck exchanges, with manual retry.
90 000 – 650 000 ₽
from 90 000 ₽
The total depends on the size of the catalogue, whether a design already exists, and which accounting systems the store exchanges stock and orders with
Layouts in your brand style. If a design already exists, this line comes off.
35 000 – 600 000 ₽
Products or services with a page for each item and a feed from your accounting system.
70 000 – 1 250 000 ₽
Acquiring on the merchant side: payment, refunds, reconciliation of incoming funds.
20 000 – 950 000 ₽
External access to part of the system: statuses, documents, requests.
150 000 – 1 900 000 ₽
1C, CRM, warehouse or marketplace.
45 000 – 1 200 000 ₽per system
Texts, products and news are edited by your own staff, not by a developer working through a ticket.
35 000 – 550 000 ₽
Metadata, structured data, a sitemap and clean URLs from day one, not "added later".
15 000 – 175 000 ₽
Writing copy around search demand and filling the sections.
25 000 – 400 000 ₽
Separate URLs per language and the markup search engines need.
25 000 – 400 000 ₽per language
from 300 000 ₽
The total depends on the number of roles and deal stages, whether we move data over from the old CRM, and which systems we exchange data with
How the work runs today, where data goes missing, what the system has to close.
20 000 – 300 000 ₽
A storage structure that survives the company growing, without a rewrite.
50 000 – 850 000 ₽
Screens built around how the employee works. Priced from the number of sections and the complexity of the tables.
120 000 – 2 300 000 ₽
Who sees and edits what. Needed anywhere more than one department uses the system.
60 000 – 600 000 ₽
Website, email, phone and messengers into a single stream with nothing lost.
35 000 – 600 000 ₽
The system tells the owner a deadline is due and tells the director when it has slipped.
20 000 – 375 000 ₽
Invoices, acts, delivery notes and contracts from system data, using your templates.
30 000 – 600 000 ₽
Figures calculate themselves and export to Excel instead of being assembled by hand for Monday.
40 000 – 600 000 ₽
1C, CRM, warehouse or marketplace.
45 000 – 1 200 000 ₽per system
Reference data, history, balances. From a non-standard program, expect the upper end.
70 000 – 1 900 000 ₽
For people who do not work at a desk: warehouse, delivery, field work.
50 000 – 900 000 ₽
Deployment, accounts, documentation and a walkthrough with the people who will work in it.
50 000 – 900 000 ₽
from 60 000 ₽
The total depends on the size of the knowledge base, the number of channels and whether the assistant has to act on its own: create leads, change statuses, book time slots
Accuracy measured on real documents before rollout. The decision is then made on a number, not on how the demo felt.
60 000 – 850 000 ₽
An answer in plain words, with a link to the source document.
90 000 – 1 350 000 ₽
Classification, assignment of an owner, answers to the routine ones.
70 000 – 1 050 000 ₽
The AI lives inside the CRM, the portal or the bot, not in a separate window someone has to remember to open.
50 000 – 750 000 ₽
The enquiry lands in the pipeline with its source and reaches the owner without being copied by hand.
25 000 – 350 000 ₽
The model does not just answer but acts: creates a request, changes a status, prepares a document. Every action is logged.
120 000 – 1 900 000 ₽
The model does not answer what it does not know and does not invent figures. Anything doubtful goes to a person.
40 000 – 600 000 ₽
The model runs on the company's servers when the data cannot leave.
180 000 – 3 100 000 ₽
from 20 000 ₽
The total depends on the number of document types and approval routes, whether you need e-document exchange with counterparties and whether we move the old archive
Where people are doing a program's job and what those hours cost. This is where the conversation starts: if the operation is cheaper than automating it, we will say so.
20 000 – 400 000 ₽
Invoices, acts and contracts are generated from data instead of typed by hand.
50 000 – 850 000 ₽
Approvals and checks stop depending on what an employee remembers.
50 000 – 950 000 ₽
Invoices, delivery notes and requests into structured data.
70 000 – 1 200 000 ₽per document type
Sending and signing documents with counterparties through an e-document operator.
30 000 – 375 000 ₽per operator
Who sees and edits what. Needed anywhere more than one department uses the system.
60 000 – 600 000 ₽
The system tells the owner a deadline is due and tells the director when it has slipped.
20 000 – 375 000 ₽
Old documents move into a searchable archive.
70 000 – 1 900 000 ₽
from 35 000 ₽
The total depends on the number of data sources, their condition and how many reports and roles you need: clean data from one system is several times cheaper to consolidate than data from five
1C, a CRM, a marketplace, the bank or a spreadsheet: data flows into the reports by itself.
55 000 – 550 000 ₽per source
Integrity, duplicates and broken relations. This is often where "the system calculates it wrong" actually comes from.
18 000 – 300 000 ₽
Figures are calculated from the system's own data.
35 000 – 550 000 ₽
Who sees and edits what. Needed anywhere more than one department uses the system.
60 000 – 600 000 ₽
The system messages the person responsible when a figure crosses a threshold.
20 000 – 375 000 ₽
For people who do not work at a desk: warehouse, delivery, field work.
50 000 – 900 000 ₽
from 150 000 ₽
The total depends on the number of roles and portal sections, the bonus logic and which systems the portal exchanges data with
How the work runs today, where data goes missing, what the system has to close.
20 000 – 300 000 ₽
External access to part of the system: statuses, documents, requests.
150 000 – 1 900 000 ₽
Earning, spending and tiers by your rules.
90 000 – 1 900 000 ₽
Acquiring on the merchant side: payment, refunds, reconciliation of incoming funds.
20 000 – 950 000 ₽
A full interface: catalogue, account, checkout.
90 000 – 1 350 000 ₽
The system tells the owner a deadline is due and tells the director when it has slipped.
20 000 – 375 000 ₽
1C, CRM, warehouse or marketplace.
45 000 – 1 200 000 ₽per system
For people who do not work at a desk: warehouse, delivery, field work.
50 000 – 900 000 ₽
Figures calculate themselves and export to Excel instead of being assembled by hand for Monday.
40 000 – 600 000 ₽
from 30 000 ₽
The total depends on the number of systems the codes pass through, the volume of goods and whether you sell on marketplaces
What connects to what, which data flows which way, and who owns each field.
30 000 – 275 000 ₽
Ordering codes and moving goods into and out of circulation from the accounting system.
110 000 – 1 100 000 ₽per system
Receiving and shipping with codes scanned on a phone or a terminal.
50 000 – 900 000 ₽
Codes land in the shipping documents by themselves, with no retyping.
50 000 – 850 000 ₽
Ozon and Wildberries receive the codes together with the shipment.
30 000 – 4 500 000 ₽per platform
Queue, retry and a notification to the owner when the other system is down.
50 000 – 425 000 ₽
A screen showing completed and stuck exchanges, with manual retry.
90 000 – 650 000 ₽
from 17 000 ₽
The total depends on the number of servers and services, the volume of data and whether downtime is acceptable: a switchover with no stop costs more than a weekend move
What it runs on, who owns the accounts, and whether the system comes back if the server disappears today.
17 000 – 275 000 ₽
A bare server brought into working order: the system, the environment, accounts, logging.
7 000 – 80 000 ₽per server
The same startup on a developer's laptop and on the production server.
25 000 – 500 000 ₽
The environment is restored from the repository, not from the memory of whoever set it up.
45 000 – 800 000 ₽
Reference data, history, balances. From a non-standard program, expect the upper end.
70 000 – 1 900 000 ₽
A separate environment where a change is reviewed before customers see it.
22 000 – 350 000 ₽
Customers never see a maintenance page, and a bad release rolls itself back.
30 000 – 500 000 ₽
On a schedule and verified by restoring. An unverified backup is the same thing as no backup.
18 000 – 350 000 ₽
Written 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 ₽
from 22 000 ₽
The total depends on the number of systems that hold personal data, where they are located and whether the data has to be moved to Russia
Accounts, password storage, vulnerable dependencies, services exposed to the internet.
22 000 – 350 000 ₽
What it runs on, who owns the accounts, and whether the system comes back if the server disappears today.
17 000 – 275 000 ₽
Unnecessary ports closed, key-based sign-in, brute-force protection, separated permissions.
8 000 – 100 000 ₽
Passwords and keys in a secure store, not in the code and not in a chat thread.
22 000 – 350 000 ₽
Remote work over a protected channel: each person has their own access, revoked when they leave.
13 000 – 250 000 ₽
Rules are documented and justified, rather than accumulated over the years on the principle of "whatever made it work".
17 000 – 300 000 ₽
Forms collect consent with a log: who gave it and when.
10 000 – 175 000 ₽
Logs from every service in one searchable place, instead of SSH across the servers.
25 000 – 450 000 ₽
On a schedule and verified by restoring. An unverified backup is the same thing as no backup.
18 000 – 350 000 ₽
Who has access to what is written down and kept current. An employee leaving does not turn into a hunt for passwords.
4 000 – 20 000 ₽per month
from 25 000 ₽
The total depends on how complex the logic is, what the load requirements are, and whether we write from scratch or step into existing code
Storage schema, indexes and relations. A mistake here costs more than everything else.
50 000 – 800 000 ₽
Documented endpoints your own and external clients work through.
70 000 – 1 200 000 ₽
Calculations, statuses, rules. Priced from the number of scenarios and how tangled they are.
90 000 – 1 900 000 ₽
Accounts, roles and sessions. Sign-in through a corporate account where that is needed.
35 000 – 600 000 ₽
Mailouts, reports and data exchange do not block the person using the system.
45 000 – 700 000 ₽
Caching and query work: the same response time on a Monday and at peak.
50 000 – 950 000 ₽
Documents and images live in separate storage, not on the server's disk next to the code.
25 000 – 450 000 ₽
Fixing one thing does not break three others.
35 000 – 600 000 ₽
When something falls over, you can see what and when, rather than "it does not work for a user".
30 000 – 475 000 ₽
from 15 000 ₽
The total depends on the number of screens, how complex the tables and forms are, and whether a design already exists: a dozen reference screens and an operator's workstation with tables running to thousands of rows are different jobs
No templates and no site builders. Priced from the number of screens.
50 000 – 950 000 ₽
Filters, sorting, bulk actions, entry of hundreds of rows without the page seizing up.
50 000 – 850 000 ₽
Data does not drift between screens, and a tab left open does not show yesterday's figures.
30 000 – 500 000 ₽
One interface for the monitor, the laptop and the phone in the warehouse.
25 000 – 450 000 ₽
Opens fast on an ordinary connection, not only on the office fibre.
20 000 – 375 000 ₽
An operator entering data all day works faster without a mouse.
20 000 – 325 000 ₽
For people who sit in the system for eight hours. Both themes are checked for contrast rather than switched with a filter.
15 000 – 250 000 ₽
Checkout, payment and submission are verified automatically before a release.
35 000 – 550 000 ₽
from 25 000 ₽
The total depends on the number of scenarios, whether payment happens inside the bot, and how deeply it ties into your accounting system: a bot on a ready-made script and a bot running on 1C data differ by a wide margin
Up to ten screens: a menu, answers to common questions, an enquiry into chat or email. No link to an accounting system.
25 000 – 175 000 ₽
The dialogue depends on the answers: different paths for different clients, validation of what was entered, a step back.
30 000 – 425 000 ₽
The enquiry lands in the pipeline with its source and reaches the owner without being copied by hand.
25 000 – 350 000 ₽
The bot runs on accounting system data: statuses, stock, client history.
40 000 – 600 000 ₽
A full interface: catalogue, account, checkout.
90 000 – 1 350 000 ₽
Invoicing and payment inside the conversation, through your provider.
35 000 – 500 000 ₽
Unusual questions are handled by a model rather than a tree of buttons.
60 000 – 850 000 ₽
Leave requests, work reports, deadline reminders.
30 000 – 500 000 ₽
Texts, buttons and scripts are changed by you, without going back to a developer over every comma.
25 000 – 350 000 ₽
MAX, VK or another channel on the same logic.
40 000 – 600 000 ₽per channel
from 25 000 ₽
The total depends on the number of pages, whether the copy and design already exist, and whether you need an admin panel to edit things yourself: a one-pager and a corporate site with a catalogue are different orders of magnitude
A landing page for one service or one campaign: sections, a form, analytics.
25 000 – 275 000 ₽
Sections built for the queries people type, not for the company's departments. Needed from a multi-page site upwards.
20 000 – 275 000 ₽
Layouts in your brand style. If a design already exists, this line comes off.
35 000 – 600 000 ₽
A corporate site with shared sections. Priced from the number of pages and the complexity of the blocks.
50 000 – 950 000 ₽
Metadata, structured data, a sitemap and clean URLs from day one, not "added later".
15 000 – 175 000 ₽
The enquiry goes where someone will see it, with spam protection and the consent required by the Russian personal data law (152-FZ).
10 000 – 175 000 ₽
Texts, products and news are edited by your own staff, not by a developer working through a ticket.
35 000 – 550 000 ₽
Products or services with a page for each item and a feed from your accounting system.
70 000 – 1 250 000 ₽
Writing copy around search demand and filling the sections.
25 000 – 400 000 ₽
Separate URLs per language and the markup search engines need.
25 000 – 400 000 ₽per language
Enquiries and data go into your system, not only to an inbox.
30 000 – 550 000 ₽
from 15 000 ₽
The total depends on the size of the system, the response time you need, and whether work is required at nights and weekends: round-the-clock cover costs several times more than support during business hours
Response time is fixed in the contract rather than depending on how busy we are this month. Baseline: business hours.
15 000 – 70 000 ₽per month
Anything not working as designed is fixed with no separate quote per correction.
12 000 – 55 000 ₽per month
New reports, fields and scenarios. You own the task queue.
25 000 – 110 000 ₽per month
Libraries and the environment are updated on a schedule, not after something has broken or leaked.
10 000 – 45 000 ₽per month
We find out about a failure, not your customer. Backups are verified by restoring them.
10 000 – 45 000 ₽per month
Evenings, weekends and nights, where downtime stops the business.
20 000 – 90 000 ₽per month
An audit before we take responsibility for a system we did not write. One-off work.
45 000 – 600 000 ₽
Each additional system beyond the first.
10 000 – 45 000 ₽per month
from 5 000 ₽ / month
The total depends on the number of pages and how competitive the queries are: promoting a landing page in one city and a catalogue of thousands of products across Russia differ several times over
Metadata, structured data, a sitemap and clean URLs from day one, not "added later".
15 000 – 175 000 ₽
Sections built for the queries people type, not for the company's departments. Needed from a multi-page site upwards.
20 000 – 275 000 ₽
Writing copy around search demand and filling the sections.
25 000 – 400 000 ₽
Every month: indexing errors, speed, markup, Yandex Webmaster and Search Console.
5 000 – 40 000 ₽per month
Pages for demand that is not yet covered: services, cities, products, questions.
8 000 – 90 000 ₽per month
New copy and rework of pages that slipped, titles and descriptions for the results page.
6 000 – 60 000 ₽per month
Pages and markup for Yandex Neuro, Alice and ChatGPT, checking their answers to your queries.
7 000 – 50 000 ₽per month
Yandex Maps, 2GIS, directories and replies to reviews.
5 000 – 25 000 ₽per month
Metrica with goals for leads and calls, rankings and traffic, a report and a plan for the month.
5 000 – 15 000 ₽per month
from 10 000 ₽
The total depends on the size of the codebase and whether you need the report alone or a remediation plan with costings as well
What has been written, how maintainable it is, and what it costs a new team to get into the project.
25 000 – 425 000 ₽
Accounts, password storage, vulnerable dependencies, services exposed to the internet.
22 000 – 350 000 ₽
Where the system slows down and what happens when the number of users grows several times over.
20 000 – 325 000 ₽
What it runs on, who owns the accounts, and whether the system comes back if the server disappears today.
17 000 – 275 000 ₽
Integrity, duplicates and broken relations. This is often where "the system calculates it wrong" actually comes from.
18 000 – 300 000 ₽
A director can make the decision, not only a technical specialist.
10 000 – 175 000 ₽
What to fix first, what can wait, and what each item costs.
18 000 – 325 000 ₽
from 18 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
An update runs the checks and ships itself. Nobody copies files by hand.
35 000 – 600 000 ₽
The same startup on a developer's laptop and on the production server.
25 000 – 500 000 ₽
A separate environment where a change is reviewed before customers see it.
22 000 – 350 000 ₽
Customers never see a maintenance page, and a bad release rolls itself back.
30 000 – 500 000 ₽
The environment is restored from the repository, not from the memory of whoever set it up.
45 000 – 800 000 ₽
A working cluster sized to your load: nodes, networking, storage, permissions.
60 000 – 800 000 ₽
An existing system moves to Kubernetes without rewriting the code.
45 000 – 700 000 ₽per service
Domains, HTTPS and certificate renewal with nobody involved.
18 000 – 275 000 ₽
Capacity is added at peak and removed at night. You pay for load, not for headroom.
25 000 – 400 000 ₽
Encryption 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 ₽
A container does not start with more rights than it needs, and services do not reach each other without permission.
30 000 – 450 000 ₽
Load, response time and errors on one screen. You see the state instead of guessing.
35 000 – 550 000 ₽
Logs from every service in one searchable place, instead of SSH across the servers.
25 000 – 450 000 ₽
You can see which step spent three of the four seconds.
35 000 – 550 000 ₽
Trigger rules and routes: who gets woken at night and what waits until morning.
18 000 – 325 000 ₽
A check from the customer's side: a site can look healthy on the metrics and still not open.
10 000 – 175 000 ₽
On a schedule and verified by restoring. An unverified backup is the same thing as no backup.
18 000 – 350 000 ₽
Written 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 replica and automatic failover: the primary going down does not stop the work.
45 000 – 700 000 ₽
Passwords and keys in a secure store, not in the code and not in a chat thread.
22 000 – 350 000 ₽
We find the system's ceiling before Black Friday rather than during it.
25 000 – 450 000 ₽
from 7 000 ₽
The total depends on the number of servers, the response time you need, and whether cover is required outside business hours: a round-the-clock arrangement costs several times more than support during the working day
A bare server brought into working order: the system, the environment, accounts, logging.
7 000 – 80 000 ₽per server
Domains, HTTPS, automatic certificate renewal, caching rules.
5 000 – 70 000 ₽
The database is tuned to your load and volume rather than left on factory defaults.
10 000 – 150 000 ₽
Corporate mail on your own domain, with the signing records set up so messages do not land in spam.
10 000 – 125 000 ₽
Unnecessary ports closed, key-based sign-in, brute-force protection, separated permissions.
8 000 – 100 000 ₽
System and package updates, disk cleanup, renewals. Business hours.
7 000 – 30 000 ₽per month
Disk space, load and certificate expiry, with alerts before any of it becomes an incident.
5 000 – 20 000 ₽per month
A schedule, storage in a separate location, and regular verification by restoring.
6 000 – 25 000 ₽per month
Response time is fixed in the contract. Baseline: business hours.
8 000 – 35 000 ₽per month
Evenings, weekends and nights, where downtime stops the business.
14 000 – 65 000 ₽per month
Who has access to what is written down and kept current. An employee leaving does not turn into a hunt for passwords.
4 000 – 20 000 ₽per month
from 9 000 ₽
The total depends on the number of sites, your resilience requirements, and whether usable equipment is already in place: connecting remote staff to one office and joining three warehouses are different jobs
Topology, addressing and segmentation. Internal services do not face the internet.
22 000 – 400 000 ₽
Remote work over a protected channel: each person has their own access, revoked when they leave.
13 000 – 250 000 ₽
Offices, warehouses and production work on one network with shared systems.
18 000 – 325 000 ₽per site
Rules are documented and justified, rather than accumulated over the years on the principle of "whatever made it work".
17 000 – 300 000 ₽
Guest access separated from working access, and staff signing in with an account rather than a shared password on a sticky note.
15 000 – 275 000 ₽
Links and equipment are watched, with alerts when connectivity degrades.
11 000 – 175 000 ₽
The primary provider going down switches over automatically, not by a phone call to support.
13 000 – 225 000 ₽
Topology, addresses and rules written down. A new engineer works from a document instead of reverse engineering.
9 000 – 150 000 ₽
The price list shows the order of prices, not the total: bundled together, some work gets cheaper and some gets more expensive. Describe the problem and we will name the exact sum before the work starts.