Bitrix24 On-Premise Setup & Configuration — Full-Cycle Service

Picture this: you’ve purchased a Bitrix24 license, installed the distribution on your server, and within a month employees are complaining about slow performance, emails land in spam, and 1C integration fails. Sound familiar? We encounter this on every second project. For example, on a recent project with 30 users, pages took 12 seconds to load after installation without Redis configuration — resulting in a 40% productivity loss. Or the case where incorrect cron settings prevented agents from sending notifications, causing managers to miss a deal. Proper configuration of Bitrix24 On-Premise is not just running the setup wizard. It’s a comprehensive set of tasks: from choosing the server stack to configuring agents and caching. With 10+ years of experience and certified Bitrix24 partner status, we’ve configured over 50 on-premise installations, each requiring an individual approach. We guarantee results or your money back within 30 days. Get a consultation with an engineer — we’ll check your configuration and propose optimizations.

Bitrix24 On-Premise Configuration: Complete Checklist

Infrastructure Requirements

Minimum requirements for teams up to 50 users:

For 100+ users, clustering is required — that’s a separate topic. However, even at 50 users, it’s important to place the DBMS on a separate server.

Initial Configuration After Installation

After installing the distribution and completing the setup wizard, go through this mandatory checklist.

How to configure SSL/TLS?

Bitrix24 On-Premise without HTTPS is unforgivable. Use Certbot + Let’s Encrypt or a corporate certificate. Set up a forced HTTP → HTTPS redirect in the nginx configuration.

How to optimize PHP?

Critical parameters in php.ini:

memory_limit = 512M
max_execution_time = 300
upload_max_filesize = 100M
post_max_size = 100M
opcache.enable = 1
opcache.memory_consumption = 256

How to configure MySQL/MariaDB?

Mandatory settings in my.cnf:

innodb_buffer_pool_size = 4G  # ~60-70% of RAM
innodb_log_file_size = 512M
max_connections = 200
query_cache_type = 0  # disable, use Redis instead

How to configure caching?

Connect Redis or Memcached for sessions and data cache. Without caching, the system runs 3–5 times slower under load. Redis is the optimal choice. According to official documentation, caching with Redis boosts performance up to 5x. Redis cache outperforms Memcached by 2x in transaction throughput. Our optimization techniques ensure peak performance.

Agents and Cron: Why This Is Critical

Bitrix24 On-Premise uses agents for background tasks: sending notifications, synchronizing with 1C, updating the search index. If agents are not configured, the system will hang during mass operations. Set up cron-based agent execution instead of the built-in hit /bitrix/tools/cron_agents.php:

*/5 * * * * php -f /var/www/bitrix/tools/cron_agents.php

Or use cron_events.php. Ensure the constant BX_CRONTAB_SUPPORT is defined in dbconn.php.

How to verify agent operation?

1. Check if cron is running: crontab -l.
2. Ensure BX_CRONTAB_SUPPORT is defined in dbconn.php.
3. Run a test: php /path/to/bitrix/tools/cron_agents.php.
4. Check agent logs in the Bitrix24 event log.

Integration with 1C and External Services

Exchange with 1C via CommerceML is a common point of failure. Ensure access rights to infoblocks are set correctly and exchange profiles work. For Bitrix24 REST API, use webhooks and OAuth authorization. More details in the official documentation.

Comparison of Business and Enterprise Editions

Mail Server and Notifications

On-premise does not use Bitrix24 cloud mail servers — you need to connect your own SMTP. Configuration: Settings → Mail → Outgoing Mail. We recommend not using corporate SMTP directly — set up Postfix as a relay with a reputable IP or use a transactional service (SendGrid, Unisender). Separately configure DKIM and SPF for your domain — otherwise Bitrix24 notifications will land in spam.

Updates and Maintenance

On-premise updates are performed manually or via the built-in updater. We strongly advise:

• Do not update immediately after a new version release — wait 2–3 weeks for patches to appear.
• Perform a full backup (files + DB) before every update.
• Maintain a staging server with the same version for pre-testing updates.

Updating Bitrix24 On-Premise is not just “press a button.” After major version updates, custom modifications made via bitrix/php_interface/init.php often break. Allocate time for verification and fixes.

Typical Errors and Solutions

Deliverables – What’s Included in On-Premise Configuration

• Audit of current server infrastructure
• Installation and setup of the Bitrix24 distribution
• Configuration of PHP, MySQL, web server (nginx/apache)
• Caching setup (Redis/Memcached)
• SSL/TLS configuration (Let’s Encrypt or corporate certificate)
• Mail server and DNS record setup (DKIM, SPF)
• Agent and cron configuration
• Integration with 1C (CommerceML) and external services
• Administrator training on system operation
• Technical support after launch (up to 3 months)
• Full documentation of the configuration
• Access credentials and handover

The on-premise version requires upfront investment but eliminates monthly payments, which is beneficial when scaling. Our service starts from $2,500 and can save you up to $5,000 annually compared to cloud subscription fees. Proper caching configuration reduces server resource costs by lowering CPU and DB load. Order an audit of your on-premise version — we’ll identify bottlenecks and propose optimization. Contact us for a consultation on on-premise setup and support.

Corporate Bitrix24 Installation: When the Cloud Is Not an Option

The cloud Bitrix24 is convenient for starting, but when a business exceeds 50 users or requires compliance with Federal Law 152, 54-FZ, or other regulations, the on-premise version becomes the only viable option. We have installed on-premise solutions in banks, manufacturing plants, and government organizations — everywhere where data cannot be shared with third parties. With 10+ years of Bitrix experience and 200+ completed installations, we deliver stable, secure portals.

Contact us for a free consultation and server requirements check — we will respond within one business day.

Why Is On-Premise Mandatory for Regulated Companies?

Regulators — Central Bank, FSTEC, Roskomnadzor — directly prohibit storing personal data in foreign clouds. Federal Law No. 152-FZ "On Personal Data" requires operators to ensure localization of databases on the territory of the Russian Federation. On-premise allows you to host the portal in a certified data center or in a closed circuit without internet access. You control who and when accesses the database.

Deep customization is another advantage. In the cloud, you are limited by REST API and the marketplace. On-premise gives full access to PHP code: you can add your own tab to a deal card, rewrite business process logic, connect direct SQL to ERP. The key is not to patch the core, but to write your own modules via \Bitrix\Main\ModuleManager. That is what we do.

High loads — 500+ active users, document flow with thousands of deals per day, constant telephony — the cloud hits limits. On-premise scales: move MySQL to a separate server, configure Redis for b_cache caching — and the portal flies. With 200+ users, the performance of a dedicated server is 3-4 times higher than a cloud plan.

Integration with internal systems: Active Directory, 1C:Enterprise via SOAP, legacy ERP through direct connection to Oracle — all this is easier when the portal is on the same local network. No hassle with VPN tunnels and timeouts. Autonomy: the portal works without internet — a must for production floors and secure facilities.

If you have fewer than 50 users, no specific security requirements, and no in-house system administrator — the cloud is cheaper, simpler, and self-updating. For everyone else, on-premise wins.

On-Premise Bitrix24 Is More Profitable for Mid-Sized Businesses

Let us compare the two options by key metrics (based on our projects):

On-premise is 2-3 times more profitable starting from 100 employees and with a system administrator on staff — confirmed by calculations for dozens of projects. The "Company" license is significantly cheaper than the annual cloud subscription for 100 users. The savings exceed $15,000 over three years for a 100-user deployment.

What Is Included in the Corporate Bitrix24 Implementation?

We do not just install Bitrix24 on a server. Deliverables include:

• Installation and configuration of the stack — nginx + PHP-FPM + MySQL/MariaDB + Redis. We calculate pm.max_children using the formula: available RAM / worker consumption (usually 256M). With 16GB RAM, we get ~50 workers.
• Cloud migration — transfer CRM, tasks, chats, disk, business processes. Entity IDs differ (deal #1234 becomes #5678) — we reconfigure all automations.
• Integrations — 1C (synchronization of directories and documents), AD (automatic account creation), telephony (SIP trunks via voximplant or your Asterisk), EDI (Diadoc, SBIS).
• Custom development — modules, REST webhooks, branching business processes, chatbots. We use CBPActivity for non-standard logic.
• Training — 2-5 days for administrators and key users.
• Documentation — architecture diagram, backup instructions, update policy.
• Technical support — SLA-based support after launch: incident response, updates, integration fixes.

We will assess your project within one business day — contact us for a quote.

What Are the Typical Pitfalls During On-Premise Installation?

Even experienced teams face common issues: incorrect pm.max_children causing OOM, missing innodb_buffer_pool_size tuning, or wrong Redis eviction policy. We avoid these by following proven patterns:

• Configure PHP-FPM pool settings based on actual average request size (profile via strace and htop).
• Set innodb_buffer_pool_size to 60-70% of available RAM for dedicated DB servers.
• Use allkeys-lru for Redis when caching entire Infoblock results.
• Enable slow query log (long_query_time = 1) from day one to catch expensive queries.

We document every decision for your ops team. See Wikipedia: On-premises software for general background.

How to Select the Right License Edition

Licenses vary by user count: CRM (up to 12), Company (up to 50), Enterprise (up to 500), Holding (unlimited). We help choose the right edition without overpaying and remind about renewals. An expired license means no security updates — a potential vulnerability.

Server Infrastructure for Corporate Bitrix24 Installation: Where the Real Pitfalls Lie

The standard recommendation of "4 CPU, 8GB RAM" is for a demo setup. In production with 200 users, active CRM, and telephony, it will not work.

Monitoring via Zabbix+Grafana — alerts on CPU >80% sustained, RAM <10% free, disk I/O wait >20%, MySQL slow queries >100/hour. Backups — daily, with restoration testing once a month (because a backup that cannot be restored is not a backup).

Updates: A Controlled Process

In the cloud, updates arrive automatically — and sometimes break custom integrations. With on-premise, you decide when to update.

1. Test on staging — an exact copy of production with anonymized database.
2. Check compatibility of custom modules — partner_modules may conflict with the new core.
3. Perform a full backup (files + DB) before applying.
4. Update during a low-load window (Sunday night).
5. Monitor for 24 hours after the update.

How Long Does On-Premise Bitrix24 Implementation Take?

Get a consultation on implementation — contact us, and we will send a project plan with exact timelines for your case. We do not leave after launch; we provide ongoing SLA support. Reach out to our team for a detailed proposal.