Bitrix24 Self-Hosted Editions and Licensing in 2026: Prices, Renewal and AI

Self-Hosted Bitrix24 Editions and Prices in 2026

As of 5 October 2026, Bitrix24 self-hosted is available in two current editions - Business and Enterprise - priced per organisation (flat fee, taxes not included), with user tiers from 50 to 1,000+ users, and an optional +1,000-user expansion pack for Enterprise. There is no perpetual licence: every copy runs on an annual subscription.

All prices are sourced from the official self-hosted price page (verified 5 October 2026):

A few things worth noting:

• Pricing is per organisation, not per user seat. Moving from Business 50 to Business 100 costs the price difference between those two editions - you do not repurchase from scratch.
• The "Corporate Portal" naming used by older documentation is legacy. The current editions are Business and Enterprise.
• A free 30-day trial is available before purchase.
• Upgrade cost = target edition price minus current edition price.

For teams deciding between cloud and on-premise, the self-hosted vs cloud TCO analysis walks through the arithmetic at various user counts.

---

How Does Annual Renewal Work for Self-Hosted Bitrix24?

Self-hosted Bitrix24 renews annually at 50% of the price of the edition you purchased - as of 5 October 2026, a Business 50 licence costs $1,795/year to maintain after the first year. There is a 14-day grace period after expiry; the copy locks completely if renewal is not completed within that window.

Key mechanics (sourced from bitrix24.com/prices/self-hosted.php, verified 5 October 2026):

• Renewal rate: 50% of the edition price each year. This applies regardless of when you renew, as long as you renew within the grace window.
• Grace period: 14 days after the licence expiry date. Miss this window and the portal locks - functionality stops until you renew.
• Upgrade path: Pay the price difference between your current and target edition (for example, Business 50 to Business 100 costs US$ 2,400).
• No instalments: Annual plans are paid upfront. For pricing queries, contact acp-24.com.

Note: for licences bought on bitrix24.com, renewal costs 50% of the edition price and there is a 14-day grace period after expiry (checked 5 October 2026).

---

What Happens When the Self-Hosted Licence Expires

When a self-hosted Bitrix24 licence expires and the 14-day grace period passes, the portal locks completely - REST API calls stop, Market apps stop working, telephony stops, and product updates and technical support become unavailable until the licence is renewed.

This is a significant operational risk. The licence includes a 12-month maintenance subscription with updates and technical support, so an expired licence first means no product updates, security patches or vendor support, and after the 14-day grace period the copy itself is locked.

Do not plan on a reduced mode in which employees keep working without a valid licence.

Practical recommendation: Put the renewal date in a shared calendar with at least a 30-day advance reminder. If you work with a Bitrix24 partner, ask them to own renewal tracking as part of a support plan. See self-hosted support and maintenance plans for what that typically covers.

---

CoPilot AI on Self-Hosted Bitrix24: What Works and What Does Not

Bitrix24 CoPilot is available on self-hosted installations from platform version 24.700.0 onward, but it requires the AI Integration module and outbound internet access to Bitrix24's AI proxy servers - meaning CoPilot prompts leave your server even on an on-premise deployment.

What you need to enable CoPilot on self-hosted

Per the official helpdesk article (updated 19 May 2026):

1. Platform version 24.700.0 or higher
2. The AI Integration module installed and active
3. Outbound HTTPS access to Bitrix24's AI proxy addresses (including ai-proxy-de.bitrix.info and related hosts)

Once configured, CoPilot works on self-hosted too: the official help states that CoPilot is available in both Bitrix24 Cloud and On-premise versions. Check which CoPilot tools your platform version includes before you plan processes around them.

What CoPilot does NOT support on self-hosted

• There is no officially documented option to run CoPilot against a local model or your own API key on an on-premise installation.
• The REST method ai.engine.* that allows registering a custom AI engine exists only in the cloud version.
• For fully in-perimeter AI processing, the documented alternative is a custom integration built by a partner that routes requests to your own OpenAI-compatible endpoint (such as a corporate vLLM or Ollama server) - or using Alaio Vibecode BYOK where the app routes to your own endpoint.

Data flow for CoPilot on self-hosted

CoPilot operates via third-party AI providers, primarily OpenAI (per the Bitrix24 AI Tools Terms of Use, updated 7 August 2026). Prompts are transmitted to the USA for processing by OpenAI. Bitrix24 stores prompt data for up to 14 days for technical purposes, then deletes it - but AI providers may use content under their own terms. This applies equally to cloud and self-hosted deployments.

For teams in regulated industries where data must stay in-country, this is a material consideration. The UAE PDPL data residency comparison and the AI data residency guide cover compliance implications in detail.

For a broader look at what CoPilot does inside the CRM, see Bitrix24 CoPilot: The AI Assistant Inside Your CRM.

---

Five Cost Layers in a Self-Hosted Bitrix24 TCO

A self-hosted Bitrix24 deployment has five recurring cost categories beyond the licence itself - server, administration, periodic environment updates, integrations, and AI/marketplace access - and teams that budget only the licence price routinely underestimate year 2 and year 3 spend.

The following illustrates how these costs flow from initial launch through ongoing operation:

Launching a self-hosted portal sets five parallel cost streams in motion: the annual licence fee, monthly server costs, ongoing administration, periodic environment updates, and optional AI access.

Layer 1 - Licence

Year 1 is the most expensive: full licence price plus implementation. Years 2 and 3 cost 50% of the licence price each, assuming timely renewal. Missing the 14-day grace window means the copy is locked, so treat the renewal date as a hard deadline.

Layer 2 - Server

You need a dedicated server (cloud VPS or physical hardware). Based on typical project experience, server specifications scale with user count:

You also need a dedicated external IP address, a domain pointed to it, and an SSL certificate (Let's Encrypt works and is free). For detailed hardware guidance, see the self-hosted hardware sizing guide.

Layer 3 - Administration

Ongoing server administration covers: uptime monitoring, backup verification, OS and PHP updates, SSL certificate management, and incident response. This can be handled by an in-house Linux administrator or outsourced to a Bitrix24 partner. Neither option is free - both should appear in the annual budget.

Layer 4 - Periodic environment updates

Every 1-2 years, expect planned work for: PHP version upgrades (Bitrix24 requires specific PHP versions; running end-of-life PHP is a security risk), Bitrix24 core version updates (which require a staging environment to test custom modifications first), and OS migrations if your base distribution reaches end-of-life.

Layer 5 - CoPilot and Market app access

On self-hosted, CoPilot is included, but it needs the AI Integration module and outbound access to the Bitrix24 AI proxy. Budget the setup and network-policy work for this layer if you plan to use AI features or Market apps.

For a full 3-year financial model comparing self-hosted against cloud at different user counts, see the 3-year TCO analysis.

---

Self-Hosted vs Cloud Bitrix24: When Does On-Premise Make Financial Sense?

Self-hosted Bitrix24 is not always cheaper than cloud - at small user counts and short time horizons, cloud is typically lower total cost. The core argument for self-hosted is data residency and control, not price; financial advantage generally appears at larger user counts over a 2-3 year horizon when the flat-fee licence structure means per-user cost drops as headcount grows.

When self-hosted typically makes sense:

• 50+ users on a 2-3 year horizon, where the flat licence fee distributes across enough seats
• Data residency requirements (local regulation, sector compliance, or internal policy) that cloud cannot satisfy
• Need for source-code-level customisation beyond what REST API allows
• Multi-branch Enterprise deployments requiring web cluster configuration

When cloud is often the better fit:

• Smaller teams with no specific data residency requirement
• Companies wanting fast deployment and no infrastructure overhead
• Businesses whose IT team does not include Linux administration experience

For a broader comparison that includes third-party alternatives, see Self-Hosted CRM Compared: When Bitrix24 On-Premise Wins.

---

Budget Planning Checklist Before You Buy

Before committing to a self-hosted Bitrix24 licence, confirm all five TCO layers are accounted for in year 1, year 2, and year 3 budgets - the licence is only one of them, and teams that skip this step routinely face unplanned spend in the second year.

Use this checklist before the purchase decision:

• Determine user count with 2-3 years of growth headroom (choose an edition tier accordingly)
• Choose server scenario: managed cloud VPS vs owned hardware
• Confirm who administers the server: in-house Linux admin or outsourced partner
• Add 50% renewal cost to years 2 and 3 of the budget
• Add server costs (monthly) across all three years
• Budget for periodic PHP and OS updates (plan for at least one environment update cycle in 3 years)
• Decide whether you need the AI Integration module for CoPilot, and confirm outbound proxy access is feasible given your network policy
• Separate implementation cost from TCO - initial setup and configuration are a one-time cost in year 1 that sits alongside the licence, not inside it
• Set a calendar reminder for renewal at least 30 days before the 14-day grace period begins

For implementation scope and effort, the Bitrix24 implementation hours reference gives realistic ranges by module. For deployment architecture decisions, deploying on AWS, Azure or a private cloud covers the main hosting options.

ACP Group is a Bitrix24 Gold partner with 750+ clients and 1,200+ completed projects. For a structured TCO calculation specific to your organisation's user count, integration requirements, and server preferences, visit acp-24.com.