+7 (700) 700 71 77 info@oneit.kz
Bitrix24On-premise edition · Gold Partner

On-premise Bitrix24 that runs without your own sysadmin

Platform and server updates, verified nightly backups, 24/7 monitoring, protection against break-ins and recovery after failures. On your servers or in our ONEHOST data centre in Kazakhstan — from 60 000 ₸ a month.

On-premise Bitrix24 on servers: updates, nightly S3 backups, 24/7 monitoring and protection
3hResponse timeto an incident in business hours
24Monitoring 24/7Zabbix on every server, Wazuh SIEM in Standard and Business
S3Backups every nightto S3, versioned and verified
KZData centre in Kazakhstanour ONEHOST hosting or your server

Diagnosis

What breaks in an on-premise portal that has no administrator

On-premise differs from the cloud in one thing: you are responsible for the server. Here is what people most often come to us with — usually after an incident has already happened.

1

Updates not installed for months

The portal is several versions behind: integrations drop off, new tools are unavailable, and known vulnerabilities stay open.

2

Backups exist, but nobody has checked them

The backup was set up at installation. When it was needed, it turned out the disk was full and the last working copy was six months old.

3

Everything slows down by the evening

PHP, MySQL and memcached run on default settings; as staff and data grow, the portal takes ten seconds to open.

4

Break-in through an old module

An unpatched Bitrix, a third-party Marketplace solution or password-based SSH — and a miner or a spam mailer appears on the server.

5

Went down on Friday, found out on Monday

There is no monitoring, so it is customers who report the problem. Recovery starts with the question “where are the backups, anyway?”

Sound familiar?

Below is what we do to prevent this, and how it works on our own portal. How it works →

What is included

Six areas that administration covers

Everything an on-premise portal needs to live for years: from updates to recovery after a failure. Integrator work on portal configuration is counted as hours within the plan.

Updates

The Bitrix24 platform and modules, PHP and MySQL, the operating system. We update within a maintenance window, with a backup before we start and a portal check afterwards.

How we do it: server settings are changed only in files that BitrixEnv does not overwrite, so an upgrade never rolls back the tuning.

Backups

Database, files and configuration — every night to versioned S3 storage in Kazakhstan. The database log archive lets us roll back to any point in time, not just to last night.

How we do it: we regularly restore backups on a test node; if a backup fails to restore, that is a monitoring error, not a surprise on the day of the outage.

Monitoring 24/7

Zabbix watches load, disks, queues, external portal availability, certificate expiry and DNS. An alert reaches the engineer before a complaint from staff does.

How we do it: we tune thresholds to your portal so that alerts do not turn into noise that nobody reads any more.

Security

Wazuh SIEM on the server, brute-force protection, key-based access, control over third-party modules and files in the web root, security updates without delay.

How we do it: the same rules as on our 48 servers under Wazuh: a suspicious file in upload is spotted by the system, not by the client.

Performance

Tuning PHP, MySQL and memcached for the real load, hunting down slow queries and missing indexes, composite cache, clearing out agents and logs.

How we do it: we look at metrics, not feelings: how many queries there are, which ones are heavy and how much memory is really needed.

Diagnostics and recovery

Investigating portal and integration errors, recovery after a failure or break-in, moving the portal between servers, Bitrix24 consultations for staff within the plan hours.

How we do it: every incident ends with a report: the cause, what was done, and what was changed so that it does not happen again.

How it works

We administer your on-premise portal the same way as our own

crm.onelab.kz is the on-premise Bitrix24 our own team works in. It is built as a seven-node cluster in the ONEHOST data centre, and everything described below we tested on ourselves first.

Diagram of a fault-tolerant on-premise Bitrix24: load balancers, two web nodes, three database nodes, S3 backups, Zabbix and Wazuh monitoring
The diagram scrolls sideways →

1Fault tolerance

For portals that must not stop: two web nodes with synchronised files and a three-node database cluster. Staff do not notice a single server going down. For smaller companies — one server with the same backups and monitoring.

2Backups that actually restore

Nightly backups of the database, files and configs to versioned S3, a database log archive for point-in-time rollback, regular verification by restoring on a test node.

3Monitoring and SIEM

Zabbix collects server and portal metrics, Wazuh analyses logs and files for signs of a break-in. Alerts reach engineers in Telegram, with maintenance windows taken into account.

4Change discipline

Settings only in files that BitrixEnv does not overwrite; a backup before every update; a log of what was changed and when. So the portal can be handed over to another administrator without any archaeology.

Tools:BitrixEnvPercona XtraDB Clusternginx · PHP · memcachedZabbixWazuhS3 ONEHOSTfail2banProxmoxHosting — ONEHOST, data centre in Kazakhstan.

Plans

Subscription administration

A monthly fee per server with a portal. Every plan includes updates, backups, monitoring and a response within three hours; the plans differ in integrator hours and depth of control. Portals on several servers — a cluster — are supported on the Business plan.

Start

60 000 ₸per month, excl. VAT

Server under supervision

Platform and Linux updates, Zabbix 24/7, resource optimisation, verified backups with restores, response within 3 hours.

  • no integrator hours;
  • for portals on our servers;
  • priority handling of tasks.
Choose Start
Standard · most popular

90 000 ₸per month, excl. VAT

Server plus portal

Everything in Start, plus 2 integrator hours a month, a personal manager in WhatsApp, investigation of portal outages and a quarterly technical audit.

  • 2 integrator hours;
  • monitoring and SIEM: Zabbix + Wazuh;
  • control of standard integrations;
  • a portal audit once a quarter.
Choose Standard
Business

from 200 000 ₸per month, excl. VAT

Portal with integrations and customisations

Everything in Standard, plus 7 integrator hours and control of non-standard integrations: 1C, custom modules, external APIs.

  • 7 integrator hours;
  • monitoring and SIEM: Zabbix + Wazuh;
  • control of any integrations;
  • advanced DevOps practices;
  • priority in the task queue.
Choose Business
What is included
Start
Standard
Business
Integrator work per month
—
2 hours
7 hours
Bitrix24 platform updates
✓
✓
✓
Server software updates (Linux, PHP, MySQL)
✓
✓
✓
Zabbix monitoring 24/7
✓
✓
✓
Monitoring and SIEM: Wazuh — log analysis, file integrity control, signs of a break-in
—
✓
✓
Server resource optimisation
✓
✓
✓
Backups: setup, verification, restores
✓
✓
✓
Incident response time
up to 3 h
up to 3 h
up to 3 h
Priority handling of tasks
✓
✓
✓
Personal manager in WhatsApp
—
✓
✓
Portal outage analysis
—
✓
✓
Technical portal audit
—
quarterly
quarterly
Control of standard integrations
—
✓
✓
Control of non-standard integrations (1C, custom modules, APIs)
—
—
✓
Cluster administration: load balancers, web nodes, database cluster
—
—
✓
Updates without stopping the portal, node failover testing
—
—
✓
Advanced DevOps practices: infrastructure as code, a staging environment, maintenance windows, automated deployment
—
—
✓
Start · 60 000 ₸
Integrator work—
Bitrix24 and server updates✓
Zabbix monitoring 24/7✓
SIEM Wazuh—
Resource optimisation✓
Verified backups✓
Incident responseup to 3 h
Manager in WhatsApp—
Portal audit—
Integration control—
Standard · 90 000 ₸
Integrator work2 hours
Bitrix24 and server updates✓
Zabbix monitoring 24/7✓
SIEM Wazuh✓
Resource optimisation✓
Verified backups✓
Incident responseup to 3 h
Manager in WhatsApp✓
Portal auditquarterly
Integration controlstandard
Business · from 200 000 ₸
Integrator work7 hours
Bitrix24 and server updates✓
Zabbix monitoring 24/7✓
SIEM Wazuh✓
Resource optimisation✓
Verified backups✓
Incident responseup to 3 h
Manager in WhatsApp✓
Portal auditquarterly
Integration controlany
Cluster administration✓
Updates without stopping the portal✓
Advanced DevOps practices✓

Custom plan and hourly work

Portal on the customer’s servers: the Business plan scope, responsibility boundaries and access are fixed in the contractfrom 200 000 ₸/month
Planned work beyond the plan hours, per hour20 000 ₸
Urgent out-of-queue work, per hour30 000 ₸
All studio specialists work within the hours: Bitrix24 integrators, developers, analysts, designers, SEO✓

Terms

  1. The Start, Standard and Business plans are for portals on our ONEHOST servers; for other platforms we define responsibility boundaries individually.
  2. When our specialists administer the server, the client is not given SSH access: we are responsible for the server’s condition.
  3. Plan hours can be spent on consultations with a technical specialist and a Bitrix24 consultant.
  4. Hours unused within the month do not carry over.
  5. Prices exclude VAT. Server hosting is charged at the rates of onehost.kz.

Hosting

Our own hosting in Kazakhstan — so we take full responsibility for the server

ONEHOST is our hosting brand: virtual and dedicated servers in a data centre in Kazakhstan. The Bitrix24 administrator and the server administrator are one team, and nobody passes the buck.

  • 1We size the server to the portal: number of staff, database and file volume, integrations. Resources are scaled up without a migration.
  • 2Migrating the portal from another host or from the Bitrix24 cloud is part of onboarding, with a check on a test address before switching over.
  • 3Data stays in Kazakhstan: servers, backups and monitoring are within our perimeter, which matters for banks, insurers and state-owned companies.
  • 4If the server is yours, we work on a custom plan with the same practices: backups, monitoring, updates, reporting.

Two hosting formats

A single server covers the needs of most companies. A cluster is needed when portal downtime costs more than a second server.

Single serverA VPS or a dedicated server, BitrixEnv, S3 backups, Zabbix and Wazuh. Up to several hundred staff.
ClusterLoad balancers, two or more web nodes, a three-node database cluster. Updates without stopping the portal.

Size a server

How we get started

The first month: from audit to steady state

We take a portal in any condition. First we understand what is there, then we close the gaps, and only after that do we move to routine maintenance.

01

Server and portal audit 1–2 days

Platform and software versions, backup status, load, access, third-party modules and traces of break-ins. You get a prioritised report: what is critical now and what can be scheduled.

02

Backups and monitoring 1–2 days

First of all, a working backup in S3 and Zabbix with alerts. From this point on, any further step can be rolled back, and we learn about problems before you do.

03

Putting things in order first 2–4 weeks

Updates in maintenance windows, closing vulnerabilities, tuning PHP, MySQL and memcached for the load, key-based access, Wazuh. If the portal is moving to us — migration and a check on a test address.

04

Routine mode monthly

Updates, backup checks, alert triage, integrator hours for your tasks, a report at the end of the month: what was updated, what happened, what we recommend.

Experience

On-premise portals we look after

From our own cluster to the portals of state-owned companies. All on long-term support, not a one-off installation.

FAQ

FAQ

We already have an on-premise portal on our own server. Will you take it on?

Yes, on a custom plan. We start with an audit: versions, backups, access and traces of problems, then we fix in the contract what we are responsible for and what your IT team is. If the server is outdated or nobody is there to maintain it, we will suggest moving to us with a check on a test address.

Why do you not give SSH access to the server?

Because we are responsible for its condition. When two administrators change settings on a server, finding the cause of a failure becomes impossible. You always have access to the portal, to the database through the interface and to all your data; we hand over backup exports on request. If you need full access, that is a custom plan on your own server.

What does “response within 3 hours” mean?

An engineer picks up the incident no later than three hours after the request during business hours. Monitoring, meanwhile, runs around the clock: we learn about an unavailable portal, a full disk or an expiring certificate automatically and often fix the problem before staff notice it.

How often do you update Bitrix24, and can an update break integrations?

We install platform updates as they are released, in an agreed maintenance window, usually at night or at weekends. Before an update we take a backup; afterwards we check the portal and integrations against a checklist. In the Standard and Business plans, integration checks after updates are part of the service.

Where are backups stored, and how fast can you restore the portal?

In ONEHOST S3 storage in Kazakhstan, with versioning: a deleted or corrupted file can be brought back for any date within the retention period. Restoring a server from a backup takes from one to several hours depending on the size of the database and files; we regularly verify backups by restoring them.

What can integrator hours be used for?

Anything related to the portal: configuring pipelines and robots, access rights, staff consultations, small customisations, answering Bitrix24 questions. Hours do not carry over to the next month; work beyond the limit is billed at the hourly rate.

Who keeps track of the on-premise licence renewal?

We do. A discounted renewal for the next 12 months costs 30 % of the edition price, but only within a window: no earlier than 90 days before expiry and no later than 15 days after. From day 16, renewal is only possible at full price, so we remind you of the deadline in advance, issue an invoice and update the key on the portal once it is paid.

How does this differ from cloud edition support?

In the cloud the vendor is responsible for the server, and we support only the portal. On-premise adds the server, updates, backups, monitoring and security — that is what administration is. For the cloud there is a separate service: Bitrix24 cloud edition support.

Can we start with a single server and move to a cluster later?

Yes, that is what we do most often. A single server with backups and monitoring covers the needs of most companies. When portal downtime starts to cost more than a second server, we add web nodes and a database cluster without reinstalling the portal.

Discuss the task

Tell us where your on-premise portal lives today

Your own server or a hosting provider, how many staff, when it was last updated and whether there are backups. That is enough for us to suggest a plan and the first steps.

  • We reply within a business day; the server audit is done in the first two days after onboarding.
  • We will show you what monitoring and the backup report look like on our own portal.
  • Moving to us comes with a check on a test address and no downtime for staff.

Have portal access details or an infrastructure description? Send them to info@oneit.kz (PDF, DOCX, XLSX up to 20 MB) — and mention it in your message.

0/500