One of the first questions when getting started with Bitrix24 is whether to go with the cloud or the on-premise edition. The decision affects your budget, timelines, customizations, and where your customers' data physically resides. Let's walk through six practical criteria, without leaning toward either side, and close with a simple decision algorithm tailored to businesses in Kazakhstan.
In brief: the fundamental difference
Cloud (SaaS) means you pay a subscription, the portal runs on Bitrix servers, and it is updated and maintained for you. You log in via a link such as yourcompany.bitrix24.kz and start working. On-premise means you buy a license once, install Bitrix24 on your own server or hosting, and from then on you are responsible for uptime, updates, backups, and security. These are not two different products in terms of CRM logic; they are two different models of ownership and responsibility.
1. Hosting and control over data
Bitrix24 cloud portals for the Russian-speaking market are hosted in the vendor's data centers (historically Russian and European infrastructure, with a separate segment for the .kz zone). You do not manage the server, which is both an advantage (you cannot break anything) and a limitation (no direct access to the database or file system).
On-premise is installed wherever you specify: on a server in your office, on a VPS from a Kazakhstani provider (PS.kz, Hoster.kz, ps.kz, the Beeline/Kcell cloud), or on foreign hosting. If it is critical for you that customers' personal data is physically stored within Kazakhstan, that is an argument in favor of on-premise on a local server.
- Cloud: data resides with the vendor, with access only through the interface and the REST API; you will not be granted access to the database itself.
- On-premise: full access to the server, database (MySQL), and files; you can run direct SQL queries, set up your own backups, and apply your own disk encryption.
- The Kazakhstan Law on Personal Data (Article 12) requires the personal data of Kazakhstani citizens to be stored on servers within Kazakhstan; for certain sectors (government, finance, healthcare) this is the decisive factor in favor of on-premise on local hosting.
2. Deployment: timelines and barrier to entry
The cloud goes live the day you pay. Registering the portal takes minutes; configuring pipelines, permissions, and integrations takes anywhere from a few days to a couple of weeks depending on complexity. No administrator and no server required.
On-premise requires preparation: a server with adequate resources (at least 4 cores / 8 GB of RAM for a small team, realistically more), the correct stack (BitrixVM on CentOS/AlmaLinux is recommended), an SSL certificate, and configuration of email, backups, and monitoring. From order to a working portal usually takes 1-3 weeks for the infrastructure alone, plus the CRM configuration itself.
3. Customization and integrations
This is the main fork in the road. In the cloud, customizations are built through the REST API, webhooks, Marketplace apps, and business processes. That is enough for most needs: website integration, Wazzup (WhatsApp/Instagram/Telegram), IP telephony on Asterisk, data exchange with 1C through the standard module, Kaspi, and payment links. But there is no access to the core or the database, so you cannot write nonstandard logic that reaches deep into the system.
On-premise gives you the PHP source code and direct database access. You can write your own modules, modify the core (carefully), build heavy reports with direct SQL queries, and set up nonstandard integrations with your own software, warehouse, and production systems. This is the territory for complex scenarios, but updates become more complicated too: every core customization requires a compatibility check.
- Choose the cloud if your integrations are standard: website, messengers, telephony, 1C, Kaspi, marketplaces.
- Choose on-premise if you need deep logic: custom modules, nonstandard data exchange, direct SQL reports, tight coupling with internal systems.
- Important: on on-premise, custom core modifications are technical debt. The more "surgery" you do, the more expensive every update becomes.
4. User limits and pricing plans
In the cloud, the number of users and the amount of disk space depend on your plan. Basic supports up to 5 users, Standard up to 50, and Professional up to 100. There are higher-capacity plans as well. Exceed the limit and you simply move up to a higher plan, which is just a matter of one payment.
On-premise is licensed by number of users on a one-time basis: for example, an edition for 50 or 100 users. Expansion means buying additional licenses. In return, there is no monthly dependency: buy for 50 users and you can use it for years without new per-user payments (updates are covered below).
5. Cost: subscription versus one-time purchase
The cloud is an operating expense (OPEX). You pay monthly, or annually at a discount. The starting cost is low and the barrier to entry is minimal, but the payment continues for as long as you use it.
On-premise is a capital expense (CAPEX). The license is bought once, but it comes with hidden line items that are often left out of the calculation.
- Bitrix24 license (one-time, depending on the edition and number of users).
- Server or VPS, paid monthly (from roughly 15,000-40,000 KZT/month for an adequate VPS for a small team).
- Renewal of technical support and updates, typically around 25% of the license cost per year after the first year; without it the portal receives no security updates.
- Administration: either an in-house DevOps engineer/admin or a contractor for ongoing support.
- SSL, backups, monitoring.
A rough estimate of the break-even point: on-premise starts to win financially over a horizon of 2-4 years and with a stable team. If your team is growing fast or you are not prepared to maintain a server, the cloud is usually more cost-effective in terms of total cost of ownership, because all the infrastructure and updates are already included in the subscription.
On-premise is cheaper "on paper" and more expensive to operate. The cloud is more expensive "by subscription" and cheaper on your nerves. Calculate TCO over 3 years, not the license price.
6. Security and maintenance
In the cloud, the vendor handles security: patches, DDoS protection, fault tolerance, and infrastructure backups are all on their side. Your area of responsibility is passwords, access rights, two-factor authentication, and employee discipline.
With on-premise, security is entirely yours. Fail to update in time and you have a vulnerability. Real incidents on self-hosted portals and websites happen precisely because of missed updates and poor server configuration. If you go with on-premise, budget for regular maintenance: updates, scheduled backups, monitoring, and permission audits.
Who should choose what: a short algorithm
- Small business, startup, team of up to 50, standard needs: cloud. Fast, predictable, no server.
- Growing company without its own IT department: cloud. Scale by changing plans rather than buying hardware.
- A requirement to store personal data within Kazakhstan (public sector, finance, healthcare): on-premise on Kazakhstani hosting.
- Need deep core customizations, nonstandard integrations, heavy SQL reports: on-premise.
- A large, stable team (100+), a 3+ year horizon, and an in-house administrator: on-premise can win on TCO.
- Not sure? Start with the cloud. You can move from cloud to on-premise later through data migration; the reverse is rarer and harder.
Conclusion
There is no single "right" answer for every case; there is an answer that fits your situation. The cloud wins on speed of deployment, freedom from infrastructure concerns, and a predictable payment. On-premise wins on control over data, freedom to customize, and potential savings over the long run, but it requires a server, hands-on effort, and discipline. Calculate TCO over 3 years, honestly assess your requirements for data and customization, and the choice will become obvious.
