Support on Telegram VPS login Video login

Bitrix24 On-Premise on a VPS: Requirements, Configuration and Common Mistakes

VPS and servers Published: · 5 min read

On-premise Bitrix24 isn’t a website — it’s a full-fledged application with chats, calls, tasks and a CRM. Server requirements are to match. Here’s how to avoid a portal that “thinks for 10 seconds.”

Cloud or on-premise

Cloud Bitrix24 is a subscription: the data sits with the vendor abroad, and you’re bound by plan limits. On-premise means a license and your own server: data stays in Uzbekistan (important under the personal data law), you can customize it, and integrate with 1C without restrictions. The downside is that the server has to be administered.

Minimum and recommended configurations

EmployeesvCPURAMNVMe diskPrice at MyCloud (with IP address)
up to 1024 GB60 GB≈ 10 000 UZS/day
10–5048 GB120 GB≈ 19 000 UZS/day
50–100816 GB250 GB≈ 37 500 UZS/day
100+ / telephony, video calls12–1632 GB500 GBfrom 70 000 UZS/day

Disk usage grows faster than you’d expect: task attachments, call recordings, document versions. Plan for 1–2 GB per employee per year.

Why not shared hosting

Bitrix24 requires a push server (Node.js), queues, cron every minute, at least 512 MB of memory per PHP process and MySQL with large buffers. On shared hosting this is either prohibited or hits the limits — the portal works, but it “thinks.”

Settings that deliver speed

  • The ready-made BitrixVM environment or an equivalent: nginx + PHP-FPM + MySQL with tuned buffers (innodb_buffer_pool_size at 50–60% of memory).
  • Opcode cache and memcached/Redis for the core cache — a must.
  • Push server for chats and notifications — without it, employees have to refresh the page manually.
  • Cron instead of “hits” for agents and email.
  • NVMe disk — the CRM writes to the database heavily.
  • HTTPS with Let’s Encrypt and no direct external access to MySQL.

Common mistakes

  1. Deploying on 2 GB of memory “as a trial,” then migrating later along with all the accumulated problems.
  2. Not setting up database backups — Bitrix’s standard backup to the same disk doesn’t count.
  3. Leaving the portal on HTTP with port 3306 open.
  4. Not updating — and Bitrix updates patch the vulnerabilities used to hack portals en masse.

How we do it

The Bitrix24 image with a ready-made environment deploys in 15 minutes. We’ll help you move your existing portal — we advise and walk you through the steps. We set up backups to separate storage and, if you wish, take over administration of the portal: updates, monitoring, recovery.

Need help with the task from this article?

We’ll pick a configuration, calculate the cost and help with the move.

Not sure what to choose? We’ll help you pick a configuration

Tell us what you need — a server for 1C, cameras for a pickup point or a move from another host. We’ll find a solution, give you an exact price and help with the move: we’ll advise and walk you through the steps.