Self-Hosted Bitrix24 Support & Maintenance Plans: SLAs, Hours and What's Covered

Why Vendor Support Alone Isn't Enough for Self-Hosted

The Bitrix24 (Alaio) vendor provides a support channel for on-premise licence holders, but that channel explicitly excludes server configuration, infrastructure diagnostics, backup management, custom module issues, and proactive monitoring - which are precisely the tasks that keep a self-hosted portal healthy.

With the cloud edition, Alaio's engineering team handles patching, uptime, and scaling automatically. The moment you move to an on-premise deployment, those responsibilities transfer to you. The vendor's built-in support chat requires an active commercial licence, a publicly reachable portal URL, a valid (non-self-signed) SSL certificate, and deals only with product-level questions - not your infrastructure.

What the vendor's own documentation explicitly marks as out of scope for on-premise support:

• Installing or configuring server software
• Preparing or restoring backups
• Load testing or infrastructure diagnostics
• Fixing database-level errors
• Custom module or third-party integration issues
• Any server-side proxy or networking problems that block updates

That leaves a substantial operational gap. A qualified partner support plan is designed to close it.

What a Complete Self-Hosted Support Plan Covers

A well-structured partner maintenance plan for self-hosted Bitrix24 addresses seven core areas: security patching, tested core updates, incident response with defined SLA targets, proactive monitoring, backup verification, a pooled hour allowance for minor changes, and strategic advisory.

Support flows from monitoring and user requests through a partner's service desk to resolution - with optional escalation to the vendor for confirmed product bugs.

The flow covers the full operational loop: alerts from server monitoring and user tickets both enter the partner's service desk, which triages and resolves infrastructure issues directly, escalates confirmed product bugs to the Bitrix24 vendor, and feeds resolved items back into a change log for advisory review.

flowchart LR
    MON[Server & App Monitoring] --> SD[Partner Service Desk]
    USER[User / Admin Ticket] --> SD
    SD --> INFRA[Infrastructure Fix\nPatching · Backup · Config]
    SD --> BUG{Confirmed\nProduct Bug?}
    BUG -- Yes --> VENDOR[Bitrix24 Vendor Support]
    BUG -- No --> INFRA
    VENDOR --> SD
    INFRA --> LOG[Change Log & Advisory Report]

Security Patching

PHP version requirements for self-hosted Bitrix24 change over time - as of 2026, the minimum is PHP 8.2 and the recommended version is PHP 8.3 or higher. Deprecated settings (such as mbstring.func_overload) block core updates if left in place. A support plan ensures these prerequisites are monitored and resolved before they cause downtime or block security releases. Keeping the platform current also keeps your security hardening posture intact.

Tested Core Updates

Updates to a self-hosted portal should always be preceded by a full backup. A maintenance plan provides a repeatable update process: snapshot → apply update in staging or a maintenance window → verify → document. This mirrors the step-by-step discipline covered in our on-premise updates & maintenance guide.

Incident Response with SLA Targets

Every plan tier defines response and resolution time targets by severity. ACP Group scopes the exact SLA numbers per engagement, but the structure typically covers:

Proactive Monitoring

Reactive support is necessary but insufficient. Proactive monitoring checks server resource consumption, SSL certificate expiry, update system health, and application error logs - catching issues before users notice them.

Backup Verification

Having backups is not the same as having working backups. A support plan includes periodic restore tests to confirm that your backup and disaster recovery strategy can actually deliver the RTO and RPO your business requires.

Pooled Hours for Minor Changes

Based on a typical contract structure, a defined pool of hours per period (for example, up to 10 hours per year on a basic engagement, scaling upward on higher tiers) covers small configuration changes, user access adjustments, minor workflow tweaks, and bug fixes caused by self-administered changes - without needing a separate project order each time.

Advisory

Regular check-ins cover licence renewal timing, upcoming PHP or OS compatibility requirements, capacity planning (see the hardware sizing guide for context), and when a feature request should become a development project.

Support Plan Tiers: Basic, Standard, and Premium

ACP Group offers three named tiers - Basic, Standard, and Premium - differentiated by response time commitments, monthly hour allowance, coverage hours, and the depth of proactive services included; exact SLA figures and pricing are scoped per client.

The table below shows the structural differences. ACP Group will confirm precise numbers during scoping.

Pricing depends on portal size, infrastructure complexity, and region. ACP Group provides a fixed quote after a brief technical discovery call.

How to Choose the Right Tier for Your Team

Choose your support tier based on three factors: the number of active users, how business-critical the portal is (revenue impact of downtime), and whether your internal IT team can handle first-level triage independently.

If your organisation has already evaluated the total cost of ownership across deployment models, the self-hosted vs cloud TCO analysis provides useful context for budgeting a support retainer alongside licence and infrastructure costs.

Checklist: What to Look for in a Self-Hosted Support Contract

Before signing any self-hosted Bitrix24 support agreement, verify these 12 points - a reputable partner will be able to answer every one of them clearly.

• Defined SLA tiers - written response and resolution targets for Critical, High, Medium, and Low severity, not just "best effort"
• Scope of infrastructure coverage - does it include the OS, web server (Apache/nginx), PHP, MySQL/MariaDB, and caching layers?
• Update process - is there a documented pre-update backup and rollback procedure?
• Security patching - are PHP version upgrades and deprecated-configuration remediation included?
• Backup verification - does the contract include periodic restore tests, not just backup creation?
• Monitoring specifics - what is monitored, at what frequency, and how are alerts routed?
• Hour pool terms - how are unused hours treated? Do they roll over or expire?
• Escalation path - is the partner a certified Bitrix24 partner who can engage vendor support for confirmed product bugs?
• Custom module coverage - are third-party or bespoke modules in or out of scope?
• Licence renewal management - does the partner track licence expiry and warn you ahead of time? (A lapsed licence disables updates, Marketplace, REST API, telephony, and open channels.)
• Data protection - is your data handled under a signed DPA compliant with applicable local regulations (GDPR, UAE PDPL, LGPD)?
• Reporting cadence - will you receive regular written reports on changes made, incidents resolved, and hours consumed?

Partner Support vs. Bitrix24 Vendor Support: Key Differences

The Bitrix24 vendor's on-premise support channel and a certified partner support plan are complementary, not interchangeable - the vendor answers product-level questions; a partner manages the full operational stack.

ACP Group - a Bitrix24 Gold partner with 1,300+ completed projects - acts as the single point of contact for all operational issues, engaging the vendor only when a confirmed platform bug requires escalation.

Getting a Support Plan with ACP Group

The right time to put a support plan in place is before an incident - not during one.

Whether you have just completed your initial deployment (see our installation guide for what good looks like at day one) or have been running a self-hosted portal for years without structured maintenance, ACP Group can scope a plan that matches your team size, criticality, and budget.

The engagement starts with a short technical discovery: current PHP and Bitrix24 version, server topology, active integrations, and internal IT capacity. From that, we produce a written proposal with tier recommendation, SLA table, and a fixed monthly retainer - no vague "best effort" language.

To start the conversation, use the contact form on this page. ACP Group will respond within one business day.

Comparing support options? See our managed Bitrix24 service and support plans - response times, scope and what is covered.