A site on 1C-Bitrix crashes under peak load, the exchange with 1C freezes every night, kernel updates are postponed for months—these systemic issues cannot be fixed with one-off interventions. We know this from experience with dozens of projects. 1C-Bitrix subscription maintenance eliminates the onboarding cycle: a fixed hourly pool, priority queue, and engineers who know your project. Switching to subscription maintenance saves up to 40% of your development budget—for a typical project, that's 40,000 rubles monthly.
Unlike one-off tasks, where each request requires 30–60 minutes of project immersion and has no fixed priority, subscription maintenance offers zero onboarding time and strict SLA. The hourly rate with a package is on average 50% lower (package rate 1,500 RUB/hour vs ad-hoc 3,000 RUB/hour), and tasks are solved 3 times faster. Contact us to choose the optimal package.
What's included in the maintenance package?
The hourly pool covers any type of task, not just emergencies:
- Technical maintenance: kernel and module updates, CPU/RAM/disk monitoring, temporary file cleanup, alerts, SSL certificate renewal. This reduces vulnerability risks—we never leave a project with an outdated PHP version.
- Customizations and development: new features, template changes, infoblock and CRM field additions, Bizproc and business process setup.
- Integrations: support for exchanges with 1C via CommerceML, monitoring of payment system APIs (YooKassa, Sber), marketplaces, and CRM. Each integration is documented.
- Content: CMS section setup, access rights, fixing incorrect content display.
Documentation is maintained: a README with deployment, a list of integrations with keys, a change log with dates and descriptions. This is a key difference from one-off tasks—accumulated knowledge stays in the project. The hourly pool is calculated individually after an Bitrix technical audit—we estimate the average monthly load and offer a starting package from 10 hours. After 1–2 months, we adjust the volume based on real data. You see the remaining hours in real time in the tracker. To calculate the optimal package, contact us—we'll help you choose the hours for your project.
What SLA is guaranteed?
Response times are fixed in the Bitrix SLA and do not depend on engineer workload. For critical incidents—30 minutes, ensuring rapid loss mitigation. Average resolution times are shown in the table below.
| Priority | Incident Description | Response Time | Resolution Time |
|---|---|---|---|
| Critical | Site unavailable, payment fails | 30 min | 2 hours |
| High | Critical function broken | 2 hours | 8 hours |
| Medium | Non-critical function error | 4 hours | 1 business day |
| Low | Minor enhancement, improvement | 1 business day | As agreed |
We use Bitrix24 or your tracker for logging.
Why switch to subscription maintenance?
According to 1C-Bitrix documentation, regular kernel updates reduce the risk of critical vulnerabilities. With one-off engagements, each new task requires repeated immersion—30–60 minutes of billable time wasted. Subscription maintenance eliminates this downtime: the engineer already knows the architecture, infoblocks, and integrations. Additional savings come from the package rate: the hourly rate is at least 50% lower, and for a typical project, savings reach 30–40 thousand rubles per month. Subscription maintenance is 3 times faster than one-off tasks, and the package rate is 2 times lower than ad-hoc rate.
| Package Hours | Recommended Volume | What's Included |
|---|---|---|
| Starter | 10 hours/month | Maintenance + small tasks up to 2 hours |
| Basic | 20 hours/month | Full cycle + integrations |
| Extended | 40 hours/month | Priority queue + unlimited minor tasks |
Starter package: 10 hours/month at 1,500 RUB/hour (package rate) vs ad-hoc rate of 3,000 RUB/hour, saving 50%.
Maintenance process
Monthly cycle:
- Analysis: collect tasks for the month, prioritize, estimate effort.
- Design: if a task requires architectural decisions—describe in tracker.
- Implementation: code, configurations, tests on staging.
- Testing: check functionality, regression on critical scenarios.
- Deployment: release to production during agreed window.
- Reporting: client receives a report on hours spent, task statuses, and infrastructure state.
Case study: industrial chemical e-commerce site
Situation: the site was launched years ago by another contractor, no documentation, last kernel update a year ago, 1C exchange periodically fails without clear reason. What we did in the first month: performed a technical audit—found 4 critical vulnerabilities (outdated PHP, unupdated modules with CVE), 23 GB of garbage in /upload/; updated PHP to the latest version and the Bitrix kernel (rebuilt on staging, resolved 2 conflicts with custom components); stabilized the 1C exchange—the exchange agent couldn't write a lock file due to permission issues; documented all non-standard components. Current state: 20 hours/month, ~8 hours for planned maintenance, ~12 for minor enhancements and editor support. In the first month, we resolved 12 tasks totaling 18 hours.
Typical mistakes in subscription maintenance
- Not tracking remaining hours: the client doesn't see the budget and tasks pile up. We provide access to a tracker with real time.
- Neglecting documentation: when changing contractors or engineers, onboarding takes weeks. We maintain documentation from day one.
- Skipping kernel updates: each missed version increases vulnerability risk. The package includes scheduled monthly updates.
Our experience: 10+ years of Bitrix development, over 50 projects under support, certified engineers. We guarantee stability and transparency. Order a consultation to choose a package—we'll help you find the optimal number of hours for your project.